Solved

Trouble with Exchange 2007 Autodiscover

Posted on 2014-10-05
4
86 Views
Last Modified: 2014-10-06
Our 3rd party spam filter is not working correctly due to an error with Autodiscover. It seems to be an issue with our certificate. We have a self signed certificate and I think it has all the correct local and remote domains names. Here is the error I get when running Test-OutlookWebServices:
1005       Error When accessing https://remote.mydomainame.com/autodiscover/autodis
                 cover.xml the error "RemoteCertificateNameMismatch:CN=remote.mydomainname.com, O=My Company Inc, DC=mycompany, DC=com" was report
                 ed.

Why is it giving me a name mismatch ?
0
Comment
Question by:WiddleAvi
  • 2
4 Comments
 
LVL 30

Accepted Solution

by:
Gareth Gudger earned 500 total points
Comment Utility
Have you seen this forum thread? Lots of great links on it too.
http://social.technet.microsoft.com/Forums/exchange/en-US/2404ddf4-ffd7-45ac-bf2c-a0d639ca17e5/how-do-i-change-the-autodiscover-address

I would always recommend going for the 3rd party certificate. It will save you a lot of trouble in the long run.
http://supertekboy.com/certificates-for-microsoft-exchange/
0
 

Author Comment

by:WiddleAvi
Comment Utility
I will try info in that link in the morning. Unfortunately the customer right now does not want to spend on a 3rd party certificate.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
Comment Utility
You can get a trusted SSL certificate for less than $80/year.
The self signed certificates are not supported for use with ActiveSync or Outlook Anywhere. If the customer has spent the money on Exchange server, CALs, Windows licences and hardware, not spending the money on an SSL certificate seems petty. I don't know how much your time is worth, but I tell my clients the maths is quite simple - every time you want to add a client, it will take 10-15 minutes to get it setup, plus the same again each time the self signed certificate is replaced. Or you can get a trusted certificate which is a lot less than one hour of my time and not have to worry about it.

Self-Signed certificates are simply not worth the hassle.

Simon.
0
 

Author Closing Comment

by:WiddleAvi
Comment Utility
Thanks for pointing me in the right direction. In the end the problem was I was using the remote.ourdomain.com in the CN but did not include it together with the list of alternate domain names. I created a new cert had remote.outdomain.com as the CN and again in the list of alternate domain names.
0

Featured Post

Free book by J.Peter Bruzzese, Microsoft MVP

Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now