Windows 10 pro lock screen wallpaper4/18/2024 However - it also immediately switched from my selected wallpaper set in focus to the original chunky font set! It has swapped sets at other times while working on this issue, but unfortunately, I can't be specific - particularly since I didn't realize that was what was occuring. It goes on (and, although doesn't always give you the quick notification at the bottom of the home screen, the crescent is displayed above) but often does NOT go off! While on, apparently it chooses to black out the wallpaper selection, which I hate, but this morning, for the first time, it disabled itself on schedule. (Kept the orginal unwanted set just in case, as it would be easier to simply modify than going back to wallpaper and starting over in the event it disappeared.ĭND malfunctioned immediately following upgrade. I had also created wallpaper for lock screen/home screen, and edited from chunky font for time display to thinner, obviously selecting the latter for use. Has worked for years until upgrading from 15.7 to 16.1 on Friday. I do not use Bedtime to schedule DND, but rather simply have it scheduled as DND: On from 8:00 p.m. msi, and thus no longer in use.I am experiencing all the same things already mentioned, but in my case, it may (or may not) be related to Do Not Disturb. msi makes it really easy to know exactly which files are installed, and automatically cleans up old files which are no longer a part of the. If management ask me how many devices have gotten the new wallpaper / lock screen images installed, I can give them exact numbers coming from reporting in ConfigMgr.I build the MSI using Advanced Installer, and the configuration needed here, is super straightforward: As usual, this is taken directly from my own production device. Notice I do something similar for our screensaver (that might turn into another blog post).ĭon’t mind me obfuscating some business applications. This can obviously be done with Intune as well. I deploy the source files via Configuration Manager, packaged as an. The DesktopImageStatus and LockScreenImageStatus values are defined as following (so this will be a place to look, if something is not working as expected): Once the policy has applied to your device, you will see your configuration made above, create entries in following location in the registry:Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP When done configuring above, you have a device configuration profile similar to below illustration, which can be assigned to your devices: This is not entirely necessary or required, and can be a local source too if configured like so: file:///C:/Windows/wallpaper.png Notice how the tooltip suggests that this should be a https source. This is not entirely necessary or required, and can be a local source too if configured like so: file:///C:/Windows/lockscreen.png Now, transitioning the lock screen and desktop wallpaper policy to Microsoft Endpoint Manager is easy, and obviously takes place in the Microsoft Endpoint Manager admin center: Ĭreate a new device configuration profile (Device restrictions) for Windows 10:īrowse to the Locked Screen Experience options. Also notice this is a user configuration: Notice that this is a computer configuration:īelow is the illustration, also taken directly from my production environment, where the desktop wallpaper policy no longer is configured. Lock screen imageīelow is the illustration taken directly from my production environment, and while still configuring something with group policy in this area (yikes), the lock screen policy is no longer configured. When coming from group policy, configuring lock screen image and desktop wallpaper, this is respectively done for the computer (computer configuration) and the user (user configuration), and would typically require 2 Group Policy objects (unless mixing user and computer configurations, but that’d be a mess in my opinion). The process made up this short blog post. This time though, I was stubborn and insisted on moving away from Group Policy and do it with Intune. I’m regularly asked to change our desktop wallpaper and lock screen images, and when things needs to be done in a hurry, you usually stick to the easy solution. I assume most hybrid (co-managed) environments still look towards Group Policy when doing this, because it’s easy and what we’ve always been doing. This is something I currently just have done myself, in our own environment, and while it’s neither super technical nor advanced, then I figured it deserved some attention regardless.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |