@Jamin79 What kind of equipment are you using for your Wi-Fi infrastructure? I've seen an issue with Cisco 802.1x auth where the Cisco controller will decide that a Mac has used an invalid authentication type even when there has been no change to a previously working Wi-Fi Configuration Profile. When that happens either the Mac has to be offline (shutdown, not just asleep) long enough for the Cisco controller to "forget" about it, or the device record showing the invalid auth request needs to be deleted from the Cisco console to force a re-evaluation.

We're using Meraki APs with everything managed by their cloud controller. Authentication is done via a Windows RADIUS server.

If you have access to the Meraki controller try looking up the Mac not getting connectivity and seeing what what the controller thinks the problem is.

It's not even getting as far as the controller. The computer is not showing the network as available in the wi-fi list, even though all the configuration is present.

And the SSID is still showing in the list of Known/Other Networks?

As an aside, hiding a SSID is not considered best practice these days (as in it offers no real security, and can introduce lag in connections), so if you've got any pull with the people managing your Wi-Fi infrastructure you might ask they stop hiding it.

Yeah, the SSID is still visible in known/other networks. Just not anywhere that you can select it, and click connect, and it doesn't connect automatically as it is configured to.

We're also having this exact issue. Hidden SSID, WPA2 Enterprise, RADIUS, Meraki.

Have you been able to resolve it?

Hi,

It's hard to say. It's a very intermittent issue, and we have so few Macs in the business that it might be weeks or months before someone experiences it.

Based on the response above, and having done some additional reading around how hidden SSIDs work, I have now unhidden our SSID, and I'm now waiting to see if the issue goes away.

My thinking is that something is malfunctioning with the beaconing process that is used to locate the hidden SSID; and, as it seems that having the SSID hidden arguably reduces, rather than improves, network security; I figure unhiding the SSID wouldn't hurt.

We are seeing the same issue with our hidden network.  We went through steps of setting up fresh configs over the summer - and now suddenly we are seeing this issue again.  We think it is somehow corresponding to  lease expiration.  In the past I was able to exclude and redeploy the profile.  However I tried that with a laptop last week and this morning they could not see the network to join again.  It no longer appears in the Menu bar as a known network but does still show in System Settings as a known network.

Having the same issue with Meraki, Jamf wifi profile, and WPA2 Enterprise w/ RADIUS through SecureW2 (who recommend the SSID be hidden in their configuration documentation for some reason).
Did you all come to any more conclusions?

We are experiencing this issue as well. Meraki AP's.

Wi-Fi Payload Settings:

- Hidden Network

- Auto Join

- WPA / WPA 2 Personal

Wi-Fi works fine for a while. Randomly, a laptop will drop the network (remains in known networks.) However, the network is not visible as an option to connect to when in range and the network is known.

I can confirm that excluding the device from the scope of the configuration profile and re-adding the device to the scope solves it but who knows for how long.

Has anyone been able to resolve this as we're experiencing this quite often with some of our users? 

I was going to try and log it with Apple support but we don't have the correct level of cover to raise it. 

Appreciate any advice. 

TIA. 

The only resolution we had was to make the SSID no longer hidden. SecureW2 verified to us that their only reason to recommend the network be hidden was to reduce user confusion with multiple SSIDs. We decided we were ok with not having it hidden in the end and no problems since.