@scentsy Did this work as expected prior to 9.93? May or may not be related to:
Known Issues Configuration profiles created in v9.93 with a Security & Privacy payload and a FileVault 2 Redirect payload contain an inactive automatic logout setting.
Ever since JSS 9.90 (?) there have been configuration profile issues. The Login Window may have an improper payload that sets that setting which may conflict with the one from Security and Privacy which then means it is impossible to tell which setting will take priority. I have not heard anything about them fixing that issue but we are still on JSS 9.91.
Also, we recently has the Security and Privacy profile start having a payload that disables iCloud Drive. We changed nothing in the profile but when the JSS randomly decided to re-install all the profiles on a station like it does, that payload it being included.
Fun with configuration profiles.
It has to be some disconnect as to what the JSS thinks should be included and what Apple thinks should be included? It is getting really annoying that you never know what setting will be deployed and is making this job really difficult.
I also do NOT like the solution of making a custom profiles for every setting I want to use. I pay to have the JAMF software to do this for me, waste of money at that point. It has been about 8 months now and there are still problem arising and no definite solutions from Jamf.
Disclaimer: do not know if it will work in your environment.
For now our work around is to create another configuration profile and setting the level to "User Level"
instead of using "Computer Level"
we also have another configuration profile "Security & Privacy" set to "Computer Level"
along with the "Login Window" payload.
and that seems to work for us.
For us is important to have the message Banner and the screen saver to activate "immediately".
Hopefully this workaround/lucky guess works for you.
@Sachin_Parmar I have not done that fix on our new version 9.93; I've done it on our previous version 9.91 and it has worked.
I was going to do that fix, but that's when I decided to test what I've posted, and since it worked for me (at the moment) I'll leave it the way it is.
Thank you for posting the link.
So remember I told you I created two configuration profiles for the screen saver to work “properly” weelllll, it turns out it was causing other issues.
So I contacted the Jamf support and they send me a link (http://www.johnkitzmiller.com/blog/security-privacy-configuration-profile-bug-in-casper-9-82/), I was going to do the custom property list file, but I just set it to “Require password 5 seconds after sleep or screen saver begins” and that worked!
I pushed that configuration (the same one we had, only changed the “immediately” to “5 seconds”).
I had a weird feeling having two configuration profile of the same settings it will cause problems.
So now there’s only one configuration profile (as it should) for the screen saver.
After a few days I notice the screen saver keeps switching randomly to "Ask for password" and it goes back to when the screen saver turns on and when I wake it up it doesn't ask for a password.
I'm on 9.93 JSS and macs running 10.11.6
as I posted on 08/18/16 I tried the suggestion from johnkitzmiller blog and it doesn't work for me.