Exchange Server 2007: Problem with Proxy Server's Security Certificate


From Exchange 2007, so it populates to all Outlook clients, how can I change the "Use this URL to connect to my proxy server for Exchange"?  This is found under the Account Settings in Outlook, Connection, Exchange Proxy Setttings...

We were using our webmail certificate and I am not sure how this changed back to the local machine certificate.  Get-ExchangeCertificate shows that the webmail certificate is enabled for SMTP.

I also issued the following which I thought changed it:

Set-ClientAccessServer -Identity MachineName -AutodiscoverServiceInternalUri 

Right now, a lot of the clients are receiving: There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site (MACHINENAME).  Outlook is unable to connect to the proxy server. (Error Code 10)
Who is Participating?
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.

Glen KnightCommented:
Do you have all the correct names in your certificate?
With Exchange 2007 you should have at least the following: (where is the part after the @ in your e-mail address) (the URL your users use to connect to Outlook Web Access)
servername.domainname.local (the internal Fully Qualified Domain Name of your CAS server)
SERVERNAME (the NETBIOS name of your server)

gtiiteeAuthor Commented:
This all happened after applying patches to my Hub Transport server and then rebooting.  I can't say for sure what the actual cause was because so many steps were taken and it seems to have been a timing with the clients connecting back to Exchange - I did re-apply the Set-ClientAccessServer -Identity MachineName -AutodiscoverServiceInternalUri  command which I think may have done it - I cant imagine why it would have been broken after reboot but I've seen stranger things.

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
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

From novice to tech pro — start learning today.