Exchange 2010 - Anyone using wildcard certificates with Exchange 2010? I need some feedback
Hi,
We would like to use wildcard certificates with Exchange 2010. I was wondering if someone is currently running Exchange 2010 with them.
So far I have seen that when you place the CSR request you just specify *.domain.com once you get the CSR and you get the wildcard cert you have to complete the request on the server side.
I assume you will export the certificate on each of the servers. In my case I have 4 servers. 2 servers with combined roles CASHT and 2 MBX servers. I will import the certificate in the CASHT servers.
If you go with SAN certificate the Wizard let's you specify the names that you want to use. I would like to configure the following names.
OWA -> webmail.domain.com
Exchange Active Sync -> sync.domain.com
Outlook Anywhere - > mail.domain.com
Autodiscover -> Autodiscover.domain.com
HUB Transport -> mail.domain.com
Legacy - > legacy.domain.com
However with wildcard you only use *.domain.com. How do you manage the names that you want to assign?
Thank you!
We would like to use wildcard certificates with Exchange 2010. I was wondering if someone is currently running Exchange 2010 with them.
So far I have seen that when you place the CSR request you just specify *.domain.com once you get the CSR and you get the wildcard cert you have to complete the request on the server side.
I assume you will export the certificate on each of the servers. In my case I have 4 servers. 2 servers with combined roles CASHT and 2 MBX servers. I will import the certificate in the CASHT servers.
If you go with SAN certificate the Wizard let's you specify the names that you want to use. I would like to configure the following names.
OWA -> webmail.domain.com
Exchange Active Sync -> sync.domain.com
Outlook Anywhere - > mail.domain.com
Autodiscover -> Autodiscover.domain.com
HUB Transport -> mail.domain.com
Legacy - > legacy.domain.com
However with wildcard you only use *.domain.com. How do you manage the names that you want to assign?
Thank you!
a wildcard certificate has certain limitation, but by all mean, it will be work fine:)
http://technet.microsoft.com/en-us/library/dd351044.aspx
http://technet.microsoft.com/en-us/library/dd351044.aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Some older devices don't work with wildcard certificates. I know that we had that problem with Windows Mobile 5, so we had to go with a SAN certificate. I don't know if a wildcard certificate would cause problems with modern systems.