You must deploy a custom registry setting to all users via Group Policy with minimal effort. Which method integrates the custom setting into a Group Policy Object (GPO) for centralized management?

Introduction / Context:
Group Policy in Windows 2000 exposes registry-based policy settings via Administrative Template (ADM) files. If a required setting does not exist in the default templates, you can author a custom ADM that writes the necessary registry values under the policy-managed branches, and then link it in a GPO for consistent, centralized deployment to users or computers.

Given Data / Assumptions:

• Need to configure a specific registry value for all users.
• Desire: leverage Group Policy, not per-machine scripting.
• Environment: Windows 2000 domain.

Concept / Approach:

ADM templates define UI elements in the Group Policy Editor and map them to registry locations. By writing a simple ADM with CATEGORY/POLICY/ACTIONLIST elements that set or remove the target keys, administrators can manage the setting with checkboxes and ensure it applies during policy refresh.

Step-by-Step Solution:

Verification / Alternative check:

Examine the registry on a client after policy application to confirm the value is present; RSoP can show that the GPO applied.

Why Other Options Are Wrong:

INF security templates focus on security settings, not arbitrary user registry preferences.

MSI deployment is for applications, not raw registry keys (unless wrapped in a transform/custom action, which adds complexity).

RIS is for operating system deployment, not ongoing policy enforcement.

None: A direct ADM-based solution exists.

Common Pitfalls:

Placing settings outside the policy branches (which may not revert); forgetting to remove 'Only show policy settings that can be fully managed' when using custom ADM.

Final Answer:

Create a custom ADM template and add it to the GPO