A 2000 Server Terminal Server in Application Server Mode that is upgraded to
2003 will take on the Terminal Server role (2003 equivalent of Application
Server Mode), however the the old TSLS can NOT server the new Terminal
Server, as a 2003 TS requires a 2003 TSLS.
Install & activate the Terminal Services Licensing Service
Install your 2003 TSCALs.
If the server is a member server, edit the registry to point the server to
itself for the TSLS.
http://www.workthin.com/tsls2k3.htm
This being said, I'm not a fan of upgrading OS on computers being used as
workstations. Terminal Server fits this category, since it is a multi-user
workstation for all intents and purposes.
I find clean installs provide the best results and remove any questions of
whether a problem was caused by OS upgrade. My normal recommendation for
single TS shop is:
1. Build a test server, even if on workstation class hardware.
2. Install and test your applications.
3. Make users terminal server profiles roaming and propagate them to a
network share.
4. Back-up any data on the terminal server that is not part of user
profiles, and make a server image so you can roll-back if there is a problem
(TS should not hold user data)
5. Do a clean install of the new OS and install applications
6. Restore any data (once again, TS usually do not act as file servers)
7. Users logon and their old profile is downloaded automatically.
In a shop using load balanced servers, i.e. via Citrix MetaFrame, servers
builds are usually automated via image or base OS image + scripted
application install.
Simplay upgrading the OS on a production terminal server hoping everything
will work is a crap-shoot, and something I would never recommend. Always
test first when business interruption is a possibility if things go south.
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com