You can use the Migrate Agent utility for registration and discovery instead of automated discovery. Using Migrate Agent is required to register and discover details about source workloads in scenarios where automated discovery is not possible, such as:
When you deploy Migrate server in the cloud without deploying a site-to-site VPN between your network and your cloud environment.
When you plan cloud-to-cloud migrations without deploying a site-to-site VPN between the participating locations: your network, your source cloud environment, and your target cloud environment.
When corporate network or policy restrictions prohibit opening inbound ports on source workloads.
For information about inbound ports required for automated discovery of Windows and Linux workloads, see Section 2.6.1, Requirements for Discovery.
Migrate Agent enables you to migrate a Windows workload without opening any inbound ports, such as SMB or NetBIOS. Only HTTPS (TCP/443) and a replication port (TCP/3725 is the default) are needed outbound for the source Windows workloads. For source Linux workloads, you also need to open the SSH port (TCP/22). See Section 2.6.2, Requirements for Workload Registration.
When you use the Migrate Agent on the source workload, the source workload contacts the target workload for data transfers. The direction is controlled at the server level. You must reconfigure the replication port direction on the Migrate Server (SourceListensForConnection=False). See Configuring the Contact Direction for the Replication Port.
You must install Migrate Agent on each source workload. When you use the register option, Migrate Agent performs discovery locally on the workload and sends its details to the Migrate Server through HTTPS (TCP/443). After you register the workload, use the Migrate Web Interface to configure the workload migration to the target cloud where the Migrate Server instance is deployed.
Registered workloads differ from discovered workloads in the following ways:
Registered source workloads do not store the source credentials on the Migrate Server.
You must use Migrate Agent to install, upgrade, and remove the Windows PlateSpin drivers from registered source workloads.
After you delete the contract for a registered source workload, use the cleanup comman to remove the OFX controller from the workload. See clu | cleanup for Windows workload and cleanup for Linux workload
See the following procedures in Section 19.7, Registering Workloads and Discovering Details with Migrate Agent: