Windows Certificate Section

This part has less experience, so write a separate article for record. In fact, it basically refers to the operation flow of qyt.

Enable role. Remember to select certificate authority web enrollment. IIS will be installed automatically and restart is required.

Configure Certificate Services

Configure Certificate Services template

Configure IIS

So you can apply for a certificate. Remember to add certsrv after URL

I first enter a domain PC to apply for a certificate. Open the console through mmc. Remember, some labs require us to apply for certificates for both users (user account) and computers (computer certificate).

Here's a note. It's best to use console to apply instead of remote desktop. I wasted the whole night. This is caused by some permission problems in windows.

Apply for a certificate for ISE. It's easier than I thought.

You need to import the root certificate before importing the requested certificate, otherwise there will be problems with the validation.

Import a previously requested certificate

Remember to use the domain name to log in!

Otherwise, the certificate keeps reporting errors. The egg hurts

In addition, I use this Windows CA to issue certificates to my SSL, there is no certificate to report an error! So even if I don't have the physical environment to test 802.1x, I don't think there will be too much problem at the certificate level. The most obvious example is that I use RDP to log in to the remote desktop, there is no certificate to report an error. This proves that there is no problem with PC's certificate.

FMC applies for a certificate when the blog is written specifically for firepower in the future.