issue where the VMs UUID was lost

GUNJOHN Lv1Posted Dec-09-2025 12:04

I migrated a VM from vSAN to Sangfor HCI and encountered an issue where the VM’s UUID was lost.
Because of this, I am unable to install the Veeam Agent Base — the agent installation keeps failing.
Does anyone know how to fix this issue?

UUID.png (353.73 KB, Downloads: 88)

UUID.png

UUID.png (353.73 KB, Downloads: 90)

UUID.png

By solving this question, you may help 782 user(s).

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Zonger Lv5Posted Dec-10-2025 04:00
  
When migrating VMs from VMware vSAN to Sangfor HCI the VM's UUID is not preserved because Sangfor HCI generates a new virtual hardware ID unless the migration is done through Sangfor's official VMware Import Tool.
A missing or zeroed UUID (as shown: 00000000-0000-0000-0000-000000000000) causes Veeam Agent Base to fail because Veeam uses the SMBIOS/UUID for host identification and licensing.

SOLUTION 1:

Regenerate VM UUID from Sangfor Console. Some Sangfor HCI versions allow you to set the UUID manually:

Shut down the VM.

Go to HCI → VM → Edit → Advanced → UUID / Hardware Info.

Enter a valid UUID (you can restore the original VMware UUID if known).

Start the VM again.

Re-run the Veeam Agent installation.

SOLUTION 2:

Re-import VM using Sangfor "Import from VMware" Tool. If UUID is critical for backups:

Shut down the VM on VMware.

Use Sangfor HCI Import from VMware tool.

Select "Preserve UUID" option.

Import the VM again, the UUID will be kept.
pbeugenio Lv2Posted Dec-10-2025 09:27
  
Hi,

Go to Edit VM > Advanced > Enable UUID Generator (cannot generate ID itself)
Newbie846490 Lv1Posted Dec-10-2025 15:43
  
Ensure that the VM configuration files (like .vmx for VMware) are intact and not corrupted. Sometimes, migration processes can lead to file inconsistencies https://quordle-wordle.com

Newbie030823 Posted Dec-11-2025 09:52
  
This usually happens when a VM is migrated between different hypervisor platforms without preserving the SMBIOS/UUID metadata.

Here are a few things you can try that normally fix this:

1. Recreate or manually assign a UUID in the Sangfor VM settings

Most HCI/virtualization platforms (including Sangfor) allow you to define or regenerate:

UUID

SMBIOS UUID

Machine ID

Check the VM’s “Advanced” or “Hardware” section and see if there’s an option to auto-generate a new VM UUID or manually enter one. After applying, reboot the VM and try running the Veeam Agent installer again.

2. Verify UUID inside the guest OS

Inside the OS (Windows):

Run:

wmic csproduct get uuid


If it returns zeros (0000-…), or is blank, the hypervisor is not injecting a valid UUID to the guest.

After fixing the VM metadata, this command should return a normal UUID.

3. Check if Sangfor HCI has an “import VM” or “rebuild metadata” function

On some versions, after migrating a VM from another platform, you need to run an “Import VM” or “Rebuild VM Info” operation to populate:

UUID

Serial number

Manufacturer fields

This often fixes missing hypervisor → guest metadata.

4. Reinstall the Sangfor Guest Tools (if available)

Some HCI stacks use guest agents/tools to push hardware identifiers into the VM. Make sure you have the latest Sangfor tools installed.

5. As a last resort: clone the VM in Sangfor

Cloning the VM sometimes forces the platform to generate a fresh UUID for the new copy. Veeam usually accepts this without issues.
see more here: https://knowledgebase.sangfor.co ... 2articleType%22%3A1,%22articleId%22%3A%22c8bfc75ff7ad4ee4b4131720473c35bc%22,%22keyword%22%3A%22%22%7D <a href="https://golf-hit.io/">golf hit</a>

I Can Help:

Change

Moderator on This Board

135
80
24

Started Topics

Followers

Follow

Board Leaders

NyxZale...

Weekly Sharers

Newbie5...

Weekly Questioners