View Single Post
Old 21-09-2005, 23:56   #20
Stuart
-
 
Stuart's Avatar
 
Join Date: Jun 2003
Location: Somewhere
Services: Virgin for TV and Internet, BT for phone
Posts: 26,546
Stuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver bling
Stuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver blingStuart has a lot of silver bling
Re: Windows 2000 Server - Remote Access

Quote:
Originally Posted by Jon M
lol, if you actually read all the posts you'd see that I was talking about "Remote Desktop" in reference to the first post .. I mentioned Terminal Services a few posts later too
Terminal Services is compatible with Remote Desktop...
__________________

Quote:
Originally Posted by Jon M
The only inbuilt service that will work is Remote Terminal Service, but I doubt your admin will get what he wants using that.

What admin task that you can perform at the Windows 2000 console, can you *not* perform with Terminal Services?
__________________

Quote:
Originally Posted by JamboUK

Ahhhhh... so I am not going that mad then... this is what I need to do... any hints and tips?

Right, it's not as easy to install as Dameware (admittedly), but, on the Console, go to "Control Panel", "Add/Remove programs", "Add/Remove Windows Components", then make sure "Terminal Services" is ticked.

When you click OK, Windows will ask if you want to use it in Remote Administration mode or Remote Application mode. Using Remote Application mode requires access to a Terminal Services Licensing server (which costs extra), so use "Remote Administration" mode. This is free, but you cannot have any more than 3 administrators attached.
Stuart is offline   Reply With Quote