+5Hello
We have a company corp wifi (which can access the jss), when the mac logs in and the wifi starts up
I see the above in the jamf.log.
I guess because the wifi is still starting up when the jamf binary is checking for the login policies.
Does anyone have some ideas how i can get the mac to see the jss when the mac logins in and is connected to the corp WIfi?
So the login policies can run?
Thanks
+35@markc0 Can you advise more on how the wireless is configured?
The message might be that the Mac cannot connect to a DNS server to resolve the DNS name of the JSS.
+5Thanks Ben, however i know it can resolve the name if i turn off the wifi and back on again.
My thoughts are that maybe the jamf binary is trying to connect before the wifi has fully started up.
i dont though if there is anyway to delay this
+35@markc0 Not that I know, but what's you're seeing is not common.. so there maybe something in your wireless config to look at.
+5Thanks again Ben, when you say this is not common
do you have a setup whereby when the mac starts up it connects to a corp wifi and is able to run login policies?
Thanks
+5Thanks, with the 802.1x did you have to do anything extra to the macs for this?
like a config profile or something?
+17I've been seeing the same thing too. We are using a 802.1x setup as well. We are using a config profile.
+8We are seeing this same error while doing our new image of 10.10.3 for next year. Tried with and without a config profile and still get the error. No 802.1x auth just WPA2
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.