Windows Server 2012 : "reboot pending" is blocking deployment of RDS (formerly called Terminal Server)

[Warren in Canada]

Update September 2012: This has been broken for months for me and I still have no idea how to fix this!

Windows Server 2012 won't let me install RDS (Terminal Server), and says I have to reboot, but I rebooted many times, and it still won't let me install RDS.


What used to be called Terminal Server, and is now (confusingly) called a "Session Based Desktop Deployment" scenario within the context of the Add Roles and Features Wizard, under the top level service named "Remote Desktop Services".

I select Quick Start, and I get this far: The server has reboots pending...

Googling this error shows me that you should remove a registry key in the System/CurrentControlSet area in the registry. I looked for that registry key, but that was not the problem, and even rebooting many many times, the error is still not going away, and I have rebooted seven times, and still the error is not going away. I am getting a bit frustrated. A bit more googling lead me to a forum post where someone says that Windows Server 2012 RTM works, but that a later Windows Update has broken the ability of Windows Server 2012 to install RDS scenarios, keeping us from starting to use our server as a "terminal-server".



wp





FIX:


1. Find registry key CurrentRebootAttempts,

if > 0 then set to 0, it's at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerManager2.


2. Go to power shell, RUN AS ADMINISTRATOR, then run these commands:


2a. import-module RemoteDesktop2b.


2b. New-SessionDeployment -ConnectionBroker

hostname.domainname.local


Supply values for the following parameters:

WebAccessServer: hostname.domainname.local

SessionHost[0]: hostname.domainname.local

SessionHost[1]: ...just press enter...

Continue reading...