RDS-O-Matic live in the wild.


Just a quick post to show you RDS-O-Matic in action. I just updated it to match what we have on the book I am releasing with Freek Berson. As I mentioned before this little handy Excel spreadsheet (Windows app will be ready and released at E2EVC Dublin) right now does the following:

  • Creates a complete RDS deployment with:
    • 2 RD Connection Brokers
    • 2 RD Web Access servers, load balanced using NLB on port TCP 443.
    • 2 RD Gateway servers, load balanced using NLB on ports TCP 443 and UDP 3391.
    • 2 RD Session Host servers with the desktop experience loaded.
    • 2 RD Licensing Servers, activated and set to whatever you choose (Per User/Device).
  • Creates a collection with the 2 RD Session Hosts on it.
  • Creates a test published application, WordPad, so you can try the environment immediately.
  • Enables HA on the RD Connection Brokers. For that you need to have SQL ready to go, the folder where the database will be stored has to be created and permissions for the RD Connection Brokers set. This is all detailed and explained in the book. We even cover the actual SQL install.
  • Retrieves the certificate (you enter the location for the certificate in PFX format) and deploys it to all roles. Here I assume you will be using a single, wildcard certificate for all the roles. If not the case, you can easily change the script you get to use different certificates.
  • Final warning, you must have the output folder created before you hit the ‘RDS-O-Matic’ button (i.e. C:\RDSOMatic).

Now that I am back at developing for iOS, is there any value in creating an iOS app that you can enter all this info and it will email you the script ready to be deployed?

Let me know.



9,346 total views, 1 views today

14 Replies to “RDS-O-Matic live in the wild.”

    1. The actual tool, a Win32 app, is ready and will be released at PubForum (E2EVC) in Dublin, June 2016. Once released, I will have a link for downloading it available here.


  1. Hi,

    Genuine question. Why NLB? It has inherent flaws that are too big to ignore. It’s not what I would use in production. (Unless maybe a small deployment?) What the people need is a guide on configuring an open source load balancer with VRRP or the like. Just my two cents.


    1. NLB was much worse back in the day. Now I am far from saying it is perfect but my experience shows that it either works perfectly or does have all sorts of issues. Depends on many things and that is the main problem. You never know what to expect. But as I said, does work for many people. The main reason for it to be part of the script is to simply have something out-of-the-box and something that can be easily scripted with PowerShell, all under Windows.



    1. Very shortly now. Three chapters should already be available directly off our sponsors websites (Tricerat, Devolutions and ControlUp). The full book will be released on Amazon. Couple days from now!


    1. it turns out that you kept it inside the executable at the moment 😉
      never the less, when I was using that magical strings presented inside one of your brilliant sessions it turned out, that microsoft has changed the structure of the commandlets and for instance even at the very beggining for New-SessionDeployment it is now New-RDSessionDeployment and you can not pass @(“”,””) as a variable for -WebAccessServer but just a string.
      Have to be cautious! 😉

Leave a Reply

Your email address will not be published. Required fields are marked *