Starting Remote Desktop On Boot - Win 2003 Server

[Robizzle01]

I set up remote desktop/terminal services for Windows 2003 Standard Server Edition and it works great except that it doesn't start on boot. Once I reboot my computer, I have to go back into System Properties -> Remote and start Remote Desktop once again.

Where can I find the setting that allows it to automatically start on boot? I checked the services window and everything should be set to start.

I'm probably missing something simple here...

[lone wolf]

Please correct me if I'm wrong, you want to connect to a w2k3 server using terminal services, or connect to something else using a w2k3 server.

If connecting to a server using remote desktop, the quick and easy way is to create a shortcut to a saved session and place it in your start menu, that is the simplest way. If you want to go deeper then set up a local group policy. I use a GPO in a domain setting that sets the default RDP to our terminal server.

[zacdl]

It sounds to me like he wants to get TO the server and the service just isn't starting.

You were rather vague... so if neither of us is right, you'll have to give more details.

It sounds to me like you get the service to start by going to Services and hitting Start?
Go into the Properties and you should see options like "Automatic" and "Disabled" or "Manual". Make sure it is on Automatic and it should start at startup.

[Robizzle01]

Whoops sorry ... My description was originally longer but I hacked it up trying to make it short enough that anyone would read and must have taken out a little too much.

I'm trying to start the remote desktop server on boot so that I can remote administrate from various other computers.

In the services window the only services that appear to be relevant are
Terminal Services - Currently set to Automatic - Allows users to connect interactively to a remote computer. Remote Desktop, Fast User Switching, Remote Assistance, and Terminal Server depend on this service - stopping or disabling this service may make your computer unreliable. To prevent remote use of this computer, clear the check boxes on the Remote tab of the System properties control panel item.

Terminal Services Session Directory - Currently set to Automatic - Enables a user connection request to be routed to the appropriate terminal server in a cluster. If this service is stopped, connection requests will be routed to the first available server.

Remote Access Auto Connection Manager - Currently set to Manual - Detects unsuccessful attempts to connect to a remote network or computer and provides alternative methods for connection. If this service is stopped, users will need to manually connect. If this service is disabled, any services that explicitly depend on it will fail to start.

I would have thought that having the first two set to auto would do the trick but when I reboot I am unable to connect. I can then right click my computer -> properties -> remote tab and set up the remote desktop server and it works until I reboot again.

[Icidic]

Isn't, in Microsoft Windows 2003 Server, Remote Desktop (Remote Administration Mode) automagically setup by default? If so, there shouldn't be any problem. The only thing I can see preventing it from starting up on boot is if some other program has grabbed the port that Microsoft Terminal Services uses before it did.

Check to make sure that Port 3389 TCP\UDP is free - and not taken up by IIS\Apache\Ventrillo\TeamSpeak\Mail\MySQL\etc.

[zacdl]

I wish I had a server in front of me to look this up for myself...

But I think Terminal Services would be all you need.

Are there any services that change when you enable Remote Desktop from System Properties???

It just sounds like a service isn't set right- just gotta figure out which one.