@rblaas See this from @kitzy

@bentoms

Hi I have seen this article.
So it seems a bug.
I have also tried to force the setting via plist but that did not work for me.

Thanks for mentioning the article

@rblaas

I'm working on the same issue right now.

The kitzy 'fix' does work, but only when there's no Login Banner profile on the device. It seems that profile overrides any settings set by the Security & Privacy profile.

This is with 9.82 and 9.9.

The Security & Privacy profile:
Login Window: Screen Saver Preferences
Ask for Password: True

The Login Banner profile:
Login Window: Screen Saver Preferences
Ask for Password: False

Would really like to see JAMF resolve this. Configuration profiles are how we keep our Macs compliant for SOC and for some of the PCI controls. But with the bugs associated with Configuration Profiles we need to use workarounds and exceptions which auditors really dislike.

We need to start hounding Apple, I am reasonably sure you see the same issue with Apple's profile manager..

The real issue is that profiles need to be one setting per profile, not nested like MCX.

C

I would like to add to this discussion that my problem was actually caused by the configuration profile from Casper.

As it turns out with the login window setting the 'ask for password' is also set. This seem to me like a defect on JAMF side.

A simpel solution is to add the Privacy and security payload. In this payload we can (again) set the 'ask for password' option.

It maybe a simply solution but after testing it doesn't work. To validate that it doesn't work, I created the same profile setting in Profile Manager. I built the profile for the Login Window and Security Settings, downloaded it. Packaged it up, to push to the waiting room then install by command line as part of our imaging process.

Call me when it actually fixed. 9.91

@bpriscott
What do you mean with Downloaded it, packaged it up??

All we do is push the configuration profile to the machines who need it.. And this is done instantly.

So I can only guess we are talking about different issues here.

As my issue was about setting the 'require password' to immediately and my (simpel) solution was working I added this to this discussion.

@rblaas

In a nutshell we create and downloaded the .mobileconfig from Profile Manager, packaged it into dmg and place the file into... /Library/Application Support/JAMF/Waiting Room/

Our first run script right after imaging is...
sudo /usr/bin/profiles -I -F /Library/Application Support/JAMF/Waiting Room/Yourprofilename.mobileconfig

We don't set Privacy here neither... we only do the basics and don't set Logout cause Profile Manager actually does work where Jamf hasn't been for us.

Tested with 9.91 JSS and 10.11.5 latest implementation.

@rblaas forgot to add we found that even though it isn't set in the JSS it was setting it anyway.

@bpriscott maybe this will help?

This is fixed in 9.98:

[D-009503] Fixed an issue where configuring the Login Window payload for a computer configuration profile also caused the Require password immediately after sleep or screen saver begins checkbox in the Security & Privacy payload to be incorrectly enforced.