Terminal Service Plus

I am currently trying to set up a new instance of TSPlus at a new location, and no matter what I do, the installation doesn't seem to work. I do have existing installations, in which I see that there is a TSPlus service running, and connections can be made to the box with no problem.

This new machine is running Windows 2012 R2 Standard, 8 GB RAM, 2xCPU. I've installed some admin tools on it such as MS SQL Managment Studio.

MS RDP has been disabled, firewall disabled, UAC disabled.

My last run followed the below procedure. A little long, but I am grasping at straws here.

1. Reboot machine
2. login as domain admin (console)
3. browse to location and double-click Setup-TSPlus
4. follow wizard, accepting all defaults
5. setup asks for a reboot, which I accept
6. after reboot, log back in (console)
7. check services listing, no ts-plus service listed
8. attempt RDP from other machine to ts-plus machine, no dice
9. open elevated command prompt on ts-plus machine, run netstat -ano | findstr "3389" and find nothing on 3389

What am I missing ? Why is the service not installing during setup ? any idea where to look ?

Hello,

This sounds like you got something corrupted in your registry somewhere... Usually this kind of issue occurs if you installed a Windows service pack after installing TSplus you can also try this compatibility patch here : dl-files.com/CompatibilityUpdate.exe

Maybe reinstalling the latest service pack may solve this issue. If you installed the RDS role on the server, remove it, uninstall TSplus, reboot and reinstall again.

I just freshly deployed the machine, moved it to OU which blocks GPO inheritance. I then did a full cycle of Windows Updates. Finally, I installed TSPlus, with the same results as previously mentioned.

I'll try the compatibility patch that you gave a link to, and see if that resolves the problem.

Thanks,

Derek

Yeah, still a no go after installing the compatibility update.

Service does not appear in the services list, even though I get the splash screen when logging into the server. Can't connect via RDP, no listening services on 3389 on the server.

Any more ideas ?

Hello,

Open a ticket and allow one of our tech to have a look to your server (by teamviewer or other). It sounds like the RDP service is down, registry is probably corrupted for some reason.