How to solve the problem that a server in Exchange 2016 environment does not allow users to access it?

Today, I will talk to you about how to solve a server in Exchange 2016 environment that does not allow users to access it. Many people may not know much about it. In order to let everyone know more, Xiaobian summarizes the following contents for everyone. I hope everyone can gain something according to this article.

An Exchange 2016 server was recently added to the environment for testing, and users connect to it when they open Outlook, with a certificate error prompt because the certificate does not include the machine.

Solution:

Delete all related directories

Remove-MapiVirtualDirectoryRemove-EcpVirtualDirectoryRemove-AutodiscoverVirtualDirectoryRemove-WebServicesVirtualDirectoryRemove-OwaVirtualDirectoryRemove-OabVirtualDirectoryRemove-MapiVirtualDirectory "mapi (Default Web Site)"Remove-EcpVirtualDirectory -Identity "xxx\ecp (default Web site)"Remove-AutodiscoverVirtualDirectory -Identity "xxx\autodiscover (autodiscover.contoso.com)"Remove-WebServicesVirtualDirectory -Identity "xxx\EWS (Default Web Site)"Remove-OwaVirtualDirectory -Identity "xxx\owa (Default Web Site)"Remove-OabVirtualDirectory -Identity "OAB (Default Web Site)"After reading the above, do you have any further understanding of how to solve a problem in which a server in an Exchange 2016 environment is not accessible to users? If you still want to know more knowledge or related content, please pay attention to the industry information channel, thank you for your support.