How to Create and Apply Group Policies in Windows Server

Group Policy centrally configures Windows user and computer settings through Active Directory. To create and apply a policy, make a Group Policy Object (GPO) in the Group Policy Management Console (GPMC), link it to the right domain, site, or organizational unit (OU), configure a setting, then verify it on a pilot client. This example uses a pilot users OU and a desktop wallpaper policy.

Before you start

• Use an Active Directory domain and a domain-joined Windows client with a test user.
• Install the Group Policy Management feature. Your account needs permission to edit GPOs and link them to the selected OU, domain, or site. See Microsoft’s GPMC requirements and procedures.
• Choose a pilot OU containing test users. GPOs link to sites, domains, or OUs, not directly to user objects.
• Store the wallpaper image where target users have read access; a UNC path is suitable for domain clients.

Links, inheritance, precedence, and filtering affect scope. Review Microsoft’s Group Policy scope guidance before linking above the pilot OU.

Create and apply a test GPO

1. Open Group Policy Management

In Server Manager, select Tools > Group Policy Management. You can also search Start on a computer with GPMC installed. Expand Forest, Domains, and your domain to browse its OUs and GPOs.

2. Create and link the GPO to the pilot OU

Right-click the pilot users OU and select Create a GPO in this domain, and Link it here…. This creates the GPO and link together. Because the example uses User Configuration, choose the OU containing the pilot users. A domain-root link may affect a much wider group.

3. Name the policy

Name the new GPO Desktop Wallpaper Policy and select OK. Use a name that identifies its purpose. If you create an unlinked GPO under Group Policy Objects, link it to the target container afterward.

4. Confirm the link and its scope

Select the pilot OU and open Linked Group Policy Objects; confirm the link is present and enabled. If you use Security Filtering, the intended user or group needs both Read and Apply Group Policy permissions. Keep default filtering for an isolated pilot OU, or verify membership and permissions for a pilot group.

5. Open the policy setting

Right-click the GPO and select Edit. In Group Policy Management Editor, open User Configuration > Policies > Administrative Templates > Desktop > Desktop, then select Desktop Wallpaper. Microsoft documents this path in its Windows background configuration guidance.

6. Enable the wallpaper policy

Open the setting, select Enabled, and enter a fully qualified path in Wallpaper name, such as \\fileserver\Branding\desktop.jpg. Confirm users can read the file through both share and file-system permissions. Select OK to save the setting, then close the editor.

7. Refresh policy on a pilot client

Sign in as a pilot user and run gpupdate /target:user /force in Command Prompt. This refreshes user policy and reapplies all settings. See Microsoft’s gpupdate reference. If the wallpaper does not change, sign out and back in, then check access to the shared image.

8. Verify the result

Check the wallpaper, then run gpresult /h "%USERPROFILE%\Desktop\gpresult.html" and open the report. Under Applied Group Policy Objects, confirm the test GPO appears. Microsoft’s gpresult reference explains report options. In GPMC, Group Policy Results shows actual settings, while Group Policy Modeling simulates a rollout.

If the policy does not apply

• Check that the user is in the linked OU and the link is enabled.
• Confirm User Configuration is enabled and filtering grants Read and Apply permissions.
• Review inheritance and link order for conflicts; see Microsoft’s processing guidance.
• Verify users can read the UNC image. For other failures, inspect the Group Policy Operational log and follow Microsoft’s troubleshooting checklist.

After the pilot works, expand the GPO link or security filter deliberately and verify the next user group with the same checks.