In this post, I describe how to manually set a certificate to the status "Archived" in Microsoft Windows. Usually, when renewing certificates, old ones get archived automatically.  However, you may want to manually set a certificate to the Archived status e.g. for testing purposes. Resolution To manually set a certificate to Archived: 1. Open a command prompt as Administrator 2. Run  certutil -store my to view the certificates in the Personal (my) store: 3. Make a note of the Cert Hash(sha1)  of the certificate you want to archive 4. Create a new file called archive.inf and insert the following text: [Properties] 19 = Empty This file is used to archive the certificate. 5. Save archive.inf e.g. to c:\ 6. In the  command prompt , change directory to where you saved archive.inf e.g. cd c:\ 7. Run  certutil -repairstore my "9a0bf9cfc3c9573121fa38fea3360ba7572a78e5" Archive.inf  replacing  9a0bf9cfc3c9573121fa38fea3360ba7572a78e5  with the Cert Hash(sha1)  noted ear

In this post, I describe how to add Rack and Chassis information to a node in Failover Cluster Manager on Microsoft Windows Server. When you view nodes in Failover Cluster Manager, you will see that there is a Rack and Chassis column but no way to add this data in the user interface. Resolution Create Fault Domains in PowerShell to add Rack and Chassis information to a node: 1. Open PowerShell ISE as administrator 2. Check your existing fault domain hierarchy using  Get-ClusterFaultDomain 3. Create your desired hierarchy (Site > Rack > Chassis > Node):      # Define a site      New-ClusterFaultDomain -Name "Site-1" -Type Site      # Define a rack within the site      New-ClusterFaultDomain -Name "Rack-1" -Type Rack -Parent "Site-1"      # Define a chassis within the rack      New-ClusterFaultDomain -Name "Chassis-1" -Type Chassis -Parent "Rack-1"      # Assign the node "HYPERV-2K16-1" to "Chassi

In this post, I describe how I resolved the warning: "A driver cannot load on this device" This warning was raised by the Program Compatibility Assistant on Windows Server 2025 when I attempted to run the program Process Explorer. Cause This warning is caused by device protection in Windows Security which helps to prevent drivers from being used to run malware. Resolution Because this warning occurred on a virtual machine used only for testing, I was happy to resolve this issue by disabling the device protection security. To do this on Windows Server 2025: 1. Open Windows Security : 2. Go to Device Security : 3. Turn off Microsoft Vulnerable Driver Blocklist : 4. Restart the computer for the settings to take effect. I was then able to run Process Explorer without getting the warning.