I talked previously here about Certificate Enrollment Web Service CES and Certificate Enrollment Policy Web Service CEP , and in this blog post, I want to share my experience in deploying these services on Windows 2012 R2, using Kerberos Windows Integration as the authentication method.
You can refer to the below Microsoft TechNet pages for step by step details and information:
- Certificate Enrollment Web Service Guidance
- Certificate Enrollment Policy Web Service Guidance
- Certificate Enrollment Web Services in Active Directory Certificate Services
I guess my previous blog post and these TechNet articles will give you all the information you need to know how to deploy CES and CEP. What is missing is sense of experience and couple of screen shots.
Assumption, you have Microsoft Enterprise CA on your network called CA-1, and it has a common name (Corporate Contoso Issuing CA). You have two Windows 2012 R2 Servers that will be used to install CES and CEP. One is called CES-1 and the other is CEP-1.
We want internal domain joined computers to enroll for certificates using Windows Integration.
First of all, check the installation requirement here, then log on to a new Windows 2012 R2 server using a powerful account
- Enterprise Admins group.
- Must have Request Certificates permissions on the target certification authority (CA).
Before you start to install the CES role on CES-1 server, create an SSL certificate with Server Authentication purpose, and put it in the personal computer store on the CES-1 computer.
Now, from Server Manager, follow the below steps to install the CES role:
- After you finish installing the role using Server Manager, you need to do the Post-deployment Configuration.
- You have to write down your internal enterprise CA server name. Do not check the (Configure the Certificate Enrollment Web Service for renewal-only mode).
- Select Windows Integrated Authentication
- On the Service Account page, it is recommended to use custom account and not leave the default. This account is simply the account that will run the application pool.
- The account should be:
- Member of the local IIS_IUSERS group.
- Has Request Certificate permission on the CA server.
- Has delegation to do stuff in the CA.
- Has SPN for HTTP for the URL CES-1.contoso.com.
To do this, go to AD, and create an account called Svc_CES for example, add do the following:
- Add it to the local IIS_IUSERS local group on CES-1 server.
- Go to the CA server, open the Certification Authority console, check the properties of the CA, and on the Security tab, make sure the account has Request Certificate right.
- Open the Account property in AD, go to the delegation tab, use (Trust this user for delegation to specified services only/Kerberos Only), and choose (HOST and rpcss) when targeting the CA-1 server
Finally register the SPN. Open CMD with domain administration right and register an SPN as per the following:
setspn -s http/CES-1.contoso.com contoso\svc_CES
- Now select the SSL certificate with subject name CES-1.contoso.com that will be assigned by the installation wizard to IIS web site.
Once the installation is done, go to IIS, and check to see that there is a web site created for CES, and the svc_CES is running the application pool for it.
My CA common name is (CorporateIssuing CA IV), and it contains spaces. Sometimes, you may need couple of tweaks to make sure the URL format in the IIS is good. Fixes are mentioned here. In my case, although my CA common name contains spaces, I found that everything is working fine and I do not to do any of the mentioned fixes. May be it is because I am running Windows 2012 R2 🙂
Before you start installing CEP on a different domain joined Windows 2012 R2 server called CEP-1, make sure to request and install an SSL certificate in the computer personal store of this computer.
Now, go to CEP-1 server that should be domain joined and Windows 2012 R2, open Server Manager and start the add roles wizard.
You will be asked to choose an Authentication method (We will use Integrated authentication) in this case.
You then will be asked to choose an SSL certificate, choose the one we installed on this server previously.
You have to do two things:
- Configure a friendly name for the Certificate Enrollment Policy Web Service
- Configure GPO to point targets to the new Policy Enrollment URL.
Details about how to do this can be found here.