Rename-Item $OSDTargetSystemRoot\Web\Wallpaper\Windows\img0.jpg img1.jpg -ForceĬopy-Item $ScriptRoot\img0.jpg $OSDTargetSystemRoot\Web\Wallpaper\Windows -ForceĬopy the files to your MDT Package directoryĬopy the new wallpaper and the PowerShell script to the Scripts directory of your MDT package source files, and update the MDT Package to your distribution points. The script will load some task sequence variables, rename the existing default wallpaper to “img1.jpg”, and copy the new “img0.jpg” into the same directory. Use the following code in a new PowerShell Script, and save it as “Set-DefaultWallpaper.ps1” Save it as “img0.jpg” Create a PowerShell Script The recommended resolution is 1920×1200, which is the same as the built-in default wallpaper. Create a Wallpaperįirst, create your new default wallpaper. I’ve tested on Windows 7 but should also work with Windows 8.1 as it uses the same location for the default wallpaper. This procedure requires MDT-integrated ConfigMgr 2012, and also requires Windows PowerShell to be added to your boot image. Instead, you can change offline during the WinPE phase of the deployment, which bypasses the permissions problem. If you check the security on that file however, you’ll notice that only the “TrustedInstaller” has full permissions to it, so to change it in the online OS requires messing with permissions. It turns out it is simple enough to do, but it requires changing the default wallpaper that comes with windows, which can be found at C:\Windows\Web\Wallpaper\Windows\img0.jpg. Recently I was given an interesting task – set the default wallpaper on new computer builds with ConfigMgr OSD, but don’t lock it such that users can’t change it. Note: For a Windows 10 Version, see this blog instead:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |