Azure Migrate Configuration manager - "Add Discovery Source" gives error: Failed to fetch BIOS GUID for the server

Hindeep Singh 0 Reputation points
2023-08-10T12:47:27.0566667+00:00

In the Azure Migrate Configuration manager, when I try to add a server in the "Add Discovery Source" it is giving me error:

Failed to fetch BIOS GUID for the server 'x.x.x.x'. BIOS GUID is important to uniquely identify and discover a server.

This is a Centos VM, while I was getting similar error in another VM I switched to password-less sudo for my user and it resolves. But issue persists in this VM. Discovery has worked fine for all the other VMs/Servers using this appliance.

All checks are passed for the appliance and other things are working fine.

I have even used: Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
and executed the following commands from the server (on which Azure Migrate Appliance is installed) which are working fine:

cat /sys/class/dmi/id/product_uuid

I even added my user to the root group, but it did not work.

Please suggest.

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
751 questions
{count} votes

2 answers

Sort by: Most helpful
  1. JimmySalian-2011 42,066 Reputation points
    2023-08-11T15:18:22.4133333+00:00

    Hi Hindeep,

    There is article on this and solution fixed the similar issue like you are facing see if it helps - https://cloudcomputingwithme.wordpress.com/2021/09/15/failed-to-fetch-bios-guid-error-occurs-for-the-server-during-validation/

    Hope this helps.

    JS

    ==

    Please Accept the answer if the information helped you. This will help us and others in the community as well.


  2. Paul Doherty 0 Reputation points
    2024-01-25T12:06:27.96+00:00

    use root, this is the way

    0 comments No comments