https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNjAwIiwiaGFzaCI6ImFlMzVkYmUxLWVkNGQtNGFkYi04OTA0LTM1ZjBiZmYzZWJmZiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Naming requirement for correct functioning of the "Guest to Agent Relationship" feature

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.
KB ID:
1600
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.7
Published:
2012-05-05
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.