Microsoft Windows 2000 Terminal Services Domain Issues Support WebCast
Windows 2000 Terminal Services is a good product for bringing users into a domain environment, whether your environment is Windows 2000 Active Directory or a Windows NT 4.0 domain. Proper Terminal Services configuration for the server©s operation mode, user home directories, user
profiles, Terminal Services Licensing, and other domain issues are described in this presentation. Microsoft Knowledge Base articles and Web links complement the material for more information on the domain subjects presented.
Scheduled Tasks Run in the Context of Session 0 with Terminal Services
Microsoft Knowledge Base Article: 255544 - Windows 2000 includes
a Scheduled Tasks tool that you can use to configure many tasks,
including scripts, documents, and programs. Although you can
configure these tasks remotely by using a Terminal Services
session, you cannot interact with the task through a Terminal
Services session when it runs.
Scripted Home Directory Paths Require That Folders Exist
Microsoft Knowledge Base Article: 271657 - You can script home folder and Terminal Services home directory paths in Microsoft Windows 2000. Home folder paths can be scripted by using Active Directory Services Interface (ADSI) to modify the HomeDrive and HomeDirectory properties of a
user account. You can also modify Terminal Services home directory properties using a custom Component Object Model (COM) object that wraps the Windows Terminal Server (WTS) APIs (WTSUserConfigTerminalServerHomeDir and WTSUserConfigTerminalServerHomeDirDrive).
Security Concern with Share-Level Security and Terminal Services
Microsoft Knowledge Base Article: 260853 - Client computers that
are running Microsoft Windows 95 or Microsoft Windows 98 with
password-protected shares (this is known as share-level
security) may pose a security concern with Windows 2000,
particularly with Terminal Services.
Terminal Services Compatibility Scripts Available
Microsoft Knowledge Base Article: 263458 - The "Terminal
Services Application Compatibility Notes" white paper is
available at the following Microsoft Web site:
Upgrading from WinFrame to Terminal Server
Microsoft's guidelines for upgrading Citrix WinFrame versions 1.6 and 1.7 to Windows NT Server, Terminal Server Edition 4.0, preserving both user settings and installed applications. Source: Microsoft.com
Using Terminal Server with Windows Load Balancing Service
Microsoft Knowledge Base Article: 243523 - This article describes how to use Windows Load Balancing Service (WLBS) or Network Load Balancing (NLB)
in Windows Terminal Server.
Using Usrmgr.exe with Windows 2000 Terminal Services on Windows NT 4.0 Domain
Microsoft Knowledge Base Article: 261099 - This article
describes how to use User Manager in Windows 2000 to gain access
to additional user properties that are available for use with
Terminal Services in a Windows NT 4.0-based domain.
Windows 2000 Terminal Services Issues in an Active Directory Domain Environment
Microsoft Knowledge Base Article: 250776 - 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
Windows 2000 Terminal Services Session Management Tools
Microsoft Knowledge Base Article: 243202 - You can use a variety of command-line tools in Windows 2000 Terminal Services to manage a server running Terminal Services. This article briefly describes the Tscon.exe, Tsdiscon.exe, Tsshutdn.exe, Tskill.exe, and Rwinsta.exe
tools, and the purpose they serve in administering a computer
running Windows 2000 Terminal Server
Zero Administration Kit for Terminal Server
The Zero Administration Kit (ZAK) allows system administrators to limit end-user access to system files and unauthorized applications. Source: Microsoft.com