Redeploying Hosts

Redeploying hosts may solve certain issues with the host, such as authentication issues related to management connections. Host redeployment allows you to regenerate the credentials used for managing the host. With agentless host redeployment you may also specify new credentials for accessing the management account. Redeploying hosts does not remove any host or management data associated to them.

To redeploy a host that is in the monitored or the managed state:

1. On the Hosts page, perform a Redeploy action on the target host(s). Doing so switches the target hosts to the available state, which enables the hosts to be deployed again.

   Agent-based hosts will automatically redeploy themselves the next time they connect to Key Manager. For Agentless hosts, you will still need to manually deploy the host.

2. This step only needs to be performed for agentless hosts.

   Deploy the target hosts in one of the following ways:

   • On the Hosts page, select the target hosts, then initiate a Deploy action.

   • Add the host to the managed environment, similarly to how you would add a new host. Adding agentless hosts is described in Adding Agentless Hosts.

Key Manager starts jobs to deploy the target hosts. The hosts will be in the monitored or the managed state once the deployment jobs finish successfully.

note

A host can be redeployed only if it retains its unique host identifier. On Unix hosts, the unique host identifier is in the file /var/sshmgr-unique-id. On Windows hosts, the value is written to the registry path HKLM\SOFTWARE\SSH Communications Security\SSH Universal Key Manager Agent\UniqueId (on 32-bit Windows), or to HKLM\SOFTWARE\Wow6432Node\SSH Communications Security\SSH Universal Key Manager Agent\UniqueId (on 64-bit Windows).

Redeploying a host updates its deployment date.