Since the B patch was on Septem(when security updates are rolled out), the C patch comes a week later, on September 18, 2018. In the sense of 'we love cryptic abbreviations', 2018.9C stands for a fix in 2018, the month of September (9) in C-Patch week. Yay, looks like Windows 10 v1803 will be fully functional just in time for Windows 10 v1809 :) This is also mentioned within the following tweet: On AugJason_E from Microsoft announced that a fix for 2018.9C is planned. Meanwhile we are in September 2018, the Windows 10 V1809 is just around the corner and the Technet thread is now well filled with frustrated admins waiting for a fix. Under Computer Configuration -> Policies -> Windows Settings -> Scripts (Startup / Shutdown).Double click it. The problem was described extensively in the Technet forum thread and then confirmed several times by other users.Īt the end of June 2018 a Microsoft employee (see the post from Kate Li, from MSFT CSG) noticed this and promised to take care of it. Create a GPO ,Llink it to the OU containing the computers. No matter what background images are placed there and set via group policy, the user only gets a login page with the blue background.Ī user-specific background image is only displayed within the Windows 10 logon page, after a user has logged on to his user account for the first time. This came to light, when rolling out Windows 10 Version 1803 via SCCM. Did the location of the default lock screen change? Or is there another reason that it would not apply until a user logs in?Ĭuriously, as soon as any user logs in, the behaviour returns to normal. The image is displayed after the task sequence concludes on a 1709 deployment, but not on 1803. We are also using the "Force a Default Lock Screen Image" GPO. Our task sequence removes all of the default images from the default location (C:\Windows\Web\Screen) and replaces them with our own, as well as clearing the contents from %ProgramData%\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_Z Instead, the computer displays the solid blue colour associated with a lack of an available image and no Spotlight. 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. I post this information for administrators who roll out Windows 10 in enterprise environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |