Operational Defect Database
BugZero found this defect 4467 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1600
Naming requirement for correct functioning of the "Guest to Agent Relationship" feature
Last update date:
8/28/2020
Affected products:
Veeam Management Pack for Microsoft System Center
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
To make the VM and OpsMgr Agent integration work properly, it is necessary that VMs discovered by the VMGUEST contains OpsMgr Agent discovery have an identical display name and NETBIOS name.
Cause
If the VMware display name is different from the NETBIOS name, the VM will have two source monitoring objects: the agent + collector machine (VEM Server) and SCOM RMS. This will result in 10401 and 26004 error messages in the SCOM RMS Event Log.
Solution
The VMs discovered by the VMGUEST contains OpsMgr Agent discovery must have identical display and NETBIOS names.The other approach would be to keep the VMGUEST contains OpsMgr Agent discovery disabled.
More Information
Note that the 10401 and 26004 errors are not necessarily caused by incorrect VM naming. If you are sure the VMs are named as required, please contact Veeam Support for assistance.
