Microsoft RDS - Thoughts and walkthrough 1/3 - Introduction, architecture and installation Microsoft RDS - Thoughts and walkthrough 2/3 - Setup, security and optimization Microsoft RDS - Thoughts and walkthrough 3/3 - SP1 and Remote FX - Citrix Now everything is install, we need to configure and establish a communication between each component. Here we go, first we need to authorize TESTRDS1, TESTRDS2 and TESTRDSINFRA to exchange information about their RDS roles : On TESTINFRA, in the local group TS WEB Access Computers you need to add TESTRDS1 and TESTRDS2 serveurs : On TESTRDS1 and TESTRDS2, make sure to add TESTINFRA to the very same group Then on TESTINFRA, through the Server Manager console, you need to go in Remote Desktop Services  / Remote Desktop Connection Manager and then click on RD Web Access Server make sure all the machine are added : Now, still on TESTINFRA, web need to add the two Remote Session host servers to the Session Broker Computers local group This is now the DNS part, we need to create two (A) records, I chose applications and you'll need the two IP addresses of your RD servers. In my case it mean : TESTRDS1 = 192.168.0.11 and TESTRDS2 = 192.168.0.18 Now we need to configure the two session host servers (TESTRDS1 / TESTRDS2) to use the broker (TESTINFRA), to do so, on TESTRDS1 and TESTRDS2, go through the server manager console to the Remote Desktop Session Host Configuration and double click on the option, Member of farm in RD connection broker: And change as follow : And finally, configure RemoteApp (on TESTRDSINFRA) to Connect to the RD Server Farm (TESTRDS1 and TESTRDS2) Don't forget to make the change on both servers (TESTRDS1 & TESTRDS2) then we need to configure the Connection Broker for RemoteApp Programs (on TESTRDSINFRA) by changing the following options (right click on the main panel) and fill the information by the name you chose to add earlier in the DNS. We're done for the configuration part, now we can test (don't forget to publish some application), launch Internet Explorer and type the url of you Web Access server, for it look like : http://testrdsinfra.suomi.inc/rdweb Beside the warning we got because we didn't deploy any certificate, everything is working well and it looks good. I tested a bit and tried to connect with a old Wyse Sx0 / Winterm S30 and I faced a…

Microsoft RDS - Thoughts and walkthrough 1/3 - Introduction, architecture and installation Microsoft RDS - Thoughts and walkthrough 2/3 - Setup, security and optimization Microsoft RDS - Thoughts and walkthrough 3/3 - SP1 and Remote FX - Citrix With Microsoft Windows 2008 R2, Microsoft deliver an affordable application publishing system (XenApp like) for the micro size business and small business size company. Often these customers ask us : "Why XenApp is so expensive? Microsoft are doing the same !" and most of the time my answer is yes, Citrix are more expensive but if you really compare all the features, you'll see there is differences. And these differences are still huge but most of my SMB customers just need what Microsoft can bring with RDS at first. I mention at first, because once they taste the power of virtualization and the delivery in a blink of an eye, they can make the jump and check Citrix products out. I wrote this blog because I had to deploy a full Microsoft RDS architecture with Remote Desktop Session Host,  Remote Desktop Licensing, Remote Desktop Connection Broker and Remote Desktop Web Access and I think in less than one year this very same customer will call to request a XenApp or XenDesktop POC. So if I want this customer call next year, I need to do a good job so he will really use this RDS infrastructure and users will get use to being able to work from everywhere. For the one not use to 2008 R2 yet, terminology did change too : Previous name Name in Windows Server 2008 R2 Terminal Services Remote Desktop Services Terminal Server Remote Desktop Session Host (RD Session Host) Terminal Services Licensing (TS Licensing) Remote Desktop Licensing (RD Licensing) Terminal Services Gateway (TS Gateway) Remote Desktop Gateway (RD Gateway) Terminal Services Session Broker (TS Session Broker) Remote Desktop Connection Broker (RD Connection Broker) Terminal Services Web Access (TS Web Access) Remote Desktop Web Access (RD Web Access) Previous name Name in Windows Server 2008 R2 Terminal Services Manager Remote Desktop Services Manager Terminal Services Configuration Remote Desktop Session Host Configuration TS Gateway Manager Remote Desktop Gateway Manager TS Licensing Manager Remote Desktop Licensing Manager TS RemoteApp Manager RemoteApp Manager Now let's go for a basic setup with 3 machines (Microsoft Windows 2008 R2) 2 machines with the Remote Desktop Session Host role - TESTRDS1 & TESTRDS2 1 machine with Remote Desktop Connection Broker and Remote Desktop…