Appliance Configuration Manager Failing to Validate on source discovery

Question

Am getting stuck on step 2
Add discovery source validation failed with details:
An error occurred as the URL provided for discovery of Vcenter server is not valid URL.

Answer 1

Hello @Salim - Welcome to Microsoft Q&A community forum!

Sorry for the inconvenience this must have caused. Please check the following:

Ensure the vCetner has appropriate permissions - https://learn.microsoft.com/en-us/azure/migrate/tutorial-discover-vmware#create-an-account-to-access-vcenter-server

Add the appliance to the host file for DNS resolving

To validate the connectivity from the appliance, run the following commands to set up PowerCLI on the appliance server and connect to vCenter through PowerCLI

Install-Module -Name VMware.PowerCLI -AllowClobber
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore

Connect to vCenter Server from appliance by providing the vCenter Server IP address in the command and credentials in the prompt:

Connect-VIServer -Server <IPAddress of vCenter Server>

Reference : Troubleshoot the ongoing server discovery, software inventory and SQL discovery - Azure Migrate | Microsoft Learn

More Details :
How does the Azure Migrate appliance communicate with vCenter Server and the Azure Migrate service?
The appliance connects to vCenter Server (port 443) by using the credentials you provided when you set up the appliance. It uses VMware PowerCLI to query vCenter Server to collect metadata about the VMs managed by vCenter Server. It collects configuration data about VMs (cores, memory, disks, NICs, and so on) and also the performance history of each VM for the past month. The collected metadata is then sent to Azure Migrate Server Assessment (over the internet via HTTPS) for assessment.

Also verify the port access :
vCenter Server Inbound connections on TCP port 443 to allow the appliance to collect configuration and performance metadata for assessments.
The appliance connects to vCenter on port 443 by default. If vCenter Server listens on a different port, you can modify the port when you set up discovery.

----------------------------------------------------------------------------------------------------------------------

If the response helped, do "Accept Answer" and up-vote it

Answer 2

Hello @Salim Can you please share the solution with us.