When Outlook uses anywhere, the system prompts that the name on the security certificate is invalid or does not match the name of the website.
When outlook 2013 is configured using anywhere, the system prompts that the name on the security certificate is invalid or does not match the name of the website.
650) this. width = 650; "style =" float: none "title =" 1.jpg" src = "http://www.bkjia.com/uploads/allimg/131227/164F56432-0.jpg" width = "683" height = "387"/>
First, click the lower-right corner of the Security Warning prompt to view the certificate. For example, the prompt is that the certificate is issued to the AD computer,
650) this. width = 650; "style =" float: none "title =" 2.jpg" src = "http://www.bkjia.com/uploads/allimg/131227/164F54342-1.jpg"/>
Next, open Exchange server 2013 EAC and check the server certificate. mail.xxx.com is displayed. Open the Exchange management shell and enter the command get-exchangecertifacate. The Certificate Name Is mail.xxx.com. No exception occurs.
650) this. width = 650; "title =" 1.jpg" src = "http://www.bkjia.com/uploads/allimg/131227/164F5O54-2.jpg" width = "663" height = "327"/>
After the above steps check that the exchange certificate is correct, we connect to the AD server, open IIS, and click bind.
650) this. width = 650; "style =" float: none "title =" 4.jpg" src = "http://www.bkjia.com/uploads/allimg/131227/164F56041-3.jpg" width = "671" height = "353"/>
I found that a dc001.polymathmr.com certificate has been bound. AD is set to not use 443. How can this problem be solved?
After adding a certificate, create a snapshot and delete 443. Restart IIS.
650) this. width = 650; "style =" width: 673px; float: none; height: 444px "title =" 3.jpg" src = "http://www.bkjia.com/uploads/allimg/131227/164F5N40-4.jpg" width = "666" height = "431"/>
At last, we opened outlook and found that the previous certificate alarm has been cleared. The problem is solved.
650) this. width = 650; "style =" float: none "title =" 5.jpg" src = "http://www.bkjia.com/uploads/allimg/131227/164F53519-5.jpg" width = "677" height = "391"/>
Conclusion: When I first started troubleshooting, I found that the exchange certificate alarm was repeated on the exchange Server to find the cause.
The same alarm is reported again. The final problem is found out in the Active Directory, and the problem is resolved immediately. This also gives us a solution.
In case of problems, do not rush to start. First, analyze the possible causes of the failure, or the failure is not on the server itself, but on other servers and other links. This will help us solve problems more efficiently.
This article from the "Zhou Ping's Microsoft Unified Communication" blog, please be sure to keep this source http://1183839.blog.51cto.com/1173839/1286646