Just saw the email that 9.82 is now out. I took a look at the Release notes and it seems like several good fixes made it into this version. A couple that I noted-
[D-009724] When upgrading to a Casper Suite version that uses the new jamf binary location, launch services no longer fail to automatically use the new binary location if the computer loses its connection to the JSS during the upgrade. [D-009686] When upgrading the JSS to v9.8, the “Log out users after” option is no longer enabled by default in the Login Window payload of an OS X configuration profile.
There's also this one, under Deprecations:
• Policy status determined by checking script output for “error” and “fail”—The JSS no longer determines the status of a policy by checking script output for the words “error” and “fail”. As of v9. 82, the JSS now only uses error codes to determine the status of a policy.
Thank you JAMF for finally removing this functionality! I no longer have to worry about policy scripts causing false failures to be logged (once we upgrade that is)
Anything else in the notes that are important fixes for some of you out there?
Has anyone tested Mass Update with the Download Only option? In my testing, a message pops up after the download that says 'iOS 9.2 will begin installing in 10 seconds' for both 'Download Only' and 'Download and Install and Restart', so I don't know what the expected outcome is supposed to be.
I happened to look into the screensaver passcode delay issue this morning, before seeing this post - have y'all actually confirmed that the delay is not being enforced, or are you going off of the Security window?
Reason I ask: I tested by removing the profiles from my machine, which previously showed "Immediately" for passcode requirement - and when I did, the UI defaulted to my old MCX setting which was 5 seconds.
After reapplying the profiles, it never reflected the change in timing – it still said 5 seconds.
However, I then removed the profiles again, changed the time setting to 5 minutes, and saw the UI update accordingly. When I then reapplied the profiles it still said 5 minutes - but when testing actual functionality, it did in fact ask me for a password after only a few seconds when the screensaver kicked in.
So, it appeared to be working but just not reflecting in the UI itself.
I ran the command
defaults write com.apple.screensaver askForPasswordDelay 0
to update the UI so it says “immediately”, reflecting the setting being applied by the profile. If I run the same command with
defaults write com.apple.screensaver askForPasswordDelay 600
The UI updates again - with the Profiles still in place - to show 5 minutes.
tl;dr - The Preferences -> Security UI is basing its timeout setting on the com.apple.screensaver askForPasswordDelay key.
I've attempted the iOS update push a couple of times without success. The logs on the iPads show the following (reversed from logs page into chronological order):
DeviceInformation Yesterday at 6:40 AM
Update Inventory Yesterday at 12:48 PM
AvailableOSUpdates Yesterday at 12:49 PM
ScheduleOSUpdate Yesterday at 12:49 PM
DeviceInformation Today at 6:40 A
iPad is still running 9.1
Little help here?