As I mentioned above, I've found that any of the users who had Outlook 2016 setup for their e-mail accountĪfter the certificate was installed on the Exchange server, is not seeing the certificate error. Srv Record lookup for Failed (0x8004010F) Local autodiscover for Failed (0x8004010F) I can certainly see that they are all failing, but other computers in the office work fine and do not throw the certificate error, so now I am wondering it the problem is with this user's local auto discover file? I put spaces in between each domain name variation I had to type this all out because the Autodiscover tool does not let me copy and paste the output so please excuse any typos you might find. I had to find a good time to RDP into the client's computer and run the test.īelow are the test results with the real domain name altered. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams. If you have feedback for TechNet Subscriber Support, Click here to learn more. Please remember to mark the replies as answers if they helped. Get-ClientAccessServer | Select Name,AutoDiscoverServiceInternalUriĪlso, I notice that this issue remain exists on some special Outlook client, I recommend to configure same account on other working PC, then check the result. Get-WebServicesVirtualDirectory | Select Server,InternalURL,ExternalURL Get-OABVirtualDirectory | Select Server,InternalURL,ExternalURL Get-MAPIVirtualDirectory | Select Server,InternalURL,ExternalURL Get-OutlookAnywhere | Select Server,InternalHostName,ExternalHostName Integration with Exchange and Skype for Business.įor certificate warning, I recommend to run below command and check the host name of each Exchange service (ensure it's ): We need those self-signed certificates which are be created by Exchange installation, "Microsoft Exchange" will be used for TLS for communication between Exchange server, and "Microsoft Exchange Server Auth Certificate" is needed when deploy If anyone has any more insights they would be greatly appreciated. There seems to be no rhyme or reason as to why the inconsistency. Some Outlook 2016 users no longer get the certificate error, some do. I have gone into servers->virtual directories and changed all the internal URLs to the external URL of I did not get a message saying they would be replaced by the new certificate when it was imported.įrom what I've read on the forums there is no 100% certain answer as to whether these self-signed certs can be removed without creating problems for Exchange and there doesn't seem to be a simple way to just disable the SMTP services from the self-signed certs.ĭNS has been updated in the server with an A record for and pointing to the server's internal IP.ĭNS hosting has also been updated with autodiscover.ourdomainname and remote.ourdomainname pointing to the public IP of the server. The original self-signed certs named "Microsoft Exchange" and "Microsoft Exchange Server Auth Certificate" are also listed and they are Valid and ThisĬertificate is only needed for e-mail, they do not have a website running on this server. It has been assigned to the SMTP, IMAP, POP and IIS services. I have imported the SAN SSL certificate from GoDaddy and it shows as Valid if I go into EAC and click servers->certificates. The server the users are connecting to is running Exchange 2016. The message shows the internal mail server name and says "The name on the security certificate is invalid or does not matchĪ SAN SSL certificate was purchased from GoDaddy 3 weeks ago with the subject (example) names of: The Problem: Outlook 2016 users are getting the dreaded Security Alert certificate error message shortly after they launch Hi, over the past 3 weeks I have read the many dozens of articles about this issue as well as many others on other forums and resources but can't seem to fix this problem completely.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |