25 August 2010

Managing your larger RDS environment using Group Policy

Manually keeping a few server configured can be fairly easy but if you have a large RDS environment this is just not practical or recommended.

Speaking form personal experience - sooner or later one of them gets away from you and then your environment is out of sync.

Luckily there is an answer that comes in the form of group policy.  There is an extensive list of policies that can be applied to manage everything from Session limits device Redirection etc. you can for instance automatically join RD Session hosts servers to a Connection Broker farm with a policy.

There are also settings here that are not accessible through the MMC consoles.  Such as "Turn off Fair CPU Scheduling"  the only other way to turn this off is the manually edit the registry per host.

There is a complete ref here:  http://technet.microsoft.com/en-us/library/cc753697(WS.10).aspx

A nice way to be able to test this is by editing the local policy on a specific machine. or by having a test policy that you can apply to a few test machines.

One important note: remeber what setting you set where.  Some setting can be set in Remote App manager and the same one are available in group policy.  generally speaking group policy will always win.

So just be aware of this in case you start to see unexpected behaviour.

No comments:

Post a Comment