can Public SAN certificate work without Exchange 2007 Hostname

We are going to register SAN certificate with Entrust which we will issue to our Exchange 2007 CAS Server. we have registered a domain e.g. domain.com on internet. But internally we use a different domain for AD and Exchange e.g. xyz.com. we have generated the SAN request and sent to Entrust, they are saying that you can't put xyz.com on the SAN certificate becuase it's not registered on your name. I have added all domain names during certificate file generation :

new-exchangecertificate -generaterequest -subjectname "c=india,o=ABC Corp,CN=webmail.domain.com" -domainname webmail.domain.com,autodiscover.domain.com,cas01.xyz.com,cas01 -Friendlyname "ABC Mail Certificate" -path c:\certreq.txt -privatekeyexportable:$true

now the request file has xyz.com entry (internal domain name used in AD). so my question is if i remove xyz.com entries then will my certificate have any problems (internal network or external network) while working on mails e.g. RPC, OWA or Outlook within LAN.

Please suggest.
fextechAsked:
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.

futurefilesCommented:
It can but i think you will get a warning on the outlook clients if the hostname is not in the SAN. Warning would be displayed every time you open outlook, if i remember correctly
0
futurefilesCommented:
Whatever server has the hub / cas role installed needs to be on the san as a hostname i.e DNS Name=exchange.abc.local
0
fextechAuthor Commented:
in my case we are not using .local but its .com e.g. xyz.com and it's registered by somebody else.
Are you using Public Certificate for do you have issued through internal CA (Microsoft)?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

futurefilesCommented:
Public from Entrust
why are you using someon elses domain name? your gonna be stuck i think
0
ParanormasticCryptographic EngineerCommented:
I assume by Entrust you are speaking of their commercial CA service, not their in-house CA product for your own internal certs.

If your internal domain ends in .com and you do not own that .com address, especially if someone else does, then it would not pass their vetting process and they must deny the request in order to maintain their integrity.  Otherwise they are certifying that you have rights to that .com, which you do not.

If it was a .local or a secondary .com that you could prove ownership of, then they would not likely have an issue with it.  This is one of those cases where technically it is possible, but it would probably not be legal for them to do so.
0
fextechAuthor Commented:
That's correct. Legally it is not correct to put some other domain in your own domain. But i don't know what's going to happen when users will be accessign mails internally, if I don't put my internal domain name in the certificate.

I also have doubt that certificate message will keep on prompting to users when they will be working on Outlook internally. Have you ever encountered such situation?
0
ParanormasticCryptographic EngineerCommented:
If they try accessing it securely and the name is not there, it will always generate a warning.  If they accept it then it willbe secured, but they will get prompted each time they log in to check their mail.

Depending on your security requirements, you might be able to get away with having unsecured connections across the LAN.  This is all up to your corporate security policy.  

If you cannot do this, then I would recommend looking into getting your improperly setup internal domain name migrated to a proper .local domain.  Here are a few links in this area - be aware of whatever apps you are running and how migration might affect them:

Windows Server 2003 Active Directory Domain Rename Tools
http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

Microsoft Exchange Server Domain Rename Fixup (XDR-Fixup)
http://www.microsoft.com/downloads/details.aspx?familyid=24b47d4a-c4b9-4031-b491-29839148a28c&displaylang=en

Rename a Windows 2003 Forest with Exchange 2003 installed
http://www.msexchange.org/tutorials/Domain-Rename.html
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
ParanormasticCryptographic EngineerCommented:
I'm just checking in on old posts today... Are you still having this issue?  If so, please let me know so I can help some more, if not, please close accordingly..
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.