Use information in this section to help troubleshoot common problems that might occur during migration of workloads to Microsoft Azure Cloud.
Issue: PlateSpin Migrate must be able to programmatically deploy a PlateSpin Migrate Replication Environment (PRE) VM during the replication of workloads to Azure. A migration fails when Migrate attempts to set up the PRE in the target Azure platform if you have not previously enabled PRE programmatic usage for the target Azure subscription and accepted the Terms of Use. The following error occurs:
User failed validation to purchase resources. Legal terms have not been accepted for this item on this subscription.
Fix: Log in to the target Azure subscription in the Azure Marketplace, then enable the target Azure subscription for programmatic use of PlateSpin Replication Environment and accept the Terms of Use. See Section 9.7, Enabling PlateSpin Replication Environment for Azure Subscriptions. After Azure is properly configured, retry the migration.
In Azure, the Dynamic assignment method is the default setting for the public IP address. The IP address can change every time the server is stopped and started. You should modify the setting to use the Static assignment method. Using a reserved IP address ensures that Azure allocates and reserves an IP address for the life of the resource.
NOTE:A change in IP address on the PlateSpin Server breaks the heartbeat communications with source workloads.
To apply a reserved IP address to an existing Migrate Server in Azure that has a dynamic IP address:
Specify Static as the assignment method for the public IP address of the Migrate Server resource:
Go to the appropriate Azure Portal and log in to your Azure account:
Open Resources, select the Migrate Server resource, then select Stop.
In the information for the Migrate Server, select the public IP address.
In the Public IP Address Configuration panel under Settings, select Configuration.
Specify Static as the assignment method for the Public IP address.
Click Save.
Azure allocates and reserves an IP address from a pool of its available IP addresses in the Azure location where you deploy the Migrate server.
Start the Migrate Server resource.
Heartbeat communications for existing migration jobs will be broken until you modify the server IP address stored in the OFX Controller configuration file on the source workload.
For each source workload that has already been configured for migration on the Migrate Server, use the Migrate Agent to set the new IP address:
migrateagent.cli.exe config /setting=psserver:<new_ipaddress_or_dns_name>
The psserver option stops the OFX Controller (ofxcontroller) service, modifies the OfxController.exe.config file with the new address, and restarts the service. Heartbeat communications now work with the server’s new IP address.
After a successful cutover of a workload to Azure Cloud, the Azure Portal Web UI does not display the target computer name.
To view the workload’s computer name and DNS name, use Remote Desktop to log in to the computer, then open the Control Panel and the System page.
Issue: After you migrate a Microsoft Exchange 2016 server to Microsoft Azure, the user’s outgoing messages get stuck in the Drafts folder of their Microsoft Outlook application.
Fix: After you migrate a Microsoft Exchange Server workload to Microsoft Azure, ensure that you modify the Exchange internal and external DNS settings to use Microsoft Hyper-V Network Adapter. See KB Article 7021909.