couple questions on configuring terminal services

[MrHappyMonkey]

I'm trying to install terminal services on a server and have a couple of questions. The server is running Win2k server edition on a 1.1Ghz P3. I've got the terminal services and the licensing manager components installed. Next, I'd like to set up the termnial so that it can run on a web browser on the client machine. How exactly do I set this up? I couldn't find any FAQs on labmice.net for this.

Help?

 

[randal]

Assuming that things were installed correctly and that you have IIS 5.0 installed, it should have taken your Default Website and made a new virtual directory called "tsweb". You go to http://you.rdomain.com/tsweb and a little web-client will load up ... type in the server name to connect to, and voila, Terminal Services in action.

Example is at
http://www.hpi.net/tsweb

If you do not have the terminal services thingy automatically come up, let me know and I'll e-mail you the Terminal Services web client files, which you can place on any website you have.

Cheers,
randal

 

[MrHappyMonkey]

Thanks. I found a nice eBook that explained everything nicely. Now that I have IIS running, what do I need to do to lock it down so that no unauthorized people can enter?

 

[randal]

Well, that in itself is pretty funny, because this *is* IIS. Heh.

It takes some work to get it locked down well, yet maintain usability. A good place to start is the Microsoft IIS Lockdown Utility (link below). Mind you, it locks it down *VERY* tight, and you'll have to go about unlocking a lot of things to make stuff work.

Microsoft IIS Lockdown Tool v2.1

cheers,
randal

 

[FUBAR]

Of course, the ubiquitous answer comes to mind, windowsupdate.microsoft.com for all your patching needs. That will at least do with (some of) the holes.

 

[Buddha Bart]

sorry guys, this might seem like a newbieish question, but whats the advantage of using TS over something like VNC?

bart

 

[Woodchuck2000]

sorry guys, this might seem like a newbieish question, but whats the advantage of using TS over something like VNC?

TS is far more secure for a start. There's a degree of encryption and also the authentication process is hardware to crack.
Also, it's far more bandwith efficient. Try running both over ISDN and you'll find that TS is way more useable.
And it's built into the OS as well. Using the TS Client that comes with XP, most of the useful keystrokes like alt-f4 are redirected to the remote machine whereas using VNC, they would close something on the local machine.
And TS allows users to use existing credentials to log on. And you can have multiple sessions running on a single server. And it doesnt stop people logged on locally from using the machine. The list is pretty much endless...

(Recent TS convert incase you hadn't guessed)

 

[randal]

Yes, TS is secure out of the box, and it's very, very fast. In VNC, when you move a window, it has to send pictures of the screen across the wire (very slow, pictures are big). With Terminal Services, when you move a window, the client tells the far side "move window A to coordinates 24x382", and then the client side (your machine) takes the info, makes a native API call, and moves the window. Commands are way shorter, and hence a lot faster, than screenshots. The astounding speed of TS makes it really, really easy to admin a server farm from your desk.

Also, with the windowsXP version of TS, you can even get sound across the wire, too. It's pretty awesome -- it compresses the audio, and adjusts the compression/quality depending on available bandwidth -- all on the fly. Pretty shweet.

I *love* TS.

randal