We are deploying Windows via SCCM CB in our environment, and have noticed that a Winddeployment no longer displays the custom login/lock screen image unless a user logs in to the computer first.
An administrator has already addressed the issue on Technet in May 2018. There is a problem when deploying Windows 10 version 1803. Susan indicates on that this issue will be fixed in the C/D Patching Weeks. But that won't work in Windows 10 Version 1803. When creating Windows 10 installation images, you can also specify user-specific backgrounds for the logon / lock screen and force displaying such images via group policy ("Force a specific default lock screen and logon image"). Perhaps it safes you some useless troubleshooting. * Re-open the Lock Screen in the Settings app, remove the location you just used, and select your desired backgrounds folder.I post this information for administrators who roll out Windows 10 in enterprise environments. * Make a restarting with Windows 10, and then login your desktop normally. * Go to the right side pane, scroll down to Background option, change slideshow to Album, and then set the folder to C:/windows/web/screen location. * Tap or click on the Personalization category, and select the Lock Screen tab in the left side. * Open the Settings app from your Start menu. If the slideshow is not showing pictures from selected folders on lock screen, you could try the method to fix the issue. The problem seems to happen after the version 1803 update. I disable the “Show lock screen background picture on sign-in screen” option in Settings app, and then it just shows the current accent color.
However, if I press Win + L from keyboard to active it on my Surface Pro 3’s display, the sign-in screen background covers it up and everything is static. Every time the the screen timeout normally in Windows 10, the slideshow plays well with time clock and pictures from selected folders.
0 kommentar(er)
