Backstory: The Hyper-V server went down hard and is not coming up any time soon. It was only functioning as a Veeam backup server which local virtualization capability. To get the backups operationally as quickly as possible, I stood up a VM on the VMware host and restored the Veeam config.
Problem: Veeam thinks the VMware VM is still a Hyper-V server, so it's trying to update the Hyper-V Integration component which is no longer relevant. Can't seem to get around it. Of course, when I try to upgrade anyway it fails because the VM isn't a Hyper-V server.
BEO-VEEAM was successfully modified.
OS version: Microsoft Windows Server 2019 Standard 64-bit (10.0.17763 build:17763).
Hardware info:
Chassis type: Virtual (VMware)
Cores count: 4
Components:
Hyper-V Integration using port 6163
Installer using port 6160
Mount Server using port 6170
Transport using port 6162
Veeam Agent for Linux Redistributable
Veeam Agent for Mac Redistributable
Veeam Agent for Microsoft Windows Redistributable
Veeam Agent for Unix Redistributable
Veeam Backup VSS Integration using port 6210
Veeam Distribution Service using port 9380
Veeam VSS Hardware Snapshot Provider using port 6211
vPower NFS using port 6161
