I was thinking about this too.. Incorrect certificate.not sure though if from NPS side or client.. please correct me if I am wrong.. -- the cert stays on the NPS side locally - and simply validates if the local machine has them About the local PC. - working fine when connects to corporate SSID [old NPS] - I deleted the existing cert.. and imported the new cert provided to me.. question: - do I need to delete the existing cert and manually import the new cert? in 2016 NPS I noticed the ff: In Secure Wireless Connections: constraints/authentication method/ Microsoft : PEAP BY default we have our corporate wlan cert in there.. it didn't work.. When selected, Windows machine does the ff: Connects to test SSID Windows will provide option to “Connect automatically” - this does not work and won’t connect Another option is to “Use my Windows account” – this also does not work and won’t connect Another option is to manually enter the username and password without the domain name. But still does not work. so I selected the Windows Azure CRP Certificate Generator certificate. background: we recently moved our machines to Azure.. When selected, Windows machine does the ff: Connects to test SSID Windows will provide option to “Connect automatically” - this does not work and won’t connect Another option is to “Use my Windows account” – this also does not work and won’t connect Another option is to manually enter the username and password without the domain name. This worked and showed an option to Show certificate details. I checked the certificate and clicked OK. I am able to connect to test SSID. though I am not sure if the thumbprint shown in the cert is the correct one.. questions: - do you guys think this is a cert issue? in my opinion, it could be.. so i will get back to our systems team and verify which one is the correct cert since one worked.. - why do I have to manually enter the username/password? -does anyone have a documentation for server 2016? many thanks! Dip
... View more
