Setting Desktop Wallpapers Using Group Policy

Overview

Maintaining a consistent desktop background across domain-joined computers is a simple way to reinforce branding and create a more professional user experience.

In my home lab, I use Active Directory Group Policy to copy wallpaper images from a central Synology NAS share to each computer before applying the wallpaper. This approach ensures the image is available locally, reducing reliance on network availability during user logon.

What You’ll Need

Active Directory Domain Services
Group Policy Management Console (GPMC)
A shared folder containing your wallpapers
Domain-joined Windows computers

Step 1 – Create a Central Wallpaper Share

Store your wallpapers on a shared location that all domain computers can access.

Example:

\\SERVER\Wallpapers

In my environment, the wallpapers are stored on a Synology NAS and shared across the domain.

Step 2 – Create a Local Wallpaper Folder

Rather than pointing Windows directly at a network path, I copy the wallpapers to each PC.

Destination folder:

C:\ProgramData\OrderRealm\Wallpapers

Using ProgramData keeps the files available for all users while hiding them from normal day-to-day browsing.

Step 3 – Create a Startup PowerShell Script

Create a PowerShell script to copy the wallpapers.

Example:

$Source = "\\SERVER\Wallpapers"
$Destination = "C:\ProgramData\OrderRealm\Wallpapers"

if (!(Test-Path $Destination)) {
    New-Item -ItemType Directory -Path $Destination -Force
}

Copy-Item "$Source\*" $Destination -Recurse -Force

This ensures any updated wallpapers are copied to the local machine each time it starts.

Step 4 – Create a Computer Group Policy

Open Group Policy Management.

Create a new GPO, for example:

Wallpaper Deployment

Link it to the OU containing your computers.

Tip: I found it more reliable to separate computer settings and user settings into different GPOs rather than combining them.

Step 5 – Configure the Startup Script

Navigate to:

Computer Configuration
 └─ Policies
     └─ Windows Settings
         └─ Scripts (Startup/Shutdown)
             └─ Startup

Add your PowerShell script.

If PowerShell scripts are blocked, configure the execution policy:

Computer Configuration
 └─ Policies
     └─ Administrative Templates
         └─ Windows Components
             └─ Windows PowerShell
                 └─ Turn on Script Execution

Set it to:

Allow local scripts and remote signed scripts

Step 6 – Configure the Desktop Wallpaper

Navigate to:

User Configuration
 └─ Policies
     └─ Administrative Templates
         └─ Desktop
             └─ Desktop
                 └─ Desktop Wallpaper

Enable the policy.

Wallpaper path:

C:\ProgramData\OrderRealm\Wallpapers\wallpaper.jpg

Wallpaper style:

Fill
Fit
Stretch
Centre
Tile

Choose the style that best suits your image.

Step 7 – Apply the Policy

Run:

gpupdate /force

or simply restart the client computer.

After the startup script copies the wallpaper locally, users should receive the configured background when they next sign in.

Troubleshooting

Wallpaper Doesn’t Change

Check:

The GPO is linked to the correct OU.
The user has received the User Configuration policy.
The startup script has successfully copied the wallpaper.
The local wallpaper path exists.

Startup Script Doesn’t Run

Verify:

PowerShell script execution is enabled.
The computer account has permission to access the network share.
The script runs successfully when executed manually.

Review the Event Viewer for Group Policy or PowerShell errors if needed.

GPO Isn’t Applying

Useful commands:

gpresult /r

gpresult /h report.html

These will show whether the wallpaper policy has been applied and if any filters or permissions are preventing it.

Lessons Learned

While building Realm Labs, I discovered that keeping computer configuration (such as startup scripts) separate from user configuration (such as wallpapers and desktop settings) made Group Policy much easier to troubleshoot and maintain.

Copying wallpapers locally rather than referencing a network share also makes logons more reliable, particularly if the network isn’t immediately available during sign-in.

Next Steps

You can expand this setup by using Group Policy to deploy:

Company or home lab branding
Lock screen images
Drive mappings
Folder redirection
Login scripts
Desktop shortcuts
Registry settings

Combined together, these policies provide a consistent and professionally managed Windows environment across your home lab.