PDA Cert - multiple Domains

Folks,

I think I had been down this road earlier - but now have a new twist.

We have our sister company that needs a certificate for its Exchange 2007 server -
It looks to be only running the exchange generated certificate.

These are the suggested names we are looking at.,

Not sure if I am close in the naming -

This is the new "existing"  server......without a 3rd party cert.

Pda.cccc.com
Vpn.cccc.com
Pda.cccc.com/owa
srvemail001.cccc.acme.com
srvemail001
srvemail001.cccc.acme.local
autodiscover.cccc.acme.com
autodiscover.acme.com <<<<<<<<?????


This is our existing server at Acme.com
rsrvemail001.acme.com
rvemail001
owa-us.acme.com
rvemail001.acme.local
autodiscover.acme.com


I also have a server in the EU -

vemail001.acme.com
vemail001
owa-eu.acme.com
vemail001.acme.local
autodiscover.acme.com

I thought  the existing 2007 box had a 3rd party cert - I was wrong and need to correct this.

Any suggestions.

Thanks.

-Johnny
SynarcAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MesthaConnect With a Mentor Commented:
Are you going to have users with email address of cccc.acme.com ? If not then you are simply wasting money. Most certificate providers charge more for the additional names, some on a per name basis, some in blocks of 5.
Personally I wouldn't bother with either pda or owa variants and just tell everyone to use mail.domain.com.

Simon.
0
 
MesthaCommented:
The only names the certificate needs is

mail.example.com (the preferred common name for OWA, ActiveSync etc)
autodiscover.example.com (where example.com is the domain in the user's email addresses)
server (the server's NETBIOS name).
server.example.local (the server's real INTERNAL FQDN)

If you are supported additional SMTP addresses then you need to have autodiscover.domain2.com in there as well.

You do not have to add in server.example.com unless that is what the server's FQDN is inside (ie because your WINDOWS domain is called example.com).

/ anything is not valid for an SSL certificate, so the line above with /owa isn't correct.

Simon.

0
 
SynarcAuthor Commented:
Mestha  -
 
Thanks for the info - if we want to make sure we are covered for all scenarios... it would be best to have the following sub-domains and names in th certificate - we are still building out some portions of the network and are not sure how or when things may change - we don't want to keep changing certs.
Any thoughts?
 
srvemail001.cccc.acme.com (FQDN)
srvemail001  (netbios)
Pda.cccc.com
owa .cccc.com
srvemail001.cccc.acme.local
mail.cccc.com
mail.cccc.acme.com
mail.acme.com
 
autodiscover.cccc.acme.com
autodiscover.acme.com  
Thanks.
 
-Johnny
0
 
SynarcAuthor Commented:
It looks like i forgot an autodiscover:
 

srvemail001.cccc.acme.com (FQDN)
srvemail001  (netbios)
Pda.cccc.com
owa .cccc.com
srvemail001.cccc.acme.local
mail.cccc.com
mail.cccc.acme.com
mail.acme.com

autodiscover.cccc.acme.com
autodiscover.acme.com
autodiscover.cccc.com
0
 
SynarcAuthor Commented:
Thanks Simon - it is a sister company  - and we are just trying to cover all the bases on it because we are unsure of what the final domain naming convention will be in the future.
 
-Johnny
0
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.

All Courses

From novice to tech pro — start learning today.