Saturday, January 22, 2005

Enabling Windows 2003 Remote Desktop Connection remotely

I learned a neat new way to enable the Remote Desktop Connection service on Windows 2003 today. Several times, I have set up a Windows 2003 server, and forgotten to right click on the compter, go to the Remote tab, and enable the Remote Desktop Connection service. I figured this was a simple registry key, but I had never bothered to research it.

I was faced with this yesterday and figured it was time to get a Googling! Or, I was going to have to drive a couple of hours through Seoul traffic to get to the remote server site.

Connect to the W2K3 machine's registry remotely.

Locate the following registry subkey:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

Locate the following REG_DWORD value:
fDenyTSConnection

Change the value from a 1 to a 0.

Remote the server (you can use the SHUTDOWN.EXE command to do this remotely.)

3 Comments:

At 3:06 PM, Blogger Stuart said...

How about doing it remotely with WMI and not requiring a reboot?

wmic /node:"Computer name (Fully Qualified)" /USER:"username" RDTOGGLE WHERE SErverName="Computer Name" CALL SetAllowTSConnections 1

Way better than registry hacking.

 
At 10:10 PM, Blogger Karen said...

Windows Remote Desktop is one of the most commonly used tools for remote access. But Microsoft apart, vendors such as RHUB http://www.rhubcom.com also offer reliable Remote Access products. RHUB’s TurboMeeting is an appliance, and as such provides much more security than online hosted solutions. Impressive features include instant remote control, remote reboot, auto remote reconnection, low-bandwidth-compliance, firewall and proxy-compliance, lockdown system-compatibility, and more.

 
At 4:31 AM, Blogger Terry Hardy said...

I think most third party remote access options would also be way better than registry hacking, but sometimes it takes a little code manipulation to make a guy feel good about his work!

 

Post a Comment

<< Home