For information about the software, network, and firewall requirements that systems in your environment must meet before you add workloads to Migrate, see the following information as appropriate:
Discovery and inventory process: Requirements for Discovery
-OR-
Registration using Migrate Agent: Requirements for Workload Registration
Table 19-2 provides guidelines for machine type selection, credential format, and syntax for discovery parameters for workloads.
Table 19-2 Guidelines for Machine Type and Credentials for Source Workloads
|
To Discover |
Machine Type |
Credentials |
Remarks |
|---|---|---|---|
|
All Windows workloads |
Windows |
Local or domain administrator credentials. |
For the username, use this format:
|
|
All Linux workloads |
Linux |
Root-level user name and password |
Non-root user accounts must be properly configured to use sudo. See KB Article 7920711. |
|
Windows workloads in AWS (no VPN connection, C2C migration from AWS to Azure or to vCloud) |
Windows |
For C2C migrations from AWS, log in to the source Windows workload in AWS with RDP, then use Migrate Agent Utility to register the workload. See Windows Workload Registration and Discovery with Migrate Agent. |
|
|
Linux workloads in AWS (no VPN connection, C2C migration from AWS to Azure or to vCloud) |
Linux |
User name with root-level access and the private key file you created for your AWS EC2 Key Pair |
For C2C migrations from AWS, log in to the source Linux workload in AWS with SSH, then use Migrate Agent Utility to register the workload. See Windows Workload Registration and Discovery with Migrate Agent. Non-root user accounts must be properly configured to use sudo. See KB Article 7920711. NOTE:For AMI images in AWS, use the default non-root user system account that is automatically configured to use sudo. To run Migrate Agent commands, run the sudo -i command to access the root shell, and then run the Migrate Agent commands. |