Deploy Corporate Wallpaper in Intune Using PowerShell and ADMX (Step-by-Step)

This deployment uses two Intune components working together. When you deploy corporate wallpaper in Intune, the most reliable approach splits the job into two parts:

The script should run first so the wallpaper file is already present before the Intune desktop wallpaper policy tries to apply it. This makes troubleshooting much easier because you can verify file delivery and policy enforcement separately.

Many admins initially think they need a different wallpaper for every screen resolution. In most environments, that creates unnecessary maintenance. A better approach is to design one clean 16:9 wallpaper at 3840×2160, let Windows scale it down where needed, and enforce it using a single Intune desktop wallpaper policy.

The real design challenge is not only screen resolution. It is also aspect ratio. A 16:9 image looks right on common screens such as 1920×1080, 2560×1440, and 3840×2160. On taller or narrower screens, Windows may crop or reposition the image depending on the wallpaper style. That is why the safe zone rule matters when you deploy corporate wallpaper in Intune.

The most important part of a successful corporate wallpaper deployment is not only the Intune configuration. It is also the design of the wallpaper image itself. Before you deploy corporate wallpaper in Intune, the image should be reviewed and approved by the right team. In many organisations, the wallpaper is created by a branding, marketing, communications, or creative team, while IT is responsible for deploying it to managed devices.

For that reason, IT should provide a few simple technical requirements before the wallpaper is finalised. The image should use a 16:9 canvas, important content should stay inside the central safe zone, and logos or text should not be placed too close to the edges, corners, or taskbar area. These requirements apply regardless of whether you use the ADMX wallpaper Settings Catalog or any other policy method.

Before building the deployment, confirm the following are in place. This guide covers corporate wallpaper Windows 11 Intune and Windows 10 managed devices using the same two-part method.

Create one clean corporate wallpaper image using a 16:9 canvas. The recommended size is 3840×2160, commonly known as 4K UHD.

Recommended filename format

Use a simple filename with lowercase letters, numbers, and hyphens. Avoid spaces and special characters. This makes both the source URL and the local staged path easier to troubleshoot.

The PowerShell wallpaper staging script needs a direct HTTPS URL to download the wallpaper image. In this lab, the wallpaper source file is hosted from the site-root wallpaper folder:

The PowerShell script below is the first of the two components you need to deploy corporate wallpaper in Intune. This PowerShell wallpaper staging script downloads the wallpaper from the source URL and saves it to a predictable local path under C:\ProgramData. It also validates that the downloaded file looks like a real JPG or PNG image before reporting success.

$WallpaperUrl = "https://anupmoitra.com/wallpaper/contoso-corporate-wallpaper-3840-2160.jpg"
$WallpaperFolder = "C:\ProgramData\Contoso\Wallpapers"
$WallpaperFileName = "contoso-corporate-wallpaper-3840-2160.jpg"
$WallpaperPath = Join-Path $WallpaperFolder $WallpaperFileName
$TempPath = Join-Path $WallpaperFolder "$WallpaperFileName.tmp"
 
try {
    [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
 
    New-Item -ItemType Directory -Path $WallpaperFolder -Force | Out-Null
 
    Invoke-WebRequest -Uri $WallpaperUrl -OutFile $TempPath -UseBasicParsing -ErrorAction Stop
 
    if (-not (Test-Path $TempPath)) {
        throw "Wallpaper download did not create a file."
    }
 
    $FileSize = (Get-Item $TempPath).Length
 
    if ($FileSize -lt 10240) {
        throw "Downloaded file is too small. The URL may have returned an error page instead of an image."
    }
 
    $Header = New-Object byte[] 8
    $FileStream = [System.IO.File]::OpenRead($TempPath)
    try {
        $FileStream.Read($Header, 0, $Header.Length) | Out-Null
    }
    finally {
        $FileStream.Close()
    }
 
    $IsJpeg = ($Header[0] -eq 0xFF -and $Header[1] -eq 0xD8 -and $Header[2] -eq 0xFF)
    $IsPng  = ($Header[0] -eq 0x89 -and $Header[1] -eq 0x50 -and $Header[2] -eq 0x4E -and $Header[3] -eq 0x47)
 
    if (-not ($IsJpeg -or $IsPng)) {
        throw "Downloaded file does not appear to be a valid JPG or PNG image."
    }
 
    Move-Item -Path $TempPath -Destination $WallpaperPath -Force
 
    Write-Output "Wallpaper staged successfully at $WallpaperPath"
    exit 0
}
catch {
    Write-Output "Wallpaper staging failed. Error: $($_.Exception.Message)"
    exit 1
}

Upload the PowerShell wallpaper staging script in Intune as a platform script and assign it to a device group. The script should run in system context so it can write to C:\ProgramData.

Create the platform script

In the Microsoft Intune admin center, navigate to:

📁 Devices → Scripts and remediations → Platform scripts → Add → Windows 10 and later

Name	SCRIPT-WIN-Stage-Corporate-Wallpaper
Description	Downloads and stages the corporate wallpaper under C:\ProgramData for later use by an ADMX wallpaper policy.
Script file	Stage-Corporate-Wallpaper.ps1
Run this script using the logged on credentials	No
Enforce script signature check	No
Run script in 64-bit PowerShell host	Yes
Assignment	Pilot Windows device group

Before creating or troubleshooting the wallpaper policy, confirm that the PowerShell wallpaper staging script in Intune ran successfully and the image exists at the expected local path.

Optional local check on the endpoint

On the target Windows device, confirm the file exists:

Test-Path "C:\ProgramData\Contoso\Wallpapers\contoso-corporate-wallpaper-3840-2160.jpg"

The command should return:

True

After the wallpaper file is staged locally, create a Settings Catalog policy that uses the ADMX-backed Desktop Wallpaper (User) setting. This is the second and final step to deploy corporate wallpaper in Intune: the ADMX wallpaper Settings Catalog policy points Windows to the local image path created by the script.

Step 2: Add the Desktop Wallpaper (User) setting

In the Settings picker, browse to:

📁 Administrative Templates → Desktop → Desktop → Desktop Wallpaper (User)

Desktop Wallpaper (User)	Enabled
Wallpaper Name	C:\ProgramData\Contoso\Wallpapers\contoso-corporate-wallpaper-3840-2160.jpg
Wallpaper Style	Fill

⚠️ Critical detail: Use a normal Windows file path here, such as C:\ProgramData\Contoso\Wallpapers\contoso-corporate-wallpaper-3840-2160.jpg. Do not use a web URL and do not use a file:/// format.

The Intune desktop wallpaper policy uses a user setting, so assign it to a pilot user group. Keep the script and the policy assignments separate because they solve different parts of the deployment.

Recommended assignment flow

1. Confirm the platform script is assigned to the pilot device group.
2. Open the ADMX wallpaper policy.
3. Go to the Assignments tab.
4. Select Add groups under Included groups.
5. Select your pilot user group.
6. Review Scope tags if your tenant uses them.
7. Select Create.

Verify both components separately. A successful Intune desktop wallpaper policy status does not prove the wallpaper file was downloaded, and a successful script status does not prove the wallpaper setting applied for the user.

Endpoint testing is the final validation step when you deploy corporate wallpaper in Intune. Test corporate wallpaper Windows 11 Intune devices and Windows 10 devices separately to confirm the image looks correct on both before broad rollout.

Force a manual sync from the device

If the script or policy has not applied yet, trigger a sync from the Windows device:

Or sync from the Intune admin center:

Most issues when you deploy corporate wallpaper in Intune come from one of two places: the wallpaper file was not staged correctly, or the ADMX policy is pointing to the wrong local path.

Quick local file check

Run this on the target Windows device:

Test-Path "C:\ProgramData\Contoso\Wallpapers\contoso-corporate-wallpaper-3840-2160.jpg"

If the result is False, troubleshoot the script before troubleshooting the ADMX policy.

The following Microsoft Learn pages are useful when validating the components you use to deploy corporate wallpaper in Intune, including the PowerShell wallpaper staging script and the ADMX wallpaper Settings Catalog policy:

The most reliable way to deploy corporate wallpaper in Intune is to separate file delivery from policy enforcement. In this method, a PowerShell platform script stages the image locally, and an ADMX-backed user policy applies that local file as the desktop wallpaper.