New Terminal Server best practices

[Guest Marshall Varner]

I have just installed a new terminal server at my main office. We have a

satellite office about 25 miles away. I wanted to provide access to

resources at our main office to our satellite. We have Windows 2003 Adtive

directory domains at each location and trust have been setup. We are

connected via a point to point T1 Line.

 

The server is working properly as far as I can tell. The only application I

have installed is Office 2003 and it seems to work fine.

 

I now need to start creating user accounts and installing other apps but

before I do I wanted to make sure I don't screw anything up. I am looking

for some good documentation on best practices and procedures to keep my

server running properly.

 

Anyone have any suggestions.

[Guest sen_ismail@web.de]

Re: New Terminal Server best practices

 

Hi,

 

you will not find any documenatation about how many users and apps on

TS are available without get a slow performace. Here are many points

which are important and alltogether act as a part /Server hardware/

RAM/CPU/NETWORK/APPS....

You have to test these. I would suggest to monitor Server with perfmon

and adding more and more Users to the Server so you scaling your

environement.

 

Only : http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx

here you will find Scaling windows 2003 Terminal Server White paper

but I will be not very helpful.

 

cheers,

Ismail