Solved

UC/SAN certificates in a multi-site environment

Posted on 2011-09-12
5
371 Views
Last Modified: 2012-05-12
Hello,

I administer an Exchange environment with 5 sites in different towns, connected via WAN links. The main office is our mail gateway (for incoming traffic, anyway) and there is a Hub/MBX/CAS server at each site in the same internal AD domain (domain.internal). While intra-office traffic is handled through the WAN/VPN, each office's server can send external mail directly and has its own OWA configuration, e.g. city1.pubdomain.com/OWA, etc. There are also multiple public domains, pubdomain.com, thisdomain.org, etc. I had previously installed wildcard certificates on each server, which worked fine in the Exchange 2003 days (all sites are 2007-2010 now), but I would like to unify/simplify this process.

Two questions:
1- exactly how many SAN names do I need to include? I understand that the internal FQDN is needed, but is each individual internal servername necessary? If I'm understanding that right, my list would look something like this:
server1, server2, ..... server5
server1.domain.internal, ... server5.domain.internal
mail.domain.internal
autodiscover.domain.internal
mail.pubdomain.com
mail.thisdomain.org
autodiscover.pubdomain.com
autodiscover.thisdomain.org
city1.pubdomain.com, ..., city5.pubdomain.com
city1.thisdomain.org, ..., city5.thisdomain.org

That's a lot of names! can this list reasonably be shortened?

2- Some SAN certificate vendors are now advertising certificates that can be installed on multiple servers. Would that be helpful/cost-effective in this situation, or is that more for multiple servers in the same site?

Thanks in advance for clearing this up.
0
Comment
Question by:ICCHOOPS
  • 2
  • 2
5 Comments
 
LVL 4

Accepted Solution

by:
ctc1900 earned 350 total points
Comment Utility
For a public facing CAS, I'd suggest you avoid using internal mail servers and stick to generic names that would be used for OWA/EWS/ActiveSync access.

mail.domain1.org
mail.domain2.org
autodiscover.domain1.org
autodiscover.domain2.org
legacy.domain1.org (for E2K3 co-existance)
legacy.domain2.org
...and any other domain you could think you could use in the future for OWA/EWS/ActiveSync access.


0
 
LVL 1

Author Comment

by:ICCHOOPS
Comment Utility
Hi, CTC,

That seems reasonable, as I already have internal DNS stub zones for the public domains. Should I be including city1.domain1.org, city2.domain2.org, city2.domain1.org, etc. along with them?

Also, any insight on part 2 of my question?

Thanks a lot!
0
 
LVL 4

Assisted Solution

by:ctc1900
ctc1900 earned 350 total points
Comment Utility
Yup, adding the city*.domain*.org makes sense.

Regarding question 2. Yes, you could add the same certificate to multiple Exchange CAS servers regardless of site, the key thing is for the SAN certificate to have the needed subject names.  In the past, I've installed the certificate in one Exchange CAS server, export it from within Exchange and import it to the other ones.
0
 
LVL 23

Assisted Solution

by:Malli Boppe
Malli Boppe earned 150 total points
Comment Utility
How many internet facing CAs server do you have.
If more then one add all of them
Your primary domain webmail and autodiscover.
Thats all

Also for your 2nd email domain you need to make the below IIS changes
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html
0
 
LVL 1

Author Comment

by:ICCHOOPS
Comment Utility
Thanks for sharing
0

Featured Post

Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
To show how to generate a certificate request 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 Servers >> Certificates…
This video discusses moving either the default database or any database to a new volume.

771 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

12 Experts available now in Live!

Get 1:1 Help Now