Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
Hello AskPerf. Another quick post to alert you of a new update for the Servicing Stack, which is very important for Remote Desktop Services. Previously, installing the Remote Desktop Services role and Active Directory Domain Services role on Windows Server 2012 was not supported. This is now supported after installing the update below, along with a few other improvements.
A servicing stack update is available for Windows RT, Windows 8, and Windows Server 2012: September 2013
Don't you not want to support putting RDS - and- a DC on the same server?
This restriction in Remote Desktop Services in Windows Server 2012 has generated many questions in the Technet Forums. This is great news! Thanks!
Hi Blake, thanks for the info. Do you recommend to install the update proactively or just on the systems experiencing the issues?
I think this broke my TS environment. I have had to remove all windows updates from 9/11 on all my domain controllers. My 2008 TS servers were showing the license server unavailable. 2003 servers and some of the 2008 servers keep saying the time/date is out of sync with the DCs. DCs are all 2008 R2 with DNS and license server for TS and citrix.
@Susan - Yes, in operating systems prior to 2012 we would warn you when you tried to install the RDSH role on a Domain Controller, or if you tried to promote a domain controller that already had the RDSH role installed. The issue was a security risk but we did not block you from running RDSH role on a Domain Controller. Windows Server 2012 now installs Remote Desktop Connection Broker role service as it is required for the new RDS Management UI to function, due to the issue in the servicing stack, you could not install RDCB role on a Domain Controller. This update corrects that problem and now allows you install all RDS role services on a Domain Controller. Depending on your environment, it may still not be a good idea to do so, but it is supported.
@Brent - This is a Windows Server 2012 update only, which 2012 Server did you install this update on and how does that server fit into your RDS deployment? If your environment does not have 2012 servers then this update is not the cause of your problem.
@miroslav - I would recommend installing this update proactively as it fixes problems with the servicing stack in Windows 8 and Windows Server 2012.