If the DaaS Agent fails to pair during the image import process, use the following instructions to help troubleshoot and resolve the issue.

Check Configuration

Confirm that all the following items are configured correctly:
  • VMware Tools is up to date.
  • VM hardware version is up to date.
  • Guest OS and VM names match.
  • Correct Horizon Agent Installer version is installed.
  • VNIC adapter type is VMXNET3.
  • VNIC is assigned to the correct port group and connected in the VM properties in vCenter.
  • Domain Controller is reachable from the VM.
  • Firewall is turned off (not only that the firewall service is deactivated).

Re-Enable Agent Pairing

If you are installing the Horizon Agent Installer on an image that has already had the DaaS Agent installed, requires an agent reinstall, or is being upgraded from a previous version, you must update some registry values after installing the DaaS Agent. The previous install has left some registry settings behind and must be reset. When the platform initiates the pairing process with the DaaS Agent, it updates the registry to deactivate the agent from continuing further attempts of re-pairing. As a result, if the pairing process fails for a valid reason, further attempts to reinstall the agent fail because this registry key is stopping the process.

To re-enable agent pairing:
  1. Stop the VMware DaaS Agent service in services.msc.
  2. Open regedit and navigate to:
    Computer\HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware DaaS Agent
  3. Edit the EnableBootstrap REG_DWORD key and change the value from 0 to 1.
  4. Clear the vmid REG_SZ value of any text.
  5. On the tenant appliance:
    1. Log into the tenant appliance element database:
      psql -Uadmin edb
    2. Turn on extended display:
    3. Run the following commands:
      select * from t_general_machine where name=’VMNAME’;
      Note the tools_state, agent_version, and is_agent_pairing_acknowledged fields in the table.
       update t_general_machine set is_agent_pairing_acknowledged=’f’ where name=’VMNAME’;
  6. Switch back to the desktop and start the DaaS Agent service.
  7. Log into the Administration Console and reinitiate the DaaS Agent pairing process by importing it as a new image. You might have to convert it back to a desktop first before you can try importing it again.