Article ID: 192794 - View products that this article applies to.
This article was previously published under Q192794
Microsoft Windows NT System Policy settings are applied when a user or a computer account is a member of a Windows NT domain. By comparison, Group Policy settings are applied when a user or a computer account is a member of an Active Directory directory service domain. With Microsoft Windows NT Server 4.0 Terminal Server Edition, you may want to apply System Policy settings to affect users who log on to the terminal server through the console or through the Terminal Server client.
The procedures that are described in this article do not apply to client computers that are running Microsoft Windows 2000, Microsoft Windows XP Professional, or Microsoft Windows Server 2003 in some conditions. System Policy settings are used to configure client computers that are running Windows NT 4.0, Microsoft Windows Millennium Edition (Me), and Microsoft Windows 98. However, in a Windows 2000 network or in a Windows Server 2003 network, you must use Group Policy settings to configure and control computers that are running Windows 2000, Windows XP Professional, or Windows Server 2003. System Policy settings are different from Windows 2000 Group Policy settings in that they overwrite registry settings on the client computer with persistent changes. This behavior is known as "tattooing."
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
When you use System Policy settings for client computers that are running Windows 2000, Windows XP Professional, or Windows Server 2003, consider the following guidelines:
To implement a System Policy setting to affect all Terminal Server users who log on to the console or through the Terminal Server client, follow these steps:
The settings in this procedure modify the following path in the registry:
Subcategory: System Policies update
Selection: Remote update
Description: Controls how policies are applied to a Windows NT 4.0-based computer. With UpdateMode set to 1 (Automatic, the default), Windows NT makes a connection to the Netlogon share of the validating domain controller in the user's context and then checks for the existence of the policy file, NTconfig.pol. With UpdateMode set to 2 (Manual), Windows NT reads the string that is specified in the NetworkPath value and then checks that path for the existence of the policy file (in this case, the policy file name should be included in the NetworkPath value). With UpdateMode set to 0 (Off), a policy file is not downloaded from any system. Therefore, it is not applied.
Note The UpdateMode registry entry only applies for the Windows NT 4.0 policy. For members of an Active Directory forest, the UpdateMode registry entry is ignored, and instead, the Group Policy settings that are configured in Active Directory are applied. To gain the same effect as using the UpdateMode entry, you can use a GPO Loopback policy.
Collapse this tableExpand this table
For additional information about using a GPO Loopback policy, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260370/EN-US/ )How to apply Group Policy objects to Terminal Services servers
For additional information about how to use System Policy settings in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/318753/ )How to create a System Policy setting in Windows 2000
Article ID: 192794 - Last Review: October 30, 2006 - Revision: 4.3
Contact us for more help
Connect with Answer Desk for expert help.