Hi @Kumarasinghe,

The majority of Development’s focus is on the 9.x series; there may be functionality updates to the 8 series to account for new iOS releases, but from the looks of it, there will likely not be any major feature additions, or bug fixes as the main focus is now on the 9 series.

It’s very unlikely that any defects remaining or new defects found in the 8.x series will be addressed. If a defect or issue affects both the 8 and 9 series, it will be fixed for the 9 series, but most likely not for the 8 series.

Amanda Wulff
JAMF Software Support

We were seeing this a while back, but it seems to be showing up again with Casper 9.32 and 10.92 and 10.9.4 clients. I saw it today in a lab of newly imaged machines and it started happening again on a few machines since upgrading to Casper 9.32.

Where is see it usually happening is when logging in to OD accounts.

The solution from @rtrouton][/url to run this seems to get around it.

defaults write /Library/Preferences/com.apple.mdmclient BypassPreLoginCheck -bool YES

But is there a downside to that ?

@rcorbin

Disabling the pre-login check causes any pending profiles that contain user-level managed preferences not to be applied until the following login.

So @rtrouton you are saying when I run :

defaults write /Library/Preferences/com.apple.mdmclient BypassPreLoginCheck -bool YES

It just kicks the the can out for applying user-level profiles out till the next log in ?

So after that they still apply ? Just worried that it disables installation of those profiles entirely and permanently.

I'm also concerned about the behavior of @rtrouton 's script. Logically, if you set BypassPreLoginCheck to TRUE, it's not EVER going to install user level files, because on each reboot/login this preference is read and pre-login-check is bypassed.

Unless there's something in there I just don't see...

Ive been testing configuration profiles in a new environment.
JSS-9.51
Effecting Clients - 10.9.4 and 10.9.5 (AD managed mobile accounts)
*The below issues does not seem to occur at every login.

The message Updating managed settings appears for ~25 seconds then message appears below saying connecting to server “companyjss” followed by Processing server request “ProfileList” and then logs in…

Im also interested in a fix. @rtrouton Can you confirm the questions from @mclinde and @rcorbin ?

I'm not using user-level profiles (one reason why using this fix has worked fine for me.) Unfortunately, I can't confirm or deny whether or not those profiles apply with this fix in place.

we've got this too. Was it addressed in 9.52?

@jwojda if you see the answer above, Apple advised that this is not a bug & is working as expected.

it's just strange that it started happening after 9.51/9.52 again, and only on the 10.9.4 and 10.9.5 clients.

I've noticed the same thing on AD-bound machines running 10.9.5. We don't currently use Casper. Have tried RTrouton's fix, but this doesn't seem to have any effect. Annoying.

I don't think this is anything to do with AD. We actually mainly see this in Open Directory bound machines. We have some AD as well, but I don't think I see it as much there. Where this becomes very annoying is when you have a whole lab of users (30) getting this message when they log in. Haven't really rolled out the @rtrouton fix on mass as I'm worried it is going to disable applying profiles for good.

JSS 9.5 with early 2014 Macbook Air running 10.9 are seeing this issue also.

+1, I went from 8.73 and had this issue. Then upgraded to 9.31 and it went away. Now at 9.52 and OS X 10.9.5 it's back.

This behavior is showing in 10.10 and 9.6.1. Just started playing with it this week and found it when off network.

EDIT: That resolution was for different issue.

For the "Updating managed settings" dialog, I was able to resolve by creating a policy to re-install the quick add package.

Just wanted to advise that we're seeing this on 10.10 too. But happens post login.

Pretty infrequent, but generally when logging in as a new account & it's then pulling down the user level configuration profiles.

@ Johnny.Kim response, yes this worked for us as well! Thanks so much!