Termnial Services service enables users to connect to the computer remotely from some other PC. If this service is not running you can not set up remote desktop connection and you can’t even configure RDP settings in My computer properties.

Remote Desktop Services will stop working because this computer is past grace period and has not contacted at least a valid Windows Server 2012 license server. Click this message to open RD Session Host Server Configuration to use Licensing Diagnosis. We had this happen recently on two servers, in our case there was a subkey HKLM system currentcontrolset services TermService security Deleted the security subkey and Remote Desktop Service showed back up in services and is working. But in some cases restarting terminal services could be possible by killing the svchost process that runs the terminal services.We can use tasklist and taskkill commands for this. First get the process id of the terminal services process tasklist /svc findstr /C:TermService. Check if Terminal services is the only service running in this svchost. Oct 16, 2017 Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 Learn about the available Remote Desktop Services (Terminal Services) command-line tools, with descriptions and links for more detailed information. Remote Desktop Services (TermService) Remote Desktop Services UserMode Port Redirector (UmRdpService) You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets).

You can start the service from Service management console. Starting Terminal Services may fail and pop up an error window with the following message in it.

Remote Desktop Services Crashes - Social.technet.microsoft.com

“The terminal Services service on Local computer started and then stopped. Some services start automatically if they have no work to do, for example the Performance Logs and Alert Service.”

And if you try to start Terminal Services service from command line you would get the following error

H:>net start TermService
The Terminal Services service could not be started.

Svchost(Termservice) Process Using CPU

The service did not report an error.

More help is available by typing NET HELPMSG 3534.

H:>

The solution for the above problem is to change the registry settings for Terminal Server. Open registry editor from Run and open the below mentioned node.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server


Now set the data in the registry value TSEnabled to 1.

Reboot the machine to make the changes effective. After reboot, you can see that Termnial Services service is up and running.