I saw an issue like this around the time of Dev Preview 2 or 3 when we were still on JSS v9.32; the profile would deploy but the OS just would not recognize it in the 802.1x profile settings and wifi would never connect. Once we upgraded to JSS v9.4 the issue was resolved. We're still planning our upgrade to 9.6, and I imagine that's fine too since that's the only version of the JSS that officially supports Yosemite. What JSS version are you running?

We're running JSS 9.6

In https://support.apple.com/kb/HT6535 it states:

Description: An attacker could have impersonated a WiFi access point, offered to authenticate with LEAP, broken the MS-CHAPv1 hash, and used the derived credentials to authenticate to the intended access point even if that access point supported stronger authentication methods. This issue was addressed by disabling LEAP by default

Are you requiring LEAP which is now disabled?

- Justin

No LEAP here. We use PEAP to authenticate.

We use 802.1x certs and both of my Yosemite test units and they authenticate properly as does the iMac my office. We haven't pushed out 10.10 out in any thing like large scale but I haven't noticed anything wrong.

Well it looks as if the JSS is writing "bad" config files, as I spun up a Yosemite server and profile manager. I created an identical configuration profile, installed on my Yosemite test box and it works.

Opening a ticket with Jamf.

@ooshnoo - I'm seeing the same thing. My 802.1x PEAP Wi-Fi profile that's been working great on 10.7 thru 10.9 no longer works correctly with 10.10. I recreated the profile with Profile Manager and it's working fine. The only difference is that the JSS only lets me choose WPA/WPA2 for authentication type. Profile Manager lets you choose just WPA2 which is what I used.

We did notice in general that after some people "upgraded" to Yosemite, they had wireless connectivity issues, but I'm not sure about to what extent if it was 802.1x related or something else.

I doubt this helps as I still don't have any solid recommendations. However, I'm seeing stuff all over the interwebs regarding complaints about wifi issues in general after the upgrade (10.9 to 10.10). It looks like the general comments are pointing to corrupted network preference files. Again, I won't bother being specific as I can't test any of this until we start having replicable issues over our way.

I got confirmation from jamf on Friday that indeed the JSS is not writing correct code for the 802.1x profile and a defect has been filed to the dev team

Thank you for the update. We are seeing the same in our environment. Eager to see this fixed!

Also, be aware Apple just released this kbase article: http://support.apple.com/en-us/TS5258