hey guys,
Has anyone noticed any issues with marshmallow/windows 10 devices having issues connecting with PEAP/MSCHAPv2. We have a bunch of newer devices coming in and are unable to auth. Just curious if any of you gentleman have run into this issue yourselves?
Yes. We tell them to turn that crap off and use EAP-TLS, like a manly he-man mountain trooper should.
Then HR comes by and tells us that we had some complaints about that last bit... but we still make them go with EAP-TLS if they want to get a ride on our wireless.
smackdown!
I've definitely got PEAP/MSCHAPv2 working with the stock Win10 supplicant going to MS server 2012 NPS as RADIUS,
BUT interestingly, for EAP-TLS, I only managed to get machine certs working. Doing user certs kept breaking. I have no idea why, and never bothered debugging it further - our resident wireless gurus just flat out said you're dicing with death with stock windows supplicant. Esp in Win10 stock where you can't even LOOK at the settings except via powershell/group policy, they removed the friggin dialog box!!!