Exchange 2010 Certificates with non-split DNS

I have Exchange 2010 setup and running alongside our Exchange 2003 environment.  Our external domain name I will call exdomain.com and our internal domain indomain.com.

I have our public cert moved onto our Exchange 2010 server, mail.exdomain.com, and it works just fine.  Now Outlook complains that the cert doesn't match what it is looking for.  I understand this is because Outlook is looking for the NETBIOS name and the cert with the NETBIOS name that the install created.  From what I've read there are two ways around this.

1.  Add our NETBIOS name to our public cert
2.  Change the NETBIOS names for autodiscover, webservices and OAB via EMS to the full public name, mail.exdomain.com.

I guess either of these would work.  But I was wondering if I should do one vs the other.  We have a very basic setup with all roles on one server and no ISA server in the mix.
jpletcher1Asked:
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.

Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
You can mod the vdir to correct this....just follow this article.

http://www.shudnow.net/2007/08/10/outlook-2007-certificate-error/


0

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
jpletcher1Author Commented:
This was the article I actually had read before I posted this.  So I could follow this article or get the NETBIOS name on our cert and either should work.  Was just wondering if one way was better than the other or if either way limited us in any way.
0
jpletcher1Author Commented:
I just went ahead with the article instead of going with adding names to our current certificate since that was easier and we connect to OWA internally with the same name as we do externally.  I guess if I ever need to do it the other way I can always go back and change it.
0
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.