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!

2003 Terminal Server

Status
Not open for further replies.

Orlean

IS-IT--Management
Mar 29, 2005
6
US
I have 10 remote users connecting from one of our remote units to a 2003 TS. Our Corp has a blanket licences, do I still need to purchase CALs for our Terminal Server aswell set up a Licensing Server.

Also does anyone know a the average mem requirements per user for a TS connection?

thanks
 
hi everybody!

I have a server runing windows 2003 sbs. DHCP is runing on the server and i have a network printer instaled on the network. My problem is that every time the ip address renews the printer gets a different one... and i have to reinstall it? What should i do about it? I it necesary to put it on a static ip address?

another qestion.... I have microsoft exchage instaled on the server and i have a local domain (mydomain.local) and exchange is configured for that domanin (ex: admin@mydomain.local). I have allso an internet domain and i am hosting my web address. I what allso to host my email for the internet domain... how can i do that? is it just an exchage setting or is more complicated?

thanks

Valentin
 
Start a new thread dude...

create a dhcp reservation on the server and give the printer that IP.
 
Orlean, there's no set rules behind a "blanket license," so I can't say whether your TS CALs are covered under it or not. You'd have to check the details of that licensing agreement. It used to be, for Windows 2000, that W2K Pro included a CAL for connections to W2K term servers. That's not the case with W2K3 term servers: all CALs have to be purchased, even for XP clients.

As far as your question about memory, the overhead for a TS session is quite small, under 6mb, but that's when you leave out the shell. Depending on what the user is running and whether you have a program autoload for the session instead of using the Explorer shell, your memory requirements will be different.

For example, if I connect to a server using the explorer shell, it will load my profile, and the amount of memory my login uses will depend on how my profile is set up. On one terminal server explorer is taking up 21mb of memory and 19mb of virtual memory. On another server, I notice that my explorer shell is using on 9mb memory and 4mb virtual memory.

When I look at a server that currently has 35 active users all logged on to a custom application as a shell (no explorer) I see that each session's memory use runs between 12 and 22mb, with 17mb being about average. Since the application locks down the environment fairly well, there will be less fluctuation in session memory use than there would be if all the users were given access to the explorer shell, where they might copy stuff to the desktop, add extra background processes, etc.

Hope this gives you an idea how to guesstimate your needs.

ShackDaddy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top