Sure, @jenieze Definitely interested to know whether it helps you or not.
Originally we had a configuration profile setup for each payload, on the advice of our jump start tech. So we had one profile that contained a Security payload, and another that contained a Login. I revoked both of these first, and then issued a new profile with the combined payloads (as mentioned by several others). The profile looks like this:
This alone was enough for some clients, and seems to have been all that was necessary for most in this thread. But in our environment we also had run a script in a separate policy, once per computer. Additionally, after both updating the profiles and running the script some clients had to reboot before the settings took effect.
Someone with more scripting experience could easily do a better job, but here's the script I used:
#!/bin/bash
#
# get current logged in user
loggedInUser=$(python -c 'from SystemConfiguration import SCDynamicStoreCopyConsoleUser; import sys; username = (SCDynamicStoreCopyConsoleUser(None, None, None) or [None])[0]; username = [username,""][username in [u"loginwindow", None, u""]]; sys.stdout.write(username + "
");')
#
# Set screen lock delay preference for user to 0 seconds
defaults write /Users/$loggedInUser/Library/Preferences/com.apple.screensaver.plist askForPasswordDelay -int 0
#
# change ownership of preference back to user
chown -R $loggedInUser /Users/$loggedInUser/Library/Preferences/com.apple.screensaver.plist
After all of these issues related to lock screens, screen saver times, sleep times etc, I have decided to simply diable the setting altogether. Not worth the trouble at my company because we dont have a top-down mandatpry policy for lock screens (we are not bound by SOX or HIPPA etc).
I have unchecked the setting "Require password X after sleep or screen saver begins" in the Security & Privacy Payload, and I have unchecked the setting "Start screen saver after X" in the Login Window Payload, but my end users are still complaining that they still cant disable/change these settings.
Screenshot below clearly shows the setting is no longer enabled on the JSS, but the clients are still prompted for passwords at 5 seconds. Apparently this is making users grumpy.
I just want to punt on this particular Profile. Not worth the energy and time to babysit it.
If I nuke the entire Profile (delete it from the JSS) will it remove itself from all managed Mac systems?
@prbsparx how do you have your configuration profile set for the screen saver?
I have a configuration profile with two payloads: Login Window and Security & Privacy
I'm also on 9.96 and ours its working fine. (our macs are on 10.11.x and 10.12.x)
