Remote Desktop Services won't install, (reports needing reboot regardless of rebooting)

I am trying to set up Server 2012R2 to allow 6 people to RDP into it.  I have bought the 6 per user cals.

After installing RDS role via server manager.  I am stuck trying to configure.  I have rebooted 3 times.

When going through the Add Roles. ( logged on as Domain Admin)
 ) I select Remote Desktop Services Installation
 ) I select Standard Deployment ( I also Tried Quick Start).  (Drop down only has the 1 local server)
 ) I select Session-Based Desktop Deployment
 ) I select only machine listed (localhost)
 ) Install RD Web Access Role is checked
 ) Server is selected for Server Pool

BAM, "checking Compatibility" windows pops up saying server has Pending Reboot.
I have rebooted several times always coming back to this same point.

I could "exclude" it, but it's the only server and needs to be configured, so that shouldn't do anything.

How am I supposed to continue?
Dwight CraneIT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

please check the following key and post what is there

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Dwight CraneIT ManagerAuthor Commented:



This occurred because you tried to update a hardware driver and didn't reboot after the application update.

Here is a process for Symantec, but you can follow the same process in order to recover for this..

Please backup the registry keys you are modifying. I would do this after hours and make sure you are local if you don't have a CMC you can log into.

Open the Windows Registry using regedit.exe.

  • Search for the entry "PendingFileRenameOperations" in:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
  • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager
  • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager
  • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore
If you find the entry, first back up each key, and then delete the entry in each key.

  • Search for the RebootRequired key:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
  • If you find the key, first back up the key, and then remove the key.
  • Restart the SEP installation; the install should finish without error.

here is the source article :

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dwight CraneIT ManagerAuthor Commented:
So there was a program that was essentially reinstalling itself every reboot, so the values were getting repopulated.  I uninstalled the program then I was able to delete those keys without them reappearing.

Awesome, Glad you got it resolved.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.