Jump to content

Recommended Posts

Posted

I have read how to set up a Windows 2003 server with Terminal services on and DHCP and i can cope with that no problems. I have read a little about the client stuff but this is where i get stuck.

 

The pcs i intend to use for the clients are all the same spec, with NICS that will PXE boot from floppy. SO i know i can boot from floppy or cd.

 

I could leave the old 20gb drives in them? Is this a good idea or waste of time?

When the client gets to a log on box is it the same as the rest of the fat client domain?

If so do they see a Server 2003 log on box as the server is running 2003?

Does the GPO use the same policy on the client as it does ona fat client in the domain?

 

Sorry but i need basics help please so i can sort of imagine this before set it up

Posted

You can use the 'magical' Etherboot disk that I refer to in my conference document to install an Etherboot image to a small partition on the hard disk - it's all done for you - and you therefore don't need to PXE boot or use boot floppies/cds. The disk is available at http://etherboot.anadex.de/

 

Once booted to the terminal server it is exactly the same as the rest of the domain (assuming that the same GPOs have been applied to your terminal server(s). The users will see a Server 2003 login box as opposed to XP of course but that doesn't matter - plus the colours are nicer ;)

 

As for your GPOs, try your existing ones and you will pprobably find that they need no adjustment.

 

The only thing you need to watch is printers... check out my script in the scripts forum for this as it takes into account thin clients so that users get the correct printer depending upon their location.

 

Don't worry about asking questions - it's a steep learning curve but you may as well make life as easy as possible by learning from others' wisdom... as long as you understand why you are doing things you will know how it works.

Posted
If you just want to see what it's like to use a terminal server, you can simply run that command from your workstation once the server is configured. Likewise, for purely testing purposes, you can set up a terminal server as a virtual machine but in a production environment you must use dedicated hardware.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...