![]() Xcopy "%PathToM圜ustomDesktop%" "%systemroot%\Web\Wallpaper\Windows\img0.*" /f /y Xcopy "%PathToM圜ustomLockscreen%" "%systemroot%\Web\Screen\img100.*" /f /y Rename %systemroot%\Web\Wallpaper\Windows\img0.jpg img01.jpg Rename %systemroot%\Web\Screen\img100.jpg img200.jpg Rename %systemroot%\Web\4K "4K - renamed" :: Remove previously renamed folder (for updates) %systemroot%\system32\icacls.exe %systemroot%\Web\*.* /Grant System:(F) /T %systemroot%\system32\takeown.exe /f %systemroot%\Web\*.* /R CMD script that includes: :: Modify default desktop/lockscreen images (requires taking rights) Toward the end of an "imaging" task sequence and also toward the end of an upgrade task sequence, I run a. I don't know if this is the best solution, but it's what I've been able to get working given that nobody else (especially Microsoft) seems to be interested in configuring default UI adjustments (as opposed to forced UI settings via GPO). This shouldn't be that hard! And, someone else must be doing this! All the other adjustments to the default registry file remain for new profiles, but not that one. ![]() That works in that after the TS is done, the Default\NTUSER.DAT file does have the correct path to the custom image, however users have the default path, C:\Windows\Web\Wallpaper\Windows\img0.jpg in their HKCU\Control Panel\Desktop Wallpaper registry key. REG ADD "HKLM\DefaultUser\Control Panel\Desktop" /v "Wallpaper" /d "%ProgramData%\MySettings\CustomDesktop.jpg" /t REG_SZ /f ![]() I am already loading, modifying and unloading the Default\NTUSER.DAT file in order to set some other default options, so I just added an additional line: REG LOAD HKLM\DefaultUser %SystemDrive%\Users\Default\NTUSER.DAT Thus, I figured I have to use a different method of setting a default, custom desktop image. They point to the custom image, but use the Windows image (from some hidden, unknown source).Ĭlearly, Microsoft is doing something funky, and I can't resolve it. This is true for existing profiles and for new profiles. The settings window will show a mini version of what I expect to see, but the actual desktop is of the default image. However, the desktop background for any user is the default, "blue-light window" picture. I run the same rename/replace script as part of the upgrade TS, and when it is done, the correct files sit where they should. Windows feature upgrades have recently started breaking that model. That has worked well (and continues to work). That said, what I have been doing for the last few years is renaming the normal default desktop image at %systemroot%\Web\Wallpaper\Windows\img0.jpg and then dropping in the custom image with that original name. I also can't use the user side of a GPO with Loopback, so setting the Windows Theme and/or a login script is not an option. They should have the option to change it, so I do not want to use Group Policy. When I "image" a computer using a Task Sequence, I want new users to have a default custom desktop image.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |