Screen and energy saver settings affecting iCloud

[al_platt]

We have a profile in place that sets the require password immediately option (which seemed to be fixed with 9.9)

However, any machine getting that profile, the iCloud drive option turns off and is blocked.

Has anyone else had an issue with this?

Just caused major problems in a high level meeting!

Thanks

Al

[strider_knh]

Have you checked a station with the configuration profile installed to see what payload is actually being deployed in System Information or the Profile System Preference pane?

In 9.82 there were issues of configuration profiles deploying the wrong payload, this may have carried over from that. We have yet to install 9.9 to check the configuration profile changes.

[al_platt]

Ah, thanks for the info, I wasn't aware of that.

I haven't checked as i removed the profile once i identified it was causing the issue.

I've gone back to a deployed .plist to set instead.

Profile is backed up so when I get time I'll redeploy to a test box and see what's what.

[somnico]

we have the same issue here the profile description says:
do not allow iCloud documents sync - true

but this is no feature to choose or not

[jonnydford]

Noticed this is happening for us too.

Sigh.

Can't go through a JSS upgrade without another Config Profile breaking.

[Parm]

Hey Guys,

We were seeing this on 9.9. We've had individual config policies for Security and Privacy and Login Window since early version 9, these set gatekeeper, password after sleep immediately, banner on the login window etc etc. Somehow the setting that allows iCloud Sync was disabled and could not be set to enable on the machine even if it was allowed in the config profile. We were also seeing really high ( >100%) cpu usage on Spotlight and we couldn't click a window to bring i to the front and make it active. @strider.knh We were seeing lots of strange profile settings that didn't tally with the profiles we were deploying.

When we amalgamated these config profile into one profile everything was fixed.

[bentoms]

FWIW, delved into this issue this AM I have posted my findings here.

[Person]

Thank You @bentoms I was just running into this issue with some users. I am not sure why we have not seen it til now but recently came across several users with this issue.