We help IT Professionals succeed at work.
Get Started
Exchange 2019. Outlook clients get warning about certificate
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.
Why Experts Exchange?
Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.
Jim Murphy
Programmer at Smart IT Solutions
When asked, what has been your best career decision?
Deciding to stick with EE.
Mohamed Asif
Technical Department Head
Being involved with EE helped me to grow personally and professionally.
Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question
Connect with Certified Experts to gain insight and support on specific technology challenges including:
- Troubleshooting
- Research
- Professional Opinions
Did You Know?
We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE