Config Profiles - Energy Saver

[bajones]

Anyone tried setting a startup/shutdown schedule in an energy saver payload pushed to a 10.8.2 machine? Every time the profile is installed in a fresh 10.8.2 install on a couple Late 2012 Mac Minis (machine specific build, of course) I can no longer log into these machines. I only get a white screen. I have tested this in a setting where the only thing thats different from a "fresh out of the box and fully updated" install is jamf 8.62 management and this one payload, so no packages or bindings or anything else.

[franton · Accepted solution]

That is the simplest way of doing it. However look up the "pmset" command anyway. Find the right syntax and you can fire it remotely at computers via Casper Remote.

[jacob_salmela]

Interesting. We experienced this issue at two different schools, but they were iMac Intel (Early 2008) running 10.7.5.

We determined the problem was due to the config profiles with an energy saver payload. Our district submitted this information to Apple.

There was a solution that worked for some people (running 10.7.2) found at this post:

https://jamfnation.jamfsoftware.com/discussion.html?id=46

I'll let you know if I find out anything else.

[franton]

We successfully do this for our "out of hours" update policy. It's combined with our energy saver settings. However i'm not sure how you're deploying this. Our deployment is just a script that executes a lot of pmset commands.

There's also a couple of extension attributes with scripts to detect whether the settings are correct or not. This is mated to a series of smart groups looking for a specific setting. As a result if someone goes and changes the settings, our policy resets it back to what it should be.

If you're interested, I can post more details on this tomorrow.

[bajones]

Franton, we are using our JSS to push out a config profile by scoping it to a group of Mac Minis. I was under the impression that jamf uses Apple-provided frameworks in their profile creation tools, so I can only assume the problem is something on Apple's end. The group only consists of 3 computers, so I'm just going to set the schedule by hand.

I was hoping there was a quick fix and I could use the built-in config profiles features of the JSS as they were intended. The issue isn't important enough to warrant me spending time on scripts and extended attributes for 3 computers.

[franton · Accepted solution]

That is the simplest way of doing it. However look up the "pmset" command anyway. Find the right syntax and you can fire it remotely at computers via Casper Remote.

[daz_wallace · Accepted solution]

We have experienced this at two different sites as well as on a CMA course.

Not been able to identify the cause and have, for the time being, used MCXs instead.

Very strange behaviour. There is a file you can delete to fix the issue is this preference file /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist and reboot

[bajones]

Good call, daz_dar. That info might have saved me 5 or 6 reimages. Definitely will remember that plist for the future if the issue is not fixed.

EDIT: Has anyone peeked at the plist that is created when using config profiles instead of the pmset command? I'd be interested to know if it were malformed somehow. Possible Jamf bug?

[daz_wallace]

Looks like it's fixed:

https://jamfnation.jamfsoftware.com/discussion.html?id=6869