Download the KSP installation file and then select and run it.

Run the XorbleKSP4KV.msi installer and wait for the installation to complete (this should only take a few seconds)

Installing the Xorble KSP with Dependencies

As well as the MSI, a setup.exe file is also provided together with run times for Visual C++ 14 and .NET Framework 4.7.2, which are dependencies of the KSP.

Checking the Installation

KSP Installed Files

The installation should copy the installation files to the following

Copies the following files to c:\windows\system32 (%SystemRoot%\System32)

  • XorbleKSP4KV.dll

Copies the following file to C:\Program Files\Xorble\XorbleKSP4KVSetup\

  • XorbleKSP4KVUserConfig.exe
  • XorbleKSP4KVSyncSvc.exe
  • XorbleKSPRegisterProvider.exe

Registry keys

The installation will create a new registry key at the following location:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Xorble\XorbleKSP4KV

KSP Registration

Registration of the Cryptographic Provider in the registry. The provider registration can be seen at the following registry path:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Cryptography\Providers\Xorble Key Storage Provider for Key Vault\UM

New Event Provider

The installer also registers a new event source which can be shown in the event viewer as shown below:

Azure Endpoints Accessed by the KSP

The KSP needs to be able to access various endpoints within Azure. Specifically, the KSP needs to be able to communicate with Azure Key Vault, Entra and the licensing endpoint. The URLs that it needs to communicate with are as follows:

Installing the KSP using a PowerShell RunBook

The PowerShell script “InstallXorbleKSP4KV.PS1” within the ZIP download automates the installation including installing the pre-requistites and then the KSP.

This script can be run manually or can be automated across multiple machines using a RunBook.

Create a new automation account (called something like XorbleKVKSPInstall) and within this create a new Runbook (called something like XorbleKVKSPInstallPS5_1). The Runbook will need to be created to use PowerShell 5.1 by default. Paste the following PowerShell code into the RunBook.

From the automation account create Hybrid Worker Groups for each of your groups of machines that need to have the KSP installed.

Once when this is setup, start the runbook, select Hybrid Worker and the group of machines to target and the hit Start.