• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 439
  • Last Modified:

Exchange 2010 - Anyone using wildcard certificates with Exchange 2010? I need some feedback


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!
1 Solution
You don't assign the names when using a wildcard certificate. Any name that resolves to the server using the wildcard certificate will work, as long as it matches the wild card.

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.
Jian An LimSolutions ArchitectCommented:
a wildcard certificate has certain limitation, but by all mean, it will be work fine:)

Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Well when you use a wildcard certificate, you just need to configure the URL's internally as usual. get the wildcard certificate and assign it to the services on exchange. and.. the problem you will have is with the outlook anywhere service. OA and wildcard certificates dont work "out of the box".. you need to change a parameter on the outlook provider. run on your exchange CAS:

Set-OutlookProvider EXPR -certprincipalname:*.domain.com

hope it helps
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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now