Last year, I shared a few of my favorite tips to address remote desktop issues. I’ve discovered a new trick that can reconfigure remote desktop remotely; this is especially important if you don’t have monitor (console) access, a network-attached KVM, someone local to the server console, or a hardware device such as an HP iLO or Dell DRAC.
Remote desktop for Windows Servers can be set through the registry. Remote access of the Windows registry is enabled by default (when Firewall is disabled), and remote desktop can be disabled or enabled. The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections value is set to 1 by default to disable remote desktop; editing the value remotely to 0 will enable remote desktop on the next reboot. You can make a reboot happen immediately with either the shutdown command or the Restart-Computer PowerShell command. Please refer to one of my previous tips to learn how to launch these two commands.
Opening the fDenyTSConnections value through a remote registry (Figure A) is done with administrative permissions via Regedit and selecting the Connect Network Registry option from the File menu. (Note: Editing the registry is risky, so be sure you have a verified backup before saving any changes.)
Remotely opening the fDenyTSConnections registry value. (Click the image to enlarge.)
In order to make the change take effect, a reboot is required.
This configuration is a documented procedure and is outlined in this TechNet article. Remote desktop can be enabled or disabled on the fly when configured in Server Manager (Windows Server 2008) or on the Remote tab of My Computer (Windows Server 2003).
If you have used this trick to troubleshoot remote desktop, let us know in the discussion.
Stay on top of the latest Windows Server 2003 and Windows Server 2008 tips and tricks with our free Windows Server newsletter, delivered each Wednesday.