software inventry failing in azure migrate

Question

software inventry failing in azure migrate

Muhammad Hafiz Imran 0

I have installed the Azure Migrate appliance for VMWare ESXi, and it can discover the server, but is unable to get the software inventory, although I have provided the domain admin credentials, and the strange this is that only one server gave me the application inventory out of 84 servers.
The error I am getting is "Credentials provided for appliance to access the server are incorrect" or "Credentials are not provided in appliance to access the server for guest discovery."

I can connect the servers from the ESXi host using RDP/ping and command Invoke-Command -ComputerName machinename/IP -Credential $cred1 -ScriptBlock { hostname }, but still servers are not giving the software inventory.

Note: I am using Visual Studio Enterprise Subscription – MPN subscription.

Any help?

2 answers

Your answer

Answer 1

Gulnaz Mushtaq 410 MVP

First check whether the Azure Migrate appliance is deployed and configured and discovery is working i.e., VM list is populated or not. Have you provided domain admin credentials? Also check that servers are reachable via RDP and Invoke-Command or not.

Try the following troubleshooting:

As Azure Migrate uses WMI over DCOM to collect software inventory. You need to open Port 135. Do random ephemeral ports (49152–65535). Allow proper WMI permissions on each guest VM.

Now run following PowerShell command on the target machine to test WMI:

Get-WmiObject -Class Win32_Product -ComputerName <VMName> -Credential (Get-Credential)

If this doesn’t work it means there's likely a DCOM or firewall issue. Therefore, temporarily disable the firewall for testing. Review GPOs blocking remote WMI.

Sometimes with domain admin if UAC remote restrictions are enabled, WMI queries may not work. In this case you should check the following registry value on the target servers:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy

Set it to 1 (DWORD). If you cannot see this you can create it.

One more thing to confirm that the account is not just a member of Domain Admins, but has explicit local admin rights on the VMs.

Muhammad Hafiz Imran 0 Reputation points

2025-07-31T13:11:21.6066667+00:00

I have the same configuration. I can telnet the target machine on port 135 from the appliance and also run the Get-WmiObject -Class Win32_Product -ComputerName <VMName> with success, but still the application/software discovery is showing an error. "Either no credentials have been provided for the server or you have provided domain credentials with incorrect domain name on the appliance."
Gulnaz Mushtaq 410 Reputation points MVP

2025-08-02T20:25:42.9666667+00:00

If you still get this error, you should go to the Azure Migrate appliance portal https://<appliance-ip>:44368 and go to Manage Credentials option. Here you should re add the domain credentials. Follow one of the below formats:

******@contoso.com OR <CONTOSO\xyzuser>

Now go to Manage Machines option. Click Edit Credentials Mapping. Make sure that correct credential is mapped for each machine.

Use a wildcard match if many machines follow the same pattern, e.g:

*.contoso.com

Now run software inventory collection

If the above solution doesn't work, you should delete and add the credential again.

For that, delete the credential from Manage Credentials. Once this is done then reboot the appliance. Now add it again cleanly and map it again under Manage Machines

Let me know if you need further help.
Muhammad Hafiz Imran 0 Reputation points

2025-08-04T13:22:50.7433333+00:00

@Gulnaz Mushtaq I have seen this article. When you are running the VMWare appliance, you can not find these options, like managing the machine individually.

Answer 2

Hi @Muhammad Hafiz Imran ,

Please try the following steps and ensure that the confidence level is at least 4 stars.

In the meantime, perform the steps below and revalidate

Revalidate Credentials in Appliance Portal

Use either Domain Admin or Local Administrator credentials.

Go to the Azure Migrate appliance portal, remove and re-add credentials, and revalidate.

2. Confirm WinRM Configuration on Target VMs

Run the following command on each VM (or via GPO/script):

PowerShell command >>>>>>>>>. winrm quickconfig

Kindly ensure WinRM service is enabled and running.
Allow WinRM in Windows Firewall (TCP ports 5985 and optionally 5986 for HTTPS).
3. Confirm Required VM Settings

Setting Requirement

Firewall Inbound access on TCP 5985 (HTTP) and optionally 5986 (HTTPS) enabled.

WinRM Must be enabled and running on all VMs.

Credentials Use local admin or domain admin accounts with VM access permissions.

Network Access Appliance must reach VMs on ports 135, 139, 445, and 5985.

DNS Resolution Appliance must resolve each VM's hostname. Use FQDNs if required.

Please do let me know if still not resolved. I will be happy to help you further.

Share via

software inventry failing in azure migrate

2 answers

Your answer