[THIN] KB: Windows 2000 Terminal Services Issues in an Active Directory Domain Environment

  • From: "Jim Kenzig http://ThinHelp.com" <jkenzig@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Mon, 19 Dec 2005 16:57:49 -0800 (PST)

http://support.microsoft.com/default.aspx?scid=kb;en-us;250776
Windows 2000 Terminal Services Issues in an Active Directory Domain Environment
View products that this article applies to.
Article ID:250776
Last Review:December 14, 2005
Revision:3.0

This article was previously published under Q250776
On This Page
SUMMARY
MORE INFORMATION
 Installing Terminal Services on a Domain Controller
 Installing Terminal Services on a Member Server
  Application Server Mode
  Remote Administration Mode
 Active Directory Users and Computers
  Terminal Server Profile Path
  Terminal Server Home Folder
  Roaming Profiles
 User Profile Path and Terminal Server Profile Path
  User Profile Path
  Terminal Server Profile Path
 Home Folders
  Terminal Server Home Folder
 Terminal Server Connection Configuration
  User Rights
 Terminal Server Licensing
  Terminal Server Licensing Service
 Terminal Services Licensing Tool
 Citrix MetaFrame Add-on Product
 Terminal Services Client Options
  Supported Clients
  Independent Computing Architecture (ICA)
 Terminal Services Tools
  Included with Windows 2000 Server
 Benefits of Using Terminal Services
APPLIES TO

SUMMARY
Windows 2000 Terminal Services provides increased functionality for Windows 
2000 domain environments, and affects all aspects of the domain environment. 
This article describes the affected areas, and provides links to Microsoft 
Knowledge Base articles that contain specific troubleshooting steps for those 
areas. 
Back to the top

MORE INFORMATION
You can install Terminal Services for Windows 2000 during Windows 2000 Setup, 
or at any time thereafter. Windows 2000 server administrators can enable or 
disable Terminal Services by using the Add/Remove Programs tool in Control 
Panel. For additional information about how to install Terminal Services, click 
the article number below to view the article in the Microsoft Knowledge Base: 
222992 (http://support.microsoft.com/kb/222992/EN-US/) Windows 2000 Terminal 
Services Toggle Functionality 
Back to the top

Installing Terminal Services on a Domain Controller
When you enable Log on Locally on a domain controller that is running Terminal 
Services, this feature is also enabled at the console of all domain controllers 
for this domain, and can be accessed by all Terminal Services clients. Log on 
Locally is described later in this article in the User Rights section. 
Back to the top

Installing Terminal Services on a Member Server
Windows 2000 Terminal Services is designed to run a variety of Microsoft 
BackOffice programs. The following modes are available in Terminal Services: 
Application Server Mode
âUsers are able to connect to the Terminal Server, and functionality is 
similar to Windows NT 4.0 Terminal Server.
âRequires Terminal Server Client Access Licenses (CALs).
âCitrix MetaFrame can be installed for user connections by Independent 
Computing Architecture (ICA) clients.

Remote Administration Mode
This mode permits administrators to remotely administer a Terminal Server 
through a session. âTwo concurrent connections are available for server 
administration, and Terminal Services clients are unable to run programs.
âCitrix MetaFrame is not feature complete.
For additional information about Terminal Services modes, click the article 
number below to view the article in the Microsoft Knowledge Base: 
243212 (http://support.microsoft.com/kb/243212/EN-US/) Determining the Mode of 
a Terminal Services Server 
For additional information about changing Terminal Services modes, click the 
article number below to view the article in the Microsoft Knowledge Base: 
238162 (http://support.microsoft.com/kb/238162/EN-US/) Change Between Remote 
Administration and Application Server Mode 
For information about how to use Terminal Services for remote administration of 
the Windows 2000 Server family, view the following Microsoft Web site: 
http://www.microsoft.com/technet/prodtechnol/win2kts/maintain/tsremote.mspx 
(http://www.microsoft.com/technet/prodtechnol/win2kts/maintain/tsremote.mspx)
For additional information about how to add Server Operators to the list of 
available logons, click the article number below to view the article in the 
Microsoft Knowledge Base: 
253831 (http://support.microsoft.com/kb/253831/EN-US/) Remote Administration of 
Terminal Services by Non-Administrators Accounts 
NOTE: By default, only the administrators group has remote administration 
permissions. For additional information about the performance impact of remote 
administration, click the article number below to view the article in the 
Microsoft Knowledge Base: 
243213 (http://support.microsoft.com/kb/243213/EN-US/) Impact of Running Remote 
Administration on a Terminal Server 
For additional information about installing MetaFrame in remote administration 
mode, click the article number below to view the article in the Microsoft 
Knowledge Base: 
238353 (http://support.microsoft.com/kb/238353/EN-US/) MetaFrame 1.8 Installs 
on a Remote Administration Mode Terminal 
NOTE: Remote administration mode only permits two concurrent connections and 
does not permit a Terminal Server to go into Install mode for program 
installation. 
Back to the top

Active Directory Users and Computers
Terminal Server Profile Path
Used for profiles while in Terminal Server Edition (TSE), and for non-TSE 
profiles. 
Terminal Server Home Folder
Home folders are used to store user data in a multiple-user environment. Local 
profiles are created in the x:\Documents and Settings\Username folder on the 
Terminal server, where Username is the user logon name.

It is not recommended for Clustered Terminal Services by Network Load Balancing 
or with Citrix MetaFrame add-on, which is described later in this article. This 
can also fill up the small system partition and not utilize the large data 
partitions.


Roaming Profiles
Terminal Server Profile Path is used for roaming profiles only while in TSE, 
and also works for clustered Terminal Server. You can select a server to house 
roaming profiles that can be accessed by any Terminal Server. 
Back to the top

User Profile Path and Terminal Server Profile Path
User Profile Path
âAvailable for both Terminal Server and Windows NT Server.
âAvailable for Windows 2000 Professional desktops that have the same desktop 
settings whether they are using a Terminal Services session or a Windows 2000 
Server and domain logon.

Terminal Server Profile Path
âThe roaming profile is for Terminal Services use only.
âWorks for Microsoft Windows 95 and Microsoft Windows 98 clients, or other 
desktops that need a roaming profile that stores their virtual Windows 2000 
Professional user settings.
For additional information about roaming profiles, click the article number 
below to view the article in the Microsoft Knowledge Base: 
243535 (http://support.microsoft.com/kb/243535/EN-US/) Terminal Services Client 
Roaming Profile Is Overwritten 
Back to the top

Home Folders
Home folders store user data in a multiple-user environment. 
Terminal Server Home Folder
System Policies: Local TSE and Domain Policies âLocal policies are applied 
when you work on that Terminal Server only.
âDomain policies are applied whenever the user logs on, and they are stored 
in the SYSVOL share on the Windows 2000 domain controllers.

Back to the top

Terminal Server Connection Configuration
This is the system-wide user interface settings for RDP-TCP and ICA-TCP 
Security tab has Permissions, and it can override Connection Permissions 
settings in User Manager for Domains. This is often overlooked due to the 
standard Windows NT Server troubleshooting on User Manager for Domains. 
User Rights
"Access this Computer from Network" is needed to access the Server outside of 
Terminal Server sessions for file and print sharing.
For additional information about the Log on Locally feature, click the article 
number below to view the article in the Microsoft Knowledge Base: 
247989 (http://support.microsoft.com/kb/247989/EN-US/) Terminal Server Clients 
Cannot Log on to Domain Controller 
234237 (http://support.microsoft.com/kb/234237/EN-US/) Assign Log On locally 
Rights to Windows 2000 Domain Controller 
Back to the top

Terminal Server Licensing
License Manager tracks domain licenses and other Windows 2000 servers. 
Terminal Server Licensing Service
If this is not completed, you may have profile issues. If no licenses are 
available, the user is able to log into the domain but does not load TSE local 
profiles.

For information about Microsoft Windows 2000 Terminal Services Licensing, view 
the following Microsoft Web sites: 
http://www.microsoft.com/technet/prodtechnol/win2kts/evaluate/featfunc/tslicens.mspx
 
(http://www.microsoft.com/technet/prodtechnol/win2kts/evaluate/featfunc/tslicens.mspx)
http://www.microsoft.com/windows2000/remove404.asp 
(http://www.microsoft.com/windows2000/remove404.asp)
http://www.microsoft.com/windows2000/remove404.asp 
(http://www.microsoft.com/windows2000/remove404.asp)
For additional information about activating a license server, click the article 
number below to view the article in the Microsoft Knowledge Base: 
237811 (http://support.microsoft.com/kb/237811/EN-US/) Activating a Terminal 
Services License Server Over the Internet 
237801 (http://support.microsoft.com/kb/237801/EN-US/) Windows 2000 Terminal 
Services Requires Licensing Service 

For additional information about locating an activated license server, click 
the article number below to view the article in the Microsoft Knowledge Base: 
239107 (http://support.microsoft.com/kb/239107/EN-US/) Establishing Preferred 
Terminal Services License Server 
232520 (http://support.microsoft.com/kb/232520/EN-US/) Description of Terminal 
Services License Server Discovery 

For additional information about license management for Terminal Services, 
click the article number below to view the article in the Microsoft Knowledge 
Base: 
244749 (http://support.microsoft.com/kb/244749/EN-US/) Licenses Required When 
Using Terminal Services Client Software 
248430 (http://support.microsoft.com/kb/248430/EN-US/) How to Transfer TS CAL 
from One Computer to Another 
For additional information about upgrading from Windows 2000 Terminal Services 
Beta, click the following article number to view the article in the Microsoft 
Knowledge Base: 
248409 (http://support.microsoft.com/kb/248409/) Terminal Services Licensing 
Problems After Upgrade to Release Version of Windows 2000 
248650 (http://support.microsoft.com/kb/248650/EN-US/) Windows 2000 Evaluation 
Version and Terminal Services Licensing 
Back to the top

Terminal Services Licensing Tool
âAn existing Windows 2000 license is used for client desktops that are 
running Windows 2000.
âTemporary licenses for Windows 2000 Terminal Services Client Access License 
is used for clients that do not have a license, and grants them 90 days access 
while licenses are being purchased for non-Windows 2000-based desktop clients.
âTemporary licenses for Windows 2000 license is used for clients that do not 
have a license, and grants them 90 days access while licenses are being 
purchased for Windows 2000-based client computers.
âWindows 2000 Terminal Services Client Access License is used for non-Windows 
2000-based desktop clients.

Back to the top

Citrix MetaFrame Add-on Product
Citrix MetaFrame version 1.8 for Windows 2000 Server is the next generation 
from MetaFrame version 1.8 thin-client solutions for Windows NT 4.0 Server, 
Terminal Server Edition. âServer Clustering for Load Balancing of the 
Terminal Servers.
âInstalls over Terminal Server.
âCitrix Licensing Services can be used as well as Terminal Server License 
Manager.
âPublished programs for users to find and then start.
For more information about Citrix MetaFrame, view the following Citrix Web 
site: 
http://www.citrix.com/products/metaframe.asp 
(http://www.citrix.com/products/metaframe.asp)
Back to the top

Terminal Services Client Options
Remote Desktop Protocol (RDP) is the Microsoft client program that permits 
connections to Terminal Services with or without Citrix MetaFrame. 
Supported Clients
Windows 2000 Server, Windows 2000 Professional, Microsoft Windows NT 4.0 
Workstation, Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows 3.x, 
HP/C clients for Windows CE, and Windows Based Terminals (WBT) with Remote 
Desktop Protocol (RDP) embedded.

Add-ons: âRemote control of a session.
âRemote printer attachment.
âClient clipboard redirector.

Independent Computing Architecture (ICA)
Citrixs client program for Terminal Server with Citrix MetaFrame 

Clients: Microsoft Windows RDP clients, Macintosh, Unix, Novell, OS/2, Linux, 
Microsoft Windows CE, Windows Based Terminals (WBT) with ICA embedded. 

Add-ons: âSupport for several client platforms.
âShadowing.
âRemote printer attachment.
âSound through the channel.
âRemote HDD attachment.

Back to the top

Terminal Services Tools
Included with Windows 2000 Server
For additional information about these tools, click the article number below to 
view the article in the Microsoft Knowledge Base: 
240444 (http://support.microsoft.com/kb/240444/EN-US/) Useful Terminal Services 
Resource Kit Utilities 
243202 (http://support.microsoft.com/kb/243202/EN-US/) Windows 2000 Terminal 
Services Session Management Tools 
Back to the top

Benefits of Using Terminal Services
âYou can use older hardware to run 32-bit programs.
âEfficient management on the server.
âRoaming profiles are easily managed.
âEfficient license management.
âEase of remote administration. 
For additional information about Terminal Services, view the following 
Microsoft Web sites: 
http://www.microsoft.com/technet/prodtechnol/win2kts/default.mspx 
(http://www.microsoft.com/technet/prodtechnol/win2kts/default.mspx)
http://www.microsoft.com/windows2000/remove404.asp 
(http://www.microsoft.com/windows2000/remove404.asp)
For information about program optimization, view the following Microsoft Web 
site: 
http://www.microsoft.com/windows2000/remove404.asp 
(http://www.microsoft.com/windows2000/remove404.asp)
For additional information about issues in a domain environment, click the 
article number below to view the article in the Microsoft Knowledge Base: 
245607 (http://support.microsoft.com/kb/245607/EN-US/) Terminal Server Edition 
Issues in a Domain Environment 
Microsoft provides third-party contact information to help you find technical 
support. This contact information may change without notice. Microsoft does not 
guarantee the accuracy of this third-party contact information.

The third-party products that are discussed in this article are manufactured by 
companies that are independent of Microsoft. Microsoft makes no warranty, 
implied or otherwise, regarding the performance or reliability of these 
products.

Back to the top

APPLIES TO
âMicrosoft Windows 2000 Server
âMicrosoft Windows 2000 Advanced Server
âMicrosoft Windows 2000 Datacenter Server

Other related posts:

  • » [THIN] KB: Windows 2000 Terminal Services Issues in an Active Directory Domain Environment