Installing Remote Desktop Services on Windows Server 2012 R2 EC2 fails every time
Posted on 2016-09-05
Hi All, we have recently moved all of our servers from a private cloud provider to AWS. As part of the move, there was a task to consolidate around 7 - 13 windows boxes, with a separate service running on each, into 1 APP and 1 DB server. We have now completed this process finishing with Sage 200 which was moved by a third party professional service. Sage is set up to be used as a remote application, at the moment only 2 people can access the application at one time as Remote Desktop Services is not installed on the APP server.
Whenever I try to install RDS it breaks the server. After looking like a successful install, the server will reboot to complete the process and then not be accessible again. I can see that it is on in AWS, it has only passed 1 of the 2 AWS status checks, non of the services running on it are accessible (e.g. we have LanSweeper running on it), I cant ping it and I cant RDP to it. If I view the instance screen shot, I can see the 'Ctrl Alt Delete' screen which hasn't frozen as the time changes. As AWS doesn't offer any kind of console to hard link into the server (Like a v sphere client for VMWare) the only way to get the server back to any working order is to restore from an image. I have now restored 2 images so that one can be used by staff but only 2 at a time and I can use the other to try and figure out what's going wrong.
Some things I've tried (all result in a non-responsive server which needs to be terminated and a new one restored)
- Turn Windows firewall on during the installation. I saw this in a Microsoft online solution.
- Get Windows up to date. Windows hadn't seen an update in a while and in fact the first update attempt failed. I ran WinUpdateDiag tool to get it working and up to date.
- Install RDS using Powershell. Again, a suggestion I saw online.
The last time I tried was after getting windows up to date, I installed the RDS features and then whilst the machine was booting back up I sat refreshing the instance screenshot in AWS watching the 'Working on features' progress up to 100% and then say 'we couldn't complete the features. undoing changes'. It then went into the unresponsive state that I've previously mentioned.
I'm now in a position the suggest Citrix to my boss or spin up a new server and migrate Sage again but I'd like to throw it out to the community first. Any suggestions greatly appreciated and let me know if you need more info.