By Manny Fernandez

January 10, 2020

Configuring Microsoft CA Services

Microsoft includes a Certificate Authority Server or CA server at no cost to you (you will need a server license of course).  There are zero cost solutions out there like openssl however they lack the Microsoft Active Directory integration.  When you have FortiAuthenticator, it CAN act as a CA server and it does a fantastic job, however once again, the AD integrated CA is more appealing since it has deployment capabilities out of the box where the FAC COULD be a bit more cumbersome for novice AD sysadmins.  In this article, I am going to cover how to deploy Microsoft CA Services.  This is a prequel (although I wrote it almost a year ago) to my CA for SSL Decryption post.  Let’s get started.

Adding a Role

Windows Servers has a Server Manager utility that makes it easy to add services to your server installation. For instance you can add a DHCP Server role or in our case, the CA Server role.  By choosing the Server Manager utility (normally pinned to the task bar), you will be presented the following.  Choose Add roles and features

2020-01-10_10-28-42.png

Normally, you will see this page although you can opt to Skip this page by default

2020-01-10_10-28-57.png

Next we will choose Role-based or feature-based installation

2020-01-10_10-29-11.png

You will then need to select your server and hit Next

2020-01-10_10-29-27.png

Now choose Active Directory Certificate Services and hit Next

2020-01-10_10-29-53.png

You will now need to click Add Feature at this point.  This is informational and should be very simple.

2020-01-10_10-30-10.png

Nothing major below except for the Active Directory Certificate Services being selected.  Now hit Next.

2020-01-10_10-30-29.png

In the next screen, just click Next

2020-01-10_10-31-07.png

More informational reading.  The important thing here is that you cannot change the name of the server once it becomes a CA Server.

2020-01-10_10-31-20.png

You can now choose what additional services you want to enable.  For our purposes, we only require Certificate Authority and Certificate Enrollment Web Service

2020-01-10_10-32-46.png

Choose Next

2020-01-10_10-33-11.png

You can choose to Restart the destination server... I always do since my CA is usually not part of the authentication piece of AD (not a DC).

2020-01-10_10-33-30.png

Plenty of validation for this option.  You will need to hit Yes

2020-01-10_10-33-41.png

Finally, you can hit install.

2020-01-10_10-34-18.png

But Wait2.png

2020-01-10_12-03-56.png

Once you finish the installation, there will be an yellow exclamation on the Server Manager, click it to finish configuring it.

2020-01-10_12-06-55.png

Choose the CA and CA Web Enrollment options and hit Next

2020-01-10_12-07-22.png

You can choose either Enterprise CA or Standalone CA (I recommend the Enterprise CA) unless you need to.  If you need a non-integrated CA, just use FAC or OpenSSL.

2020-01-10_12-07-49.png

Next you will decide if this will be a Root CA or a Subordinate CA server.  Subordinates can sign certificates as long as the Root is trusted.  I almost always install a Root CA although there is use cases to do Subordinates, most common is having the Root offsite somewhere and have the sub do all the heavy lifting.

2020-01-10_12-08-05.png

You want to create a new Key Pair and hit next.

2020-01-10_12-08-33.png

You will want to choose the Key Length and the algorithm to use.  Your mileage may vary.

2020-01-10_12-08-48.png

Now you will need to verify some liberties the install took for you.  If you are good, hit Next.

2020-01-10_12-09-05.png

Specify the time before the Root certificate is good for.

2020-01-10_12-09-15.png

Informational pop up to give you the path of where it is going to store logs.

2020-01-10_12-09-33.png

Again, verify.  (Measure twice, cut once).

2020-01-10_12-09-53.png

Again, more information telling you the changes have been made.

 

 

 

Recent posts