Hi guys,
So this may be related to the issue at this post:
[https://www.jamf.com/jamf-nation/discussions/24129/sierra-10-12-5-upgrade-breaking-corp-wifi](link URL)
We just took delivery of 5 shiny new MacBook Pro 2017 models with two thunderbolt ports but no touchbar.
We currently have 35 older MacBooks running El Cap 10.11.6 that have config profiles deployed on them with a Network payload and a Certificate payload. These are bound to our Active Directory.
The setup we have working with these is a machine based authentication to the WiFi at the login window, and then the user logs in to authenticate both to the network and then to their AD account.
This has worked fine, but deploying this same config profile to these new MacBooks doesn't work.
The WiFi icon seems to flash solid briefly several times at the login window, but it isn't successfully authenticating to the network.
The network settings we have set are:
**Auto-Join (checked)
Security Type: WPA/WPA2 Enterprise
Use as login window configuration (checked)
Protocols:
PEAP
Use Directory authentication (checked)**
And in the trust tab, I have checked a series of certs that are the root and intermediate certs for our AD as well as the CA for our AD. I added these to the 'Certificate' payload.
I don't necessarily think the settings in my profile are incorrect, since it works on the older MacBooks running El Cap, but clearly something has changed in Sierra that has thrown everything out of whack.
One error I do see in the WiFi logs on the new MacBooks is something about an EAPOL frame being dropped and it not being a key frame.
Anyone see anything I'm missing?
Thanks for your help,
Rory.
