Certificate Services with Enterprise Root and Subject Alternative Name for Web Servers

I am trying to get certificates with Subject Alternative Names going in my enterprise. I currently have an enterprise root CA running on Windows 2003 R2 Enterprise. The CA cert has been imported to all of my domain members via group policy years ago. That is working fine. I have a new Windows 2008 R2 Enterprise server which is a subordinate (enterprise?) CA. What I need to be able to do is issue Web Server and Computer certificates with Subject Alternative Names for some web servers and other servers related to Remote Desktop Gateway and Session Host servers.

The Technet Article "How to Request a Certificate With a Custom Subject Alternative " <http://technet.microsoft.com/en-us/library/ff625722(WS.10).aspx> says that I should not enable EDITF_ATTRIBUTESUBJECTALTNAME2 because it's a security problem for Enterprise CAs.

When following the instructions for Certificate Enrollment wizard with an enterprise CA, the Web Server Certificate is not available. Only the Computer template is available. It says that I don't have permissions to request the other certificate types.

When I have my new subordinate CA running, my plan is to power down my W2K3R2 root CA.
LVL 43
kevinhsiehAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Adam BrownConnect With a Mentor Sr Solutions ArchitectCommented:
You need to make sure you have permission to enroll web certificates on your CA. If you are a domain admin or enterprise admin, you should already have permission, but to check, run MMC on your CA and open the Certificate Templates snap-in. Find the Web Server certificate in the list, right click, select properties, then go to the security tab and make sure your account or a group you belong to has Enroll permission.
0
 
kevinhsiehAuthor Commented:
Well, you were close. As an Enterprise Admin, I had permissions to the template. I could enroll a a web server certificate from IIS, but not from the local certificate manager. It turns out that the MACHINE needed permissions to the template. I created a new group in AD, added the appropriate servers, and then gave that group permission to enroll the certificate. I was then able to do it successfully after rebooting the machines.
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.