PersonalizationDesktopImageStatus failed on 14 clients

Fred Fulford 36 Reputation points
2021-02-18T16:08:58.06+00:00

We deploy a new desktop wallpaper and lock screen image every month to to all Windows devices in our estate via a configuration profile called “Win10_Device_Restrictions - V1.1”, using the settings Locked Screen Experience > Locked screen picture URL (Desktop only) and Personalization > Desktop background picture URL (Desktop only).

69560-url.png

This works on the vast majority of clients, but is failing on some (around 14). Investigation of these clients shows that Deployment Status of Win10_Device_Restrictions - V1.1 shows failed, and when drilling down it shows that every Setting has succeed except for PersonalizationLockScreenImageStatus and PersonalizationDesktopImageStatus.

69635-failed.png

69671-desktopfailed.png

All devices are running Windows 10 Enterprise 20H2 and are fully up to date.

Multiple reboots have not forced the wallpaper and lock screen image to update, we have tried making a change to the policy to push it back out but these two settings are still failing for these clients. PersonalizationCSP registry key on failing client devices shows the correct URLs for both images (as defined in the configuration profile) but the DesktopImageStatus and LockScreenImageStatus are both showing a value of 2 (Download or copy in progress)

69681-reg.png

Have checked permissions,

Microsoft Intune Configuration
Microsoft Intune Configuration
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Configuration: The process of arranging or setting up computer systems, hardware, or software.
1,734 questions
{count} votes

6 answers

Sort by: Most helpful
  1. Admin: Fred Fulford 0 Reputation points
    2023-05-02T06:20:21.15+00:00

    Sorry matey, no such luck. We ended up building an alternative method using a BITS transfer from block storage and scheduled tasks, I'm not entirely sure of how it was set up, but it's still not 100%

    0 comments No comments