exchange certificate not working

hi, i have an exchange 2016 server running.

i installed a new certificate on this server. this works, when i use the web adress. owa and ecp, no problems. the certificate is working.

when opening outlook i still got errors:

the certificate is published... green and ok!
the date of the certificate... green and ok!
the name on the certificate.... red and nok!

i see also on top of this popup: exchange.domainname.local

i think this should be mail.domainname.be

our certificate is a wildcard *.domainname.be

any idea how to fix this?
LVL 1
Rik Van LierCEOAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Todd NelsonSystems EngineerCommented:
You will need change your autodiscover service connection point (SCP) on the new Exchange server to a name that exists in the certificate.  By default, when Exchange is installed the setup uses the server name and your internal domain name to set the value; and the value cannot be changed in the Exchange Admin Center.

From your Exchange 2016 server, run this command in the Exchange Management Shell...

Get-ExchangeServer | Get-ClientAccessServer | fl identity,*uri*

Open in new window


In all likelihood, the output will look something like this...

Identity:  "YourExchange2016ServerName"
AutoDiscoverServiceInternalUri:  https://exchange.domainname.local/autodiscover/autodiscover.xml

Open in new window


To fix the error, update the AutoDiscoverServiceInternalUri value through the Exchange Management Shell using the Set-ClientAccessServer command.  Similar to this...

Set-ClientAccessServer -Identity "YourExchange2016ServerName" -AutoDiscoverServiceInternalUri https://autodiscover.domainname.be/Autodiscover/Autodiscover.xml

Open in new window


Hope this helps.
MASEE Solution Guide - Technical Dept HeadCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rik Van LierCEOAuthor Commented:
@MAS, this is for exchange 2007 and 2010.

i am running 2016

same to do?
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

MASEE Solution Guide - Technical Dept HeadCommented:
You can use the same for Exchange2016.

MAS
Tej Pratap Shukla ~DexterServer AdministratorCommented:
Hi,
Go through below links to resolve Exchange Certificate issue.
http://www.exchangemvp.org/exchange-autodiscover-proxy-certificate-issue/

Hope, you will get the answer.
Mre MartinCommented:
have you assigned services to the public certificate ?
Rik Van LierCEOAuthor Commented:
The Solution of MAS solved the problem
Todd NelsonSystems EngineerCommented:
You should have enough information to resolve your question.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.