Hey everyone! I’m new to Hexnode UEM and just started managing a bunch of macOS devices (Sonoma OS). I’m trying to enforce a screensaver after 10 minutes of inactivity and make sure a password is required to unlock. I’ve been using a script, but it’s not working, and the end-users can still mess with the screensaver settings in System Settings. Any ideas on how to fix this?
Configure screen saver settings on Sonoma MacsSolved
Replies (2)
Hey @remy-parker ! You can actually get this done with a custom configuration profile. Here’s a configuration profile:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>PayloadContent</key> <array> <dict> <key>PayloadType</key> <string>com.apple.screensaver</string> <key>PayloadVersion</key> <integer>1</integer> <key>PayloadIdentifier</key> <string>com.example.screensaver</string> <key>PayloadUUID</key> <string>D2D53DF4-E764-48BA-ADDA-ADDAF1CFAF4E</string> <key>PayloadDisplayName</key> <string>Screen Saver Configuration</string> <key>PayloadDescription</key> <string>Configures screen saver settings and password requirement.</string> <key>idleTime</key> <integer>600</integer> <key>askForPassword</key> <integer>1</integer> <key>askForPasswordDelay</key> <integer>0</integer> </dict> </array> <key>PayloadDisplayName</key> <string>Enforce Screen Saver and Password Requirement</string> <key>PayloadIdentifier</key> <string>com.example.screensaver.policy</string> <key>PayloadUUID</key> <string>44500351-FCAB-48AB-8998-4704104B9322</string> <key>PayloadVersion</key> <integer>1</integer> <key>PayloadType</key> <string>Configuration</string> </dict> </plist> |
This configuration will lock the screen saver settings so users can’t change them manually. Easy fix 😉
Hello @remy-parker , glad to see you’re jumping in with your questions! @otis’s got it spot on with the configuration profile, and we’ve verified it, so you’re good to go if you want to use that. You can deploy this configuration to your end points via Hexnode’s Deploy Custom Configuration feature.
But here’s a pro tip: Hexnode UEM offers a built-in feature that can address your issue without requiring a custom profile. By using the Screensaver policy, you can enforce a screen saver after 10 minutes of inactivity and require a password for unlocking. This solution is more efficient and eliminates the need to manage custom profiles.
Either way works, though, so feel free to go with whichever you prefer. Hit us up if you run into any issues.
Cheers,
Ben Clarke
Hexnode UEM
-
Expand