Remove BIOS UUID from identification rules

Idea ID 1664821

Remove BIOS UUID from identification rules

0 Votes

Using BIOS UUID as an attribute in the identification rules is a problem because it's no longer stable in today's virtual enviornments.  VMware documents that the UUID can change when a VM is moved or copied.  IN the case of copying a VM, the fact that it changes is good.  In the case of moving a VM, the fact that it can change is bad, as UD would consider the VM a different server, even though nothing else has changed

https://kb.vmware.com/s/article/1541

Please take the BIOS UUID out of the identification rule

(submitted on behalf of Cigna)

1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Declined

Unfortunately, this is not something that we can change.  There are 2 main reasons

1. There is a use case to keep the BIOS UUID in the identificaiton rules because when a VM is copied, the BIOS UUID chanigng is the correct action, and UCMDB should create a different CI as a result.

2. This BIOS UUID rule has been in place for a long time.  If we were to pull this out of the identification rules OOTB, the impact on all customers could be significant.

Therefore, the only option is for a cusotmer with this issue to modify the OOTB identification rules to account for how their own business addresses this problem.  This is not a change we can globally make to the UCMDB product

About the Author
Bill has over 26 years of experience in the IT industry focusing on providing business solutions utilizing HPE Software’s tools at enterprise scale. He comes from the HPE-IT organization where he managed the first deployment of HPSC (now HPSM) and then later UCMDB with its discovery partner UD. Bill also managed a team of IT Developers, who created customized configuration management solutions for HPE-IT and HPE’s ES clients.
Most "Liked" Contributors
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.