Troubleshoot issues with discovery client

Latest: v6 v5

This document shows you how to resolve issues with the discovery client.

Use logs to identify issues

The discovery client generates log files that you can use for debugging. Logs are stored locally on the machine where you installed the discovery client in the C:\ProgramData\Google\mcdc\logs folder.

Note: The logs files are limited in size, therefore the discovery client periodically deletes the content of old logs.

Troubleshoot permissions and service accounts

If you experience issues with the authorization in connected mode, you might not have the permissions required to create a service account in your organization, or might lack the required roles to authorize the discovery client.

To resolve the issue, ask your organization administrator to create a service account for you, and to assign the roles/migrationcenter.discoveryClient role. Also, make sure that the Cloud Resource Manager API is enabled in the project.

If you have a newly created organization on Google Cloud, by default service account key creation is disabled. To enable service account key creation, make sure you have the Organization Policy Administrator role assigned, then follow these steps:

1. In the Google Cloud console, go to IAM > Organization Policies.
2. Click the policy named Disable service account key creation.
3. Click Manage Policy.
4. On the Edit policy page, in the Applies to section, select Customize.
5. In the Rules section, expand Edit rule, then set Enforcement to Off.
6. To finish, click Set Policy.

Troubleshoot installation issues

If you install or upgrade the discovery client, but you're not logged in as a local administrator, the MSI execution likely fails with the following error message:

Google Cloud Migration Center discovery client Setup Wizard ended prematurely
because of an error. Your system has not been modified. To install this program
at a later time, run Setup Wizard again. Click the Finish button to exit the
Setup Wizard.

To resolve the issue, right-click the MSI file and run it as an administrator.

In some cases, due to specific Windows versions or domain policies, the "Run as Administrator" option might be hidden. To resolve the issue, try the following workarounds:

• Preferred method: Open PowerShell as an administrator, and run msiexec.exe /i mcdc.msi /L*V "C:\installer.log".

  Tip: if you have issues installing with PowerShell, check if you're using relative paths or long paths.

• Alternative method: Edit the registry to show this option in the UI.