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
#WINDOWS LOCK SCREEN WALLPAPERS WINDOWS#
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 kommentar(er)
