This document is designed to help with common issues / failures that may occur when automatically deploying the Hyper-V Host agents through the Management Console.
Version 9
Here is a list of common failures when deploying the VM Backup Hyper-V Host Agent, and how to resolve each failure:
The host machine must have the full .NET4.8 installation
VM Backup requires .NET4.8 to be installed on each host machine. Ensure that it's installed, if not you can find the installation link here: https://www.microsoft.com/en-us/download/details.aspx?id=17851
The host machine and VM Backup server have a time offset of more than 5 minutes
Correct the time and timezone of both machines to ensure they are in sync.
Microsoft DCOM hardening update
As of March 2023, Microsoft has finalized hardening the security for the DCOM protocol by enabling it by default, which means that you must apply the latest security updates as of March 2023. Microsoft removed the ability to disable it and this means that the latest security Windows Updates must be installed. More information on this can be found here.
The host machine is not domain joined (WORKGROUP)
If the host machine you are trying to add is not domain joined i.e. a workgroup, ensure that you are using the "administrator" account. Another account with administrative privileges will fail to deploy the sub-agent.
An old installer is getting pushed out
Delete the C:\ProgramData\Hornetsecurity\VMBackup\Installers folder from both the machine running VM Backup and the Hyper-V host. Then re-attempt the deployment.
The agent was actually pushed and installed successfully but took longer to start than expected and the UI times out
Click on the Discover Virtual Machines button on the host list in the UI. The connection will be refreshed and if the agent is installed and running then the UI will be corrected.
A previous install / uninstall of the VM Backup is on this machine required a restart
Restart the Hyper-V Host and try push the agent again.
Check for a Windows Error 1219
Check this KB article as you might be running into a Windows Error 1219.
VM Backup v8.x is running on the Hyper-V Host
You must first uninstall v8.x before pushing a v9.0 agent to that machine. Uninstall v8 using the REMOVEALTARO command in command prompt or using the Windows Uninstall Control panel and then try the deployment again.
You have a newer version of the VM Backup Hyper-V Host Agent software running on the Hyper-V Host
You cannot push an Agent from an older version of VM Backup Hyper-V Backup if the host is already running a newer version. You need to uninstall the Hyper-V Host agent using the REMOVEVMB command in command prompt or using the Windows Uninstall Control panel and try again.
Windows Firewall is blocking ports required to copy over the installer files from the VM Backup Hyper-V Backup machine to the Hyper-V Host
Open the ports required (as below) on your firewall:
(a) to copy over the installer and invoke it: TCP 445 and UDP 445
(b) for VM Backup and VM Backup Hyper-V Host agent to communicate: TCP 36021and 36022
The Host machine has other users logged to terminal services. Even though pushing the agent is successful, it still indicates that it requires an upgrade
You need to uninstall the Hyper-V Host agent using the REMOVEVMB command in command prompt or using the Windows Uninstall Control panel and try again.
If all else fails... you can easily install the agent manually
Version 8
Here is a list of common failures when deploying the VM Backup Hyper-V Host Agent, and how to resolve each failure:
The host machine must have the full .NET4.7.2 installation
VM Backup requires .NET4.7.2 to be installed on each host machine. Ensure that it's installed, if not you can find the installation link here: https://www.microsoft.com/en-us/download/details.aspx?id=17851
The host machine and VM Backup server have a time offset of more than 5 minutes
Correct the time and timezone of both machines to ensure they are in sync.
Microsoft DCOM hardening update
As of March 2023, Microsoft has finalized hardening the security for the DCOM protocol by enabling it by default, which means that you must apply the latest security updates as of March 2023. Microsoft removed the ability to disable it and this means that the latest security Windows Updates must be installed. More information on this can be found here.
The host machine is not domain joined (WORKGROUP)
If the host machine you are trying to add is not domain joined i.e. a workgroup, ensure that you are using the "administrator" account. Another account with administrative privileges will fail to deploy the sub-agent.
An old installer is getting pushed out
Delete the C:\ProgramData\Altaro\AltaroBackupProfile\Installers folder from both the machine running VM Backup and the Hyper-V host. Then re-attempt the deployment.
The agent was actually pushed and installed successfully but took longer to start than expected and the UI times out
Click on the Discover Virtual Machines button on the host list in the UI. The connection will be refreshed and if the agent is installed and running then the UI will be corrected.
A previous install / uninstall of the VM Backup Hyper-V backup software on this machine required a restart
Restart the Hyper-V Host and try push the agent again.
Check for a Windows Error 1219
Check this KB article as you might be running into a Windows Error 1219.
VM Backup Hyper-V Backup v4.x is running on the Hyper-V Host
You must first uninstall v4.x before pushing a v5.0 agent to that machine. Uninstall v4 using the REMOVEALTARO command in command prompt or using the Windows Uninstall Control panel and then try the deployment again.
You have a newer version of the VM Backup Hyper-V Host Agent software running on the Hyper-V Host
You cannot push an Agent from an older version of VM Backup Hyper-V Backup if the host is already running a newer version. You need to uninstall the Hyper-V Host agent using the REMOVEALTARO command in command prompt or using the Windows Uninstall Control panel and try again.
Windows Firewall is blocking ports required to copy over the installer files from the VM Backup Hyper-V Backup machine to the Hyper-V Host
Open the ports required (as below) on your firewall:
(a) to copy over the installer and invoke it: TCP 445 and UDP 445
(b) for VM Backup Hyper-V Backup and VM Backup Hyper-V Host agent to communicate: TCP 35108 and 35221
The Host machine has other users logged to terminal services. Even though pushing the agent is successful, it still indicates that it requires an upgrade
You need to uninstall the Hyper-V Host agent using the REMOVEALTARO command in command prompt or using the Windows Uninstall Control panel and try again.