Share via

Windows Configuration Designer Default Backgrounds and Accent Color ppkg not applying

Question

Sunday, April 23, 2017 8:36 PM | 1 vote

I'm running into a issue with some provisioning packages I have created while attempting to force background and colors settings. Using WCD v10.0.15063.0 I have created 2 custom ppkg that includes the following settings:

  • DesktopSettings.ppkg
  •  DesktiopBackgroundAndColors
  •     DeployDesktopBackgroundFile: C:\Backgrounds\DesktopBackgroung.jpg
  •     RegisterDesktopBackgroundFile: DesktopBackgroung.jpg
  •  SetColors
  •     Order: 0 = 15538990
  • PersonalizationSettings.ppkg
  •  Personalization 
  •     DeployDesktopImage - C:\Backgrounds\DesktopBackgroung.jpg
  •     DeployLockScreenImage - C:\Backgrounds\LockScreenBackgroung.jpg
  •     DesktopImageURL - C:\Backgrounds\DesktopBackgroung.jpg
  •     LockScreenImageURL - C:\Backgrounds\LockScreenBackgroung.jpg

I have deployed both the above packages individually on a freshly installed (non-custom, straight from iso) Windows 10 Pro, v1703 workstation and the configurations don't take affect. I can see the jpg files do get copied to "C:\Windows\Web\Wallpaper", but the background does become the default background or even in the selection menu under Settings -> Personalization -> Background or Colors, for the Current User (after reboot) or Newly created local user accounts.

To apply the ppkg's I have manually clicked to install and I have used PS Commands to install with logging (Add-ProvisioningPackage -Path C:\PersonalizationSettings.ppkg LogsDirectory Path c:\Temp). Logging shows clean installs, so this makes me believe the issue is around the configured settings within the ppkg's and that there is something missing (like another setting to force the configurations to take effect on the workstation).

Any ideas on if I'm doing something incorrect or if this is supported?

Many pre-thank's for all that try assist!!!

All replies (8)

Tuesday, April 25, 2017 7:46 AM

Hi ,

Does this issue only occur with Windows 10 version 1703?
Did this method work in previous version of Windows 10?

Best regards

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, April 26, 2017 11:06 AM

I have tested this on version 1703 and 1607, both Enterprise and Pro editions and these ppkg's do not work on either.

Wednesday, September 6, 2017 8:56 AM

I'm running into the exact same issue, has anyone been able to resolve this? 

Monday, November 13, 2017 12:59 PM

Can´t get lockscreen and desktop image deployed too....

Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

Friday, January 26, 2018 3:35 PM

I think the Url setting has to point to where the wallpaper will reside on the computer, have you tried with 

  • DesktopImageURL - C:\Windows\Web\Wallpaper\DesktopBackgroung.jpg
  • LockScreenImageURL - C:\Windows\Web\Wallpaper\LockScreenBackgroung.jpg

Sunday, January 28, 2018 10:22 AM

I think the Url setting has to point to where the wallpaper will reside on the computer, have you tried with 

  • DesktopImageURL - C:\Windows\Web\Wallpaper\DesktopBackgroung.jpg
  • LockScreenImageURL - C:\Windows\Web\Wallpaper\LockScreenBackgroung.jpg

Let me think about this. Then I would have to somehow copy and overwrite my wallpapers to exact same location with same name. 

Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

Wednesday, May 16, 2018 10:36 AM

Hi, 

DeployDesktopImage and DesktopImageURL are settings provided by "Personnalization CSP". This configuration provider is not enabled by default. In order to enable it, you also have to enable the following settings in your provisioning package :

  • SetEduPolicies = TRUE 

You can easily find these settings by using search bar in ICD or you can find it Under SharedPC \PolicyCustomization\SetEduPolicies

regards, 

Régis

Thursday, November 1, 2018 2:57 PM

I just made this work on my 1809 test kiosk machine after a bit of banging my head against the wall. I had two simple issues that, had I read the documentation, I should have avoided. Everything I needed was here:

/en-us/windows/configuration/wcd/wcd-personalization#deploydesktopimage

To make it work, you will need two separate files, one for the desktop and one for the lock screen (even if they are the same image they need separate files with different names). Then in WCD, in the "DeployDesktopImage" node browse to where the file is stored on your workstation (not the kiosk). I'm my case it was c:\files\desktopimage.jpg. In the "DesktopImageUrl," enter just the file name in the field (desktopimage.jpg). You can repeat this configuration for the lock screen image with a different file.

In my experience, the SetEduPolicies does not need to be configured.

The reason for this is that all files copied by the Provisioning Package are copied to the same folder and the Provisioning Package references automatically when it is executed (hence the lack of file paths in the ...ImageUrl settings). The Deploy...Image setting tells where WCD can find it on your local machine. This is added to the .ppkg during the build process and copied to the device at runtime.

This copy process is explained, albeit in a different context, in this document. Refer to item 4 in the remarks section at the end of the document.

/en-us/windows/configuration/provisioning-packages/provisioning-script-to-install-app#remarks 

I hope this helps!