Skip to main content
Re-register a Hyper-V host
Updated over a week ago

πŸ“ Note
​When re-registering a server or host, or restarting a service, do not make any manual modifications to the configuration file folder. These modifications might lead to errors in reactivation, backup, or restore operations.

If you want to make any manual modifications to the configuration file folder, contact Support.


Re-register a Hyper-V host if:

  • You initially registered it as a standalone host, and you want to re-register the host as a part of a cluster

  • You initially registered it as a standalone host, and you want to re-register a host that is managed using System Center Virtual Machine Manager (SCVMM)

  • You initially registered the host as a part of the cluster, and you want to re-register a host that is managed using SCVMM

  • You refreshed the hardware of the host and the host is disconnected from the Druva Cloud after the hardware refresh

  • Your host is disconnected from the Druva Cloud if the Phoenix.cfg (For agent version prior to 7.0.0) / Config.yaml (For agent version 7.0.0 and later) file gets deleted

You can use Druva to re-register or re-add a Hyper-V host so that:

  • It is not registered as a new host with Druva.

  • The Enterprise Workloads agent creates successive recovery points of the virtual machines running on the host.

  • The Druva Cloud does not store the recovery points as recovery points from a different host.

To re-register a host, download the Enterprise Workloads agent from the Management Console, and install and activate the Enterprise Workloads agent once again on the host. Re-registration of a host requires three steps:

  1. Download the Enterprise Workloads agent and generate an activation token

  2. Install the Enterprise Workloads agent

  3. Activate the Enterprise Workloads agent


πŸ“ Note
​If you plan to change the management type of the host virtual machine, such as SCVMM, Standalone, or Cluster, the state of the host virtual machine on the Druva Cloud must be in sync with the state of the virtual machine in your infrastructure. Before the re-registration of the host, ensure that the host is connected to the Druva Cloud and the virtual machine list is refreshed. If the host is disconnected, you must first re-register the host with the same management type, refresh the list of virtual machines, and then re-register to change the management type.


Step 1: Download the Enterprise Workloads agent and generate the activation token

To re-register a host, perform the following steps:

  1. Log on to Management Console.

  2. select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.

  3. In the left navigation pane, click Hosts. On the Hosts page, select the host that you want to re-register.



    β€‹πŸ“ Note
    ​You can apply filters based on VM, Host, Cluster, or SCVMM.


  4. Click more options and then click Re-register.

    Reregister.png
  5. Click Proceed on the Re-register Hyper-V Host dialog.

  6. On the Re-register Hyper-V Host page, click Check prerequisites and ensure that you review the requirements before configuring Hyper-V hosts for backup.

  7. Under Download and install agent on the host, do one of the following:

    • If you have not yet downloaded the Enterprise Workloads agent installer, click Download. The agent download starts on the same browser page.

    • If the Enterprise Workloads agent has already been downloaded, proceed to the Activate Host for Backup section.

  8. Under the Activation Token field, click the Copy Token icon to copy the activation token and save it in a text file.



    β€‹πŸ’‘ Tip

    Ensure that you use this activation token for the correct host. If you use this re-registration activation token to re-register a different host, backup jobs will fail for virtual machines running on the other host as well for the virtual machines running on the host you originally wanted to re-register. In addition, on the Hosts tab of the Hyper-V page, details of the other host become identical to the host you originally wanted to re-register.


  9. Click Done.

Step 2: Install the Enterprise Workloads agent

Before you begin, ensure that:

  • You are logged in as an administrator to the host.

  • Your host matches the requirements listed in the support matrix.

  • You have downloaded the Enterprise Workloads agent installer on your host. The installer is available on the Druva downloads page. You can also download the installer from the Management Console at the time of registering hosts.

Perform the following steps to install the agent:

  1. Copy the downloaded Enterprise Workloads agent installer to the host on which you want to install it.

  2. Double-click the Enterprise Workloads agent installer. The installation wizard appears.

  3. Accept the license agreement and click Next.

  4. Use the local system account for installing the agent on the Hyper-V host.

  5. In the Install location box, enter or select the full path to the installation home directory.

  6. Click Install.

  7. After the installation completes, click Finish.

Command-line install

From the command prompt, run the following command:
​For agent version prior to 7.0.0

msiexec /i <path to Phoenix msi> /qn /quiet /log <path to log file>
​
​For agent version 7.0.0 and later
​​msiexec /i <path to EnterpriseWorkloads-UnifiedAgent msi> /qn /quiet /log <path to log file>


​For example:
​For agent version prior to 7.0.0

msiexec.exe/i C:\Users\Administrator\Downloads\Phoenix-6.0.1-154609.msi /qn/quiet/log C:\Users\Administrator\Downloads
​
​For agent version 7.0.0 and later
​msiexec.exe/i C:\Users\Administrator\Downloads\EnterpriseWorkloads-UnifiedAgent-7.0.0-453279.msi /qn/quiet/log C:\Users\Administrator\Downloads
​

Step 3: Activate the Enterprise Workloads agent

After you install the Enterprise Workloads agent, activate it on the Hyper-V host to authenticate the incoming backup and restore requests. To activate the Enterprise Workloads agent:
​Install the agent and register a Hyper-V host

Did this answer your question?