Windows 7 clients are getting the below popup while connecting to the Wifi network. On the event viewer, I have two events related with this warning. Event ID 36881 The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate. Event ID 36888 Schannel - "The following fatal alert was generated: 48. The internal error state is 552." What should be the best way to fix this? Thanks in advance ! Shaba

you need to install the certificate to the trusted root certificate folder. I assume you have a certificate to validate the people connecting to wifi?

you need to install the certificate to the trusted root certificate folder. I assume you have a certificate to validate the people connecting to wifi?

Please find the screen shot of the Certificate MMC My assumption is that DigiCert High Assurance EV Root CA is in the Trusted Root Certification Authorities as expected. The workaround I got is to to tewak the WIFI profile on the client. Any help appreciated.Shaba

Please find the screen shot of the Certificate MMC My assumption is that DigiCert High Assurance EV Root CA is in the Trusted Root Certification Authorities as expected. The workaround I got is to to tewak the WIFI profile on the client. Any help appreciated.Shaba

If you got the workaround working what would you like to do now? Make it so this popup doesnt come up at all without the work a round?

How should we get this configured on 1000+ laptops? Is it something which we need to configure through group policy?Shaba

If you got the workaround working what would you like to do now? Make it so this popup doesnt come up at all without the work a round?

How should we get this configured on 1000+ laptops? Is it something which we need to configure through group policy?Shaba

One more question is that publishing the Wifi profiles through Group policy is the only recommended way to get this fixed? Shaba

One more question is that publishing the Wifi profiles through Group policy is the only recommended way to get this fixed? Shaba

you can use this command netsh wlan export profile name="profile name here of wireless" folder="D:\" and then netsh wlan add profile filename="wireless name.xml" user= all I'm not sure how it works with certificates but I'm pretty sure this will work for you. This way you can store the profile in a network location and use a script on all 1000 pc's to import it in. You can use group policy

you can use this command netsh wlan export profile name="profile name here of wireless" folder="D:\" and then netsh wlan add profile filename="wireless name.xml" user= all I'm not sure how it works with certificates but I'm pretty sure this will work for you. This way you can store the profile in a network location and use a script on all 1000 pc's to import it in. You can use group policy

Hi, Please refer to the suggestion by Ang101. If you have further question, please let us know. Juke Chou TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Juke Chou TechNet Community Support

Hi, Please refer to the suggestion by Ang101. If you have further question, please let us know. Juke Chou TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Juke Chou TechNet Community Support

Juke, My questions are not answered. I know that workarounds are there, but need to know if that the recommended way in an enterprise. Tested the same on Windows 8 - same issue. And the suggestion which I got from the Network consultant is to publish this Wifi SSID through group policy with "DO NOT ASK USER TO AUTHORIZE NEW SERVERS OR TRUSTED AUTHORITIES" ticked. Is that the recommended configuration to fix this issue? Shaba

Juke, My questions are not answered. I know that workarounds are there, but need to know if that the recommended way in an enterprise. Tested the same on Windows 8 - same issue. And the suggestion which I got from the Network consultant is to publish this Wifi SSID through group policy with "DO NOT ASK USER TO AUTHORIZE NEW SERVERS OR TRUSTED AUTHORITIES" ticked. Is that the recommended configuration to fix this issue? Shaba

Hi, I think it is a good way to work around the issue. Juke Chou TechNet Community Support

Hi, I think it is a good way to work around the issue. Juke Chou TechNet Community Support

Is that the recommended way ? In one side, we are adding some security settings and then later, on the client we configure the system not to prompt in case of any issue.Shaba

Is that the recommended way ? In one side, we are adding some security settings and then later, on the client we configure the system not to prompt in case of any issue.Shaba

Hi, No recommended way. Anyway, if it does work, it is a way we could try. Juke Chou TechNet Community Support

Hi, No recommended way. Anyway, if it does work, it is a way we could try. Juke Chou TechNet Community Support

Hi, Is there anyelse I can help with?Juke Chou TechNet Community Support

Hi, Is there anyelse I can help with?Juke Chou TechNet Community Support

This workaround is something I am aware. How ever, couldn't find a permanent fix. Shaba

This workaround is something I am aware. How ever, couldn't find a permanent fix. Shaba