Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

WMI UUID Differs from VirtualCenter UUID (1880)

Last Updated: 4/15/2011Categories: InformationalTotal Views: 13168Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Details

I need to identify my virtual machines uniquely, for inventory purposes. The UUID of a virtual machine is available in the VirtualCenter client, but the value does not match the UUID reported by WMI (Windows Management Instrumentation) in the guest operating system. Why is this? Can I depend on the stability of either of these values?

Solution

VMware VirtualCenter assigns a unique, 16-byte identifier string (a UUID) to each virtual machine it manages. The UUID is stored in the virtual machine's configuration file (.vmx file) and can be accessed with the VirtualCenter client or the Virtual Infrastructure SDK. The value of the UUID is fixed; the format of the UUID differs, depending on the way in which it is retrieved.

In the virtual machine's configuration file, the UUID is stored under the "uuid.bios" key. The format separates the bytes with spaces and a hyphen. A sample UUID looks like this:

00 11 22 33 44 55 66 77-88 99 AA BB CC DD EE FF

The format used in the configuration file is the same format reported by the SDK for VirtualMachineInfo.uuid and VirtualMachineInfo.config; the latter is an array of properties retrieved from the configuration file.

However, the format of the UUID is different when it is used as a virtual machine identifier in the /vm path hierarchy. There the UUID is presented in a format described in ISO 11578. In this format, the UUID has a different byte order, and several hyphens are used to separate some of the bytes. The sample UUID shown above would be reported in this format for ISO 11578 compatibility:

33221100-5544-7766-8899-AABBCCDDEEFF

Note that Microsoft's WMI interface also reports a virtual machine's UUID to the guest operating system. This UUID is in the ISO 11578 format, and can't be compared directly to the internal form of the UUID.

As long as you retrieve the UUID in a consistent way, it retains a consistent value. You should not try to compare the value of the UUID when obtained from different sources without appropriate format conversion.

For more information on managing UUIDs when migrating virtual machines, see www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1541.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.0.x

VMware VirtualCenter 1.3.x

VMware VirtualCenter 1.2.x

VMware VirtualCenter 1.1.x

VMware vCenter Server 6.x

VMware vCenter Server 5.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant