Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Terminal Server Setup Guides

Status
Not open for further replies.

rogerpatel

Technical User
Jun 14, 2005
120
Hello,

I've been given a task of setting up a terminal server for a new Domain and looking to find out if anyone can point me in the right direction to some sort of dummy guides, do's and dont's etc etc for installing Terminal Server.

Our network is as follows

2 Windows 2003 Domain Controllers
1 Windows 2003 Server with Exchange 2003
We have 40 local users running XP with Office 2003

There is a requirement for 10 Remote users to be able to user Terminal Server remotely.

The Remote users are all based in another office with a direct connection. Speed is no problem, its a dedicated 2mb circuit.

I have installed Terminal Server in Application Mode an d install the Client Licensing, this all works.

I would like to know if there are any best practice guides on how to configure it so my users are locked down etc, i also understand there are things like making sure users profiles are kept on the D drive as to the system drive etc.
Hope u can understand what i'm trying to do here.

Thanks Very Much.

Roger
 
Don't install the TS licensing on the same server as the TS. Install this on the DC with FSMO roles. Install the Enterprise version of licensing, not the domain version. You will need to redo what you have already done on the licensing, but this is a good practice.

Even though this is just 10 users i would set up TS profiles redirected to your file server or one of your DCs. Others might call this over kill, but you may grow and having this set up at the start would also be a good practice.

Have a look at this to help in how this is done: thread48-1239910

Having the profiles set up this way will allow you to delete the TS profile on the server when users log off and implement UPHClean. This is a service that MS has released to aid with profile issues that you may encounter.

These remote users, will they be fat or thin clients (i.e. wyse terminals)?

Good luck


"Assumption is the mother of all f#%kups!
 
Great Pointers and help guys, really helpfull.

The remote computers are all Windows XP Pc's.

 

Can you please explain why i should install the TS Licensing on the same server as the TS server and install it on my Main DC with all the Roles?

Thanks
 
You should only have 1 instance of TS licensing on your domain / forest.

TS licensing is important to the management of Terminal Server access on your network. You have the 90-120 day grace period if this becomes corrupted but having it installed on the box that you general users will use (and potentially corrupt) increases this likelihood.

You have DNS, DHCP, User accounts / permissions and computer management plus many other network management components, it is the logical location. If you need to increase the number of Terminal Servers in the future, it is central for that also.


"Assumption is the mother of all f#%kups!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top