Microsoft PKI – Decommission CA Server

Abbreviated mostly  from:

Several notes:

These instructions assume that all issued certificates are expired.

If the issued certificates still exist and are active within the expire time or are revoked, you will need to go through a set of steps to revoke the remaining issued certificates and update/transfer the revocation list to the current PKI systems. Generally you can just remove the certificate templates from the old server and let the certificates expire or be re-issued by the newer issuing servers. It all depends on how quickly the old PKI server needs to be removed from inventory.

Steps are different on a single-tier PKI set up, so don't do this unless you are sure!

Get and pair the server name and CA name. This will show all info about all CA servers, so choose the server name wisely. From PowerShell or CMD terminal as admin:


Shutdown certificate services on the server being decommissioned:

certutil -shutdown

Delete CA private key using the name gathered from above (I have had issues with this step and probably is not important if you securely erase the drive immediately after server decommissioning):

certutil -delkey <"ca name">

Uninstall Certificate Services:

"Server Manager", "Manage", "Remove Roles and Features"
Click through wizard and de-select "Active Directory Certificate Services"

Restart the server.

ONLY do the following if issued objects like CRL and AIA no longer matter! DO NOT remove the Certificate Templates if you are replacing this PKI server!

Remove CA Objects from AD:

"Server Manager", "Tools", "Active Directory Sites and Services"

Select appropriate icon in left window pane, "View", "Show Services Node"

"Services", "Public Key Services"

Under the "AIA", "CDP", "Certification Authorities", and "Enrollment Services":

Delete the CA object
NOTE: should already be missing under "Enrollment Services" because it is removed during the removal of certificate services.

There are more advanced cleanup procedures in the link at the top if you feel that these deletion steps did not work properly.

There is also a method to recover the certificate templates if they are deleted.

Red Hat Registration and Subscriptions

I recently decided to spend some time refreshing my Red Hat knowledge because it has been a while since I have supported production Red Hat based servers. A lot has changed. You can signup for a developer license for free and get limited access to Red Hat products.

Registration, among other things, controls the repos that the server can use.  For instance, you cannot run ‘dnf update’ until the system is registered and attached to the available desired software repositories. The ‘subscription-manager’ command exists to handle various subscription configuration situations.

For a basic free developer subscription, the following will get things started from the command line.

Show the various commands available to the subscription manager command:


Subscribe and configure the available repos. This can apparently be used with kickstart as well:

subscription-manager register --username --password --auto-attach

Update the system:

dnf update

There is a lot more to subscription manager based on workflows, hosted repositories, configurations, etc. Because of different workflows, registration can also be performed via the GUI, web console, automation, etc.

2010 HD Dyna: Dealing with the Factory Alarm System

The 2010 Dyna models came with a factory alarm that flashed the signal lights if it was triggered. I paid the HD tax and added the siren unit since flashing turn signal lights by themselves doesn’t add much security.

The alarm system adds some challenges to performing battery maintenance, transportation, and overcoming dead/lost FOB issues (disabling the the alarm to ride).

Disable the Alarm when disconnecting the battery.

1) With the FOB near the bike, turn the ignition switch to on to disable the alarm system.
2) Remove the negative cable from the battery. 

It has also been suggested to remove the 40A main fuse before removing the negative lead from the battery. In fact, this is recommended when disconnecting power in a different section of the manual. I see no point in the additional labor for a simple battery removal. The above is straight from the owner’s manual.

Transport Mode.

This is described as disarming the motion detection but allowing the alarm to trigger if an attempt to is made to start the engine. It is safer and works better than tying the FOB to the motorcycle when transporting long distances.

1) With the FOB in range, turn the ignition switch to on.
2) Set the engine stop switch to off.
3) Turn the ignition switch to ACC.
Within 5 seconds, press both the left and right turn signals at the same time (turn signals flash once).
4) Turn ignition switch to off (turn signals flash 3 times).

To return to normal operation:

With FOB in range, turn switch to ignition and and set the engine stop switch to run.

Disabling the Alarm System to Ride

This method assumes that you are going to ride the motorcycle and the steps must be repeated after the ignition switch is turned off.

This requires that you know the security system PIN.

You must keep the FOB away from the motorcycle.

If you screw up entering the PIN, wait more than 2 minutes before attempting the next try.

1) Turn the ignition switch to ignition.
2) Within 2 seconds, hold both turn signal switched in until confirmation on the dashboard.
3) Enter the PIN by toggling the left turn signal switch to the proper number on the dash, and using the right turn signal switch to advance to the following digits.
4) After the 5th digit has been entered, press the right turn signal switch one more time. The key icon on the dash should stop blinking.

Again, once the ignition switch is turned off, the alarm system will turn back on.