troubleshooting Question
Exchange 2019. Outlook clients get warning about certificate
Martin_Radbo
asked on
asked on
Complete new installation of servers and clients.
One single server with Windows Server 2019, containg AD and Exchange server 2019.
Clients are WIn 10 Pro, joined to domain, with Outlook 2019.
Internal domain name is stsgroup.local, to late we realized that a public domain name is best practice theese days. But now we have an internal one...
When Outlook clients are setup for the first time, the following message are shown:
![error.png]()
As you can see, they try to use the internal domain name and therefor the warning is issued.
The certificate is a SAN, with autodiscover.domain.com, webmail.domain.com and mail.domain.com. It is installed on the server.
I have changed all of the URL:s for the virtual dir. to https://webmail.domain.com/...
Split DNS are configured, so in the internal dns autodiscover.domain.com and webmail.domain.com are pointing to the internal ip of the Exchange server, i.e. 192.168.140.40
The external DNS are pointing to the public IP of the Exchange server.
I have read several posts about this, but it still fails.
Please help.
One single server with Windows Server 2019, containg AD and Exchange server 2019.
Clients are WIn 10 Pro, joined to domain, with Outlook 2019.
Internal domain name is stsgroup.local, to late we realized that a public domain name is best practice theese days. But now we have an internal one...
When Outlook clients are setup for the first time, the following message are shown:
As you can see, they try to use the internal domain name and therefor the warning is issued.
The certificate is a SAN, with autodiscover.domain.com, webmail.domain.com and mail.domain.com. It is installed on the server.
I have changed all of the URL:s for the virtual dir. to https://webmail.domain.com/...
Split DNS are configured, so in the internal dns autodiscover.domain.com and webmail.domain.com are pointing to the internal ip of the Exchange server, i.e. 192.168.140.40
The external DNS are pointing to the public IP of the Exchange server.
I have read several posts about this, but it still fails.
Please help.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 16 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.