On your Windows 2000 Server based network, you create a System Policy file to centrally manage Windows NT 4.0 client computers and their user settings. To ensure that these Windows NT 4.0 systems download and apply the policy from the NETLOGON share, what exact filename must you assign to this System Policy file?

Introduction / Context:
Before Group Policy in Active Directory, Windows NT 4.0 used System Policy files to control user and computer settings. In mixed environments where Windows 2000 Server manages Windows NT 4.0 clients, System Policy files can still be used to enforce configuration settings. For these older clients to locate and apply the policy, the file must have a specific name and be stored in a specific location on the domain controller.

Given Data / Assumptions:

• Windows 2000 Server is acting as a domain controller.
• Client computers are running Windows NT 4.0 Workstation or Windows NT 4.0 Server in client roles.
• You have created a System Policy file and placed it in the NETLOGON share.
• You need to know the correct filename that Windows NT 4.0 clients expect.

Concept / Approach:
Windows NT 4.0 clients search the NETLOGON share at logon for a file named Ntconfig.pol. If they find it, they download and process the policy settings stored in the file. The name is hard coded; using any other filename will prevent the clients from applying the policy. Config.pol is used in some other contexts, but for a Windows NT domain environment with NT 4.0 clients, Ntconfig.pol is the required name.

Step-by-Step Solution:
Step 1: Recall that System Policy for NT 4.0 uses a single policy file for the domain.Step 2: Understand that this file must reside in the NETLOGON share on the domain controller.Step 3: Identify the exact name that NT 4.0 clients look for at logon. That name is Ntconfig.pol.Step 4: Compare this with alternative names. Config.pol, Nt4config.pol and Winntconfig.pol are not recognized by default NT 4.0 client logon processing.Step 5: Conclude that naming the file Ntconfig.pol ensures that Windows NT 4.0 systems will detect and apply the System Policy.

Verification / Alternative check:
Testing with a Windows NT 4.0 client confirms that if the policy file is named Ntconfig.pol in the NETLOGON share, the client retrieves and merges its settings at logon. Renaming the file to any other name prevents the policy from being applied, even if the contents are identical. This behavior is documented in Windows NT 4.0 and mixed mode network deployment guides.

Why Other Options Are Wrong:
Config.pol, Nt4config.pol and Winntconfig.pol are not the default filenames that NT 4.0 clients search for. Even though they may look plausible, the client software is coded specifically to look for Ntconfig.pol. Using these alternative names would mean that the clients never download the System Policy file and no centralized control would be enforced.

Common Pitfalls:
Administrators sometimes confuse filenames from different versions of Windows or rely on informal naming conventions that do not match the client expectation. Another pitfall is placing the file in the wrong share or folder. Remember that both the path (NETLOGON share) and filename (Ntconfig.pol) must be correct for the policy to take effect. Careful attention to spelling and case avoids frustrating troubleshooting sessions.

Final Answer:
The System Policy file must be named Ntconfig.pol for Windows NT 4.0 clients to download and apply it.