I'm looking to shift our screensaver management from Group Policy to Intune as we move towards cloud-based devices. Currently, we use GPO on an on-prem Active Directory to set screensaver timeouts and point to a folder of images. This setup allows us to easily update images by replacing files on a file share.
For Intune, I'd prefer to manage this at the device level rather than user level, ensuring that the method for updating images is efficient and doesn't require a complete rebuild each time. In my home lab, I've been experimenting and tried a user-scope approach, but it didn't work well on my virtual machine, which is why I'm focusing on device-level solutions now.
Here are some options I'm considering:
- A Win32 app that installs images locally and utilizes supersedence for updates.
- A device configuration profile using the Settings Catalog/Admin Templates to manage timeout and image paths.
- A script or proactive remediation method for updating images.
For anyone who has gone through this migration from GPO to Intune, what are your recommendations for a clean and sustainable solution? What pitfalls should I try to avoid? Appreciate any insights!
3 Answers
Have you thought about using a SharePoint site for your screensaver files? You could keep the screensaver files there and use Intune to sync the folder across devices. Then, apply another Intune policy to set the screensaver on each device from that synced folder. You can even make it read-only for most users except those who need access to update the files.
Honestly, screensavers feel a bit outdated, and Windows 11 primarily uses Lock Screen customization now. You might want to consider if that's more relevant to what you need. However, if the screensaver is for displaying announcements on idle workstations, make sure that's clear in your setup! Here's a great link to help with Lock Screen management in Windows 11: [Microsoft Docs](https://learn.microsoft.com/en-us/windows/configuration/background/?tabs=intune&pivots=windows-11).
You might want to store your images on a share, whether that’s cloud-based or local. Create a seed file for any complex updates. Instead of deploying a Win32 app to drop images directly, consider writing a script that sets up a scheduled task. This task could manage image updates from your share and make changes to the screensaver policy as needed. It sounds tedious but could save you a lot of hassle in the long run!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures