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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTQ4IiwiaGFzaCI6Ijk0M2U1OWU5LTIxMmItNGI0Ny1iMzdiLWI4YTVkOWViNmU5MiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Physical and virtual machines with identical names

Challenge

When a physical and a virtual object with identical names are present in SCOM and in the SCOM database they tend to get mixed up by the application.

Cause

Unfortunately, nworks currently does not support machines having the same name within one environment. nworks uses VM Name as a unique ID, so there is no way to use the VMware underlying unique ID. Also there is a SCOM issue with displaying performance graphs and instead of the Display Name being used, the ID will be used instead. This makes the graphs not as user-friendly because it’s very difficult when viewing graphs to relate the VMware ID to the Display Name you are familiar with.

Solution

To resolve, rename the machines in the environment.

KB ID:
1148
Version:
5.x
Published:
2011-08-05
Last Modified:
2020-08-13
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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later