See below for registering the Policy Agent from the Windows command line
Required information
Before registering the Policy Agent from the Windows command line, make sure you know:
The VM Encryption vault details. This is the vault you configured during the initial setup.
The IP addresses of the Cryptographic Security Platform Vault for VM Encryption node with which you want to register the Policy Agent.
- The login credentials for a Cryptographic Security Platform Vault for VM Encryption account with Cloud Admin privileges.
- The name of the Cryptographic Security Platform Vault for VM Encryption Cloud VM Set with which you want to associate the VM. You cannot encrypt the drive until it has been associated with a Cloud VM Set in Cryptographic Security Platform Vault for VM Encryption. For details, see the Administration Guide.
Creating the cloud VM set of certificates
When you register the VM, you can either specify the Cloud VM Set you want to use interactively during registration, or create a certificate for that Cloud VM Set in the Cryptographic Security Platform Vault for VM Encryption web GUI and use that certificate during registration.
To create the cloud VM set of certificates
- Log in to the Cryptographic Security Platform Vault for VM Encryption using an account with Cloud Admin privileges.
- In the top menu bar, click Workloads.
- On the VM Sets tab, select the Cloud VM Set with which you want to associate the VM.
- Click Actions > Create New Certificate.
- If desired, enter a passphrase for the certificate. If you enter a passphrase here, you will need to enter that passphrase when you use the certificate on the VM.
- Enter a date on which this certificate should expire.
Click Create. The Cryptographic Security Platform Vault for VM Encryption downloads a
.certfile to the default download location.Do not rename the downloaded certificate. The certificate name includes additional information, and a renamed certificate will fail.
- If necessary, copy the
.certfile to the Windows VM.
Running the registration command
Log into the VM using an account with administrator privileges, open a Windows command prompt run the following command.
hcl register [-a] [-h vm-name] [-d "vm-description"] [-p cert-passphrase] [-o one-time-passphrase] [-z cvm-set] [-v vault_id] [-n mapping-name] [-N] kc-hostname[:port],kc-hostname2[:port],... [cert-file.cert]Where:
-a— Indicates that you want to authenticate the VM through the command line or the script instead of through a certificate file. Use this option if you are using Simplified or Automated Authentication. If you created a certificate in Cryptographic Security Platform Vault, omit this option and specify the certificate name incert-file.cert.-h—The name of the VM that will be displayed in the Cryptographic Security Platform Vault for VM Encryption (Default: hostname).-d—A description of the VM that will be displayed in the Cryptographic Security Platform Vault for VM Encryption.-p—The passphrase assigned to the certificate when it was created. If you do not specify this parameter and the certificate has an associated passphrase, the registration process prompts you for the passphrase. Applies to Standard Authentication only.-v(optional)—The Vault ID of the Vault that will be displayed in Vault Management. If you do not specify vault_id, you will be asked whether you want to enter vault_id.-o—The one-time passphrase that will be used to encrypt the initial communication between this VM and the existing Cryptographic Security Platform Vault for VM Encryption cluster. If you do not specify this parameter, the registration process prompts you for the one-time passphrase. Applies to Standard Authentication only.The passphrase is valid for 15 minutes from the time it is created. Make sure you authenticate the VM in Cryptographic Security Platform Vault during this time. Authentication will fail after the passphrase has expired.
-z—The name of the Cloud VM Set defined in the Cryptographic Security Platform Vault for the VM Encryption cluster to which you want to assign this VM. Applies to Simplified or Automated Authentication only (the-aoption must be specified on thehcl registercommand).-n— The name of the Cluster Node Mapping that you want to associate with this VM. If you do not specify this option and one or more Cluster Node Mappings have been configured, the Policy Agent prompts you to select a Node Mapping from the list. If you do not want to use a Node Mapping, you must manually respond to this prompt. This option is mutually exclusive with the-Noption, described below, and it requires that the-aoption must be specified on thehcl registercommand.-N—Tells the Policy Agent that you do not want to use a Cluster Node Mapping, even if one is available. If you specify both-Nand-n, the Policy Agent ignores the-noption and does not assign a Node Mapping to the VM. Applies to Simplified or Automated Authentication only (the-aoption must be specified on thehcl registercommand).kc-hostname[:port],kc-hostname2[:port],...(required)—The list of IP addresses or hostnames for the Cryptographic Security Platform Vault nodes with which you want to register the VM. You must specify at least one Cryptographic Security Platform Vault node in this list. You must also specify a port if the Cryptographic Security Platform Vault nodes use anything other than the default port (443).If you are using the
-noption to specify a Cluster Node Mapping, this IP address will be the Cryptographic Security Platform Vault for VM Encryption node that the VM contacts to retrieve the Node Mapping information. After the Node Mapping has been retrieved, the Policy Agent ignores any other IP addresses in this list and only registers the VM with the Cryptographic Security Platform Vault for VM Encryption nodes contained in the Node Mapping.cert-file.cert—The name of the certificate file you copied to the target system if you are using Standard Authentication. If you are running thehcl registercommand from a directory other than the one where the.certfile resides, specify the full path to the.certfile as part of this option. If you did not create a certificate file in Cryptographic Security Platform Vault for VM Encryption, omit this option and use the-aoption instead.
The following command registers a VM with the "hq-vm-3" and the "HQ Windows 2022 Server" description, using standard authentication and a node at 10.238.32.74.
C:\> hcl register -h hq-vm-3 -d "HQ Windows 2022 Server" 10.238.32.74 ad85837b-9862-11e1-afd5-000c29de5d41_120507163538.certYou need to specify a passphrase that will be used for authentication with KeyControlEnter passphrase (min 16 characters): passphrase16chars Registered as hq-vm-3 with KeyControl node(s) 10.238.32.74Please login to the KeyControl node to complete the authentication of this nodeThe following command line registers the VM without prompting the user.
C:\> hcl register -h hq-vm-3 -d "HQ Linux Server Alpha" -p <certpassphrase> -o <onetimepassword> 10.238.32.74 ./install/entrust/cert/ad85837b-9862-11e1-afd5-000c29de5d41_120507163538.certRegistered as hq-vm-3 with KeyControl node(s) 10.238.32.74Please login to the KeyControl node to complete the authentication of this nodeThe following command registers a VM named "hq-vm-3" with the "HQ Windows 2022 Server" description and prompts the user for the account information, the cloud VM set, and the cluster node mapping.
C:\> hcl register -a -h hq-vm-3 -d "HQ Windows 2022 Server" 10.238.66.250Do you want to register into a Vault? (y/n) yPlease provide the vaultIDvaultid: d84243e7-d359-4179-9530-3497434e3192Please provide the login detailsusername: CloudAdminpassword: Available Cloud VM Sets--------------------------------------------------------------------------------SF-Datacenter--------------------------------------------------------------------------------Please specify Cloud VM Set to which this VM should be added: SF-DatacenterRegistered as hq-vm-3 with KeyControl node(s) 10.238.66.250Completing authentication for hq-vm-3 on KeyControl node(s) 10.238.66.250Authentication complete, machine ready to useGetting KeyControl Mapping informationThis VM can be added to one of the following KeyControl Mappings--------------------------------------------------------------------------------1 : SF-Datacenter-Map2 : West-Coast-Map--------------------------------------------------------------------------------Please select a numeric KeyControl Mapping ID (0 to skip): 1KeyControl Mapping: SF-Datacenter-Mapserver description First Node, ip 10.238.66.250, port 443server description Second Node, ip 10.238.66.251, port 443Updated KeyControl list with KeyControl nodes 10.238.66.250:443,10.238.66.251:443