Friday, January 29, 2010

A Quick Guide to Windows Terminal Server Setup

Here is quick guide for setting up a Windows 2003 Terminal Server environment. It contains the best pratices that are needed to sucessfully deploy your terminal services server on the fly. Please remember, these changes will be made after you have installed terminal services by going to Control Panel--> Add/Remove Windows Features.

You will need Windows 2003 EE version to use TS.
Important Group Policy/TS Changes For Better Experience:
- Configure "keep a live session" policy settings to the time you think users will be active on Terminal Server to efficiently use resources.
- Configure Terminal Services Profiles so users can log into any server without recreating new profile if a session directory server is used.
- Configure "Local Home Directory" (C:\AppHome) for Application Configuration Data
- Depending your security policy allow users to reconnect
- You should change theme to Windows XP LUNA to make Terminal Server more user friendly
Configuration/Administrative Templates/Control Panel/Display/Desktop Themes/Load a specific visual style file or force Windows Classic,
- Disable screen savers
- Do not change wallpaper for users
- Remove and prevent access to the Shut Down command for users
- Remove links and access to Windows Update
- Remove Favorites menu from Start Menu

For detailed information you can refer to,

Group Policy Order (top to bottom):
Computer Policies
User Policies
Terminal Services Policies as defined in Terminal Services Configuration
User Account Policy
Remote Desktop Client settings

Terminal Services Client Location:%systemroot%\system32\clients\tsclient\win32

Clustering (Optional):
- You can create a terminal services cluster but should separate licensing server
- You can also have session directory server which keeps track of sessions for users

- Place License Server on a different machine or Domain Controller.
- Licensing is activated by Microsoft clearing house online or offline.
- Licenses are permanent on the second connection of users or desktops depending on whether you have per user or per desktop licensing.

Useful TS commands:Current Users: quser/query user
Stop Logons: change logon /disable
Allow Logons: change logon /enable
Shutdown/Reboot: tsshutdn /reboot, /powerdown /delay /v
Install Application: change user /install
Run Application: change user /execute

NOTE: Before deploying applications with Terminal Server, you must determine which applications are ideal candidates for hosting in your organization, and determine if those applications will work well in a Terminal Server environment.

1 comment:

  1. You DO NOT need EE for TS!
    It will run with STD as well !
    This is a common mistake made by many people.