@AnuragSingh-MSFT Azure Migrate appliance (windows Server 2016 ) default in workgroup network.. and my machine in domain network.. solved my issue after appliance added in domain. now we are able to discover software inventory also.
Azure Migrate Windows Software Inventory Data not available
Client credentials are correct, WinRM service is runing , also firewall allowed winrm service... but still getting below error
Error ID
60001
Error message
Unable to connect to server 'NGPDC.ngpclick2cloud.com' due to an error. Error code: 'UnableToConnectToPhysicalServer' Error details: 'Unable to connect to this machine. The error per IP is: [IP: NGPDC.ngpclick2cloud.com, Error:Unable to connect to server 'NGPDC.ngpclick2cloud.com' due to an error. Error code: '-2146233087' Error details: 'Connecting to remote server NGPDC.ngpclick2cloud.com failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved. For more information, see the about_Remote_Troubleshooting Help topic.'.] [IP: 192.168.2.170, Error:Unable to connect to server '192.168.2.170' due to an error. Error code: '-2146233087' Error details: 'Connecting to remote server 192.168.2.170 failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030d occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.'.] [IP: fe80::f910:3f12:c7e7:dea1, Error:Unable to connect to server 'fe80::f910:3f12:c7e7:dea1' due to an error. Error code: '-2146233087' Error details: 'Connecting to remote server [fe80::f910:3f12:c7e7:dea1] failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030d occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.'.] '.