Today one post about things I see sometimes in the field.
Today I want to show you how to fix the issue when you get servers and clients with the same SMBIOS ID. Normally that would be an issue but as soon as you try to management them with System Center Virtual Machine Manager or Configuration Manager it will become one. Both tools use the SMBIOS ID to create a primary key in their databases to identify the system.
Currently I only know the following trick to fix the issue and that one would be extremly annoying on many clients or servers but it actually work.
First you need two tools.
1: Rufus – To create a bootable USB Stick
2: AMIDMI – With that tool you can overright the SMBIOS ID
Now create the Bootstick with Rufus and copy the AMIDMI file on the stick.
Reboot your from the stick.
Navigate to the folder with your AMIDMI file and run the command amidmi /u
Afterwards you can reboot the system and start Windows again.
When you are working with Virtual Machine Manager, you need to remove the host from your management consolte and add it again. After the host is discovered again, you can see the new SMBIOS ID.
I currently saw these issues with following motherboard vendors:
- ASRock (Client & Rack)
- ASUS (Client)
- SuperMicro (Server & ARM)
- Fujisu (Server)