Skip to main content

We have no managed profiles, no configuration profiles, no policies set at login or log out. What boxes do I need to check or uncheck to make that stupid pop-up window go away and my staff not take 1 to 2 minutes to log into their macs. This is actually ticking me off and its my program! LOL



I have worked with JAMF tech support on this issue 2 different times and they have not been able to tell me what is causing this either.

http://derflounder.wordpress.com/2013/11/13/bypassing-the-mavericks-managed-preferences-login-check/



He has a great article showing how to disable this and what it will cause by doing so. We deploy this as a .dmg and has worked great so far to speed up login greatly. Down to under a minute for logins.


The above link is good info.



There is also a good thread in JAMFNation with a fix : https://jamfnation.jamfsoftware.com/discussion.html?id=8777 and a very thorough post in MacMule: http://macmule.com/2013/10/30/updating-managed-settings-popup-at-login-window/



@rtrouton has a very useful script or pkg in his github repo: https://github.com/rtrouton/rtrouton_scripts/tree/master/rtrouton_scripts/bypass_mavericks_mdm_login_check


This has works wonders for me!



#!/bin/sh

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

@yan1212 thanks for linking my blog (macmule.com)



Apple Support advised this is the new way. So we left it.



But trust @rtrouton to get a way around it!


I'd much rather there be a shorter timeout; I could accept a 5-10 second penalty, but not well over a minute.


@JPDyson, from what Apple advised the message doesn't hold up the login, just shows the progress.


@JPDyson,



I had also requested a way to set a timeout value. As of this time, there isn't a way to set one. The check either runs or the check is bypassed, based on whether the BypassPreLoginCheck key in /Library/Preferences/com.apple.mdmclient is set to true.


Sure, I'm just whining :)


Yeah Apple says that it doesn't hold up the login...But it does.


Yes it's actually horrible I've timed it off network at over 2 minutes, 1 min 40 something seconds was the most on net work! But the scrip seems to have worked! Ran it as a policy on my 10.9 smart group.


Yes it's actually horrible I've timed it off network at over 2 minutes, 1 min 40 something seconds was the most on net work! But the scrip seems to have worked! Ran it as a policy on my 10.9 smart group.