PlateSpin Migrate 2019.5 Release Notes

August 2019

PlateSpin Migrate 2019.5 includes new features and enhancements and resolves several previous known issues.

The documentation for this product is available in HTML and PDF formats on the PlateSpin Migrate 2019.5 Documentation website.

This product contains undocumented utilities that the Technical Support team might use to diagnose or correct problems.

1.0 Documentation Updates

The following changes have been made to this document since the release of PlateSpin Migrate 2019.5.

1.1 August 2019

1.2 July 2019

Location

Update

What’s New for AWS Quick Start

This section is new.

What’s New for Migrate Server in Azure Cloud

This section is new.

2.0 Support for Migration of Windows Workloads to Oracle Cloud Infrastructure

PlateSpin Migrate includes support for migration of Windows workloads to Oracle Cloud Infrastructure. For more information, see the following sections in the User Guide:

For information about deploying the PlateSpin Migrate server in the Oracle Cloud, see Installing PlateSpin Migrate Server in Oracle Cloud Infrastructure in the Installation and Upgrade Guide.

3.0 What’s New for AWS Quick Start

PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.5 server on the AWS Cloud. For more information about the Quick Start, see Micro Focus PlateSpin Migrate on AWS.

4.0 What’s New for Migrate Server in Azure Cloud

PlateSpin Migrate 2019.5 server image and replication environment are now available in Microsoft Azure Marketplace. In the Azure Marketplace, search for “PlateSpin”, then select the PlateSpin Migrate and PlateSpin Replication Environment images from Micro Focus.

5.0 What’s New

PlateSpin Migrate 2019.5 includes several new features and enhancements.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs.

5.1 PlateSpin Migration Factory

In a PlateSpin Migration Factory environment, PlateSpin Migrate 2019.5 supports PlateSpin Transformation Manager 2019.5 and PlateSpin Migrate Connector 2019.5 (a component of PTM). To install PTM in a PlateSpin Migration Factory deployment, see the PTM 2019.5 Appliance Guide.

Table 1 identifies the compatibility of the current and prior releases of PlateSpin Migrate and PlateSpin Transformation Manager.

Table 1 Compatibility Matrix for PlateSpin Migrate and PlateSpin Transformation Manager

  • PlateSpin Migrate
  • PlateSpin Transformation Manager
  • and PlateSpin Migrate Connector

Version (Release Date)

Version (Release Date)

2019.5 (May 2019)

2019.5 (May 2019)

2019.2 (Feb 2019)

2019.2 (Feb 2019)

5.2 AWS Migration Enhancements

  • Support for New Target Platforms

    PlateSpin Migrate adds support for migration of workloads to AWS China.

  • Support for Migration of Workloads to Amazon EC2 Dedicated Hosts in AWS Government Cloud

    PlateSpin Migrate supports migration of workloads to Amazon EC2 Dedicated Hosts provisioned in the AWS Government Cloud Region.

  • Support for New AWS Instance Types

    PlateSpin Migrate adds support for the following new AWS instance types for x86 and x86_64 processor architectures offered by Amazon Web Services since the Migrate 2019.2 release:

    • m5.metal, m5d.metal, r5.metal, r5d.metal, z1d.metal, i3.metal

      NOTE:PlateSpin Migrate supports these AWS EC2 Bare Metal instances for Windows Server 2012 R2, Windows Server 2016, and all supported Linux workloads for migration to AWS.

    • m5ad, r5ad

  • Ability to Install Amazon CloudWatch Agent on Target Workloads

    PlateSpin Migrate can install the CloudWatch agent on target workloads at Cutover and Test Cutover. On the Workload Configuration page, the Install CloudWatch Agent option is displayed for the workloads that supports CloudWatch agent. For information about the option and the workloads that support CloudWatch Agent, see AWS Agent in the User Guide.

  • Ability to Add New AWS Instances to the AWS Cloud Instance Size List

    For each release, PlateSpin Migrate adds support for new cloud instances and instance families that AWS has released up to a stipulated date prior to the PlateSpin Migrate release. After that date, any new AWS instances are not available by default in the Cloud Instance Size list. You can add definitions to the PlateSpin Server for new AWS Nitro Based instances and instance families to make the instances available in the AWS Cloud Instance Sizes list. See Recent AWS Nitro System Based Cloud Instance Sizes Are Not Available for Selection.

  • Support for AWS-to-AWS Migration

    PlateSpin Migrate adds support for AWS-to-AWS migration of source workloads between AWS regions in the AWS EC2 subscription. See Prerequisites for C2C Migration from AWS to AWS in the User Guide.

5.3 Azure Cloud Migration Enhancements

  • Support for New Azure Instance Types

    PlateSpin Migrate supports new Azure instance types offered by Microsoft Azure since the Migrate 2019.2 release.

  • Ability to Install Azure Agent on Target Linux Workloads

    PlateSpin Migrate can install the Azure Linux Agent on target Linux workloads at Cutover and Test Cutover.

    On the Workload Configuration page, the Install Azure Agent option is now available for both Windows and Linux workloads that meet installation prerequisites. See Prerequisites for Installing Azure VM Agent in the User Guide.

  • Support for Azure Managed Disks

    PlateSpin Migrate adds support for Azure Managed Disks. Using Managed Disks is enabled by default for migrations to Azure. See Prerequisites for Azure Storage in the User Guide.

  • Support for Azure Availability Sets

    PlateSpin Migrate adds support for Azure Availability Sets. You can specify an existing Availability Set to use for Cutover and Test Cutover. Using an Availability Set is optional. See Prerequisites for Using Azure Availability Sets in the User Guide.

  • Support for Azure Storage Accounts V2

    PlateSpin Migrate adds support for using Azure general-purpose storage V2 for Azure Storage Accounts. When you create a Storage Account in Azure, specify StorageV2 (general-purpose v2) as the Account Kind.

  • Support for Azure-to-Azure Migration

    PlateSpin Migrate adds support for Azure-to-Azure migration of source workloads between Azure regions in the same Azure subscription. See Prerequisites for C2C Migration from Azure to Azure in the User Guide.

  • Windows Page File on Azure Temporary Storage Drive

    PlateSpin Migrate configures the Windows page file for the target VM to use the Azure temporary storage drive and mounts it to a drive letter.

5.4 Hyper-V Migration Enhancements

5.5 Source Workload Support Enhancements

PlateSpin Migrate adds support for the following source workloads:

  • Windows Server 2008 (non-R2) workloads with 64-bit architectures for migration to Azure Cloud

  • Oracle Linux 5.11 GA pre-built blkwatch drivers for UEK and RHCK kernels on 64-bit and 32-bit architectures

For detailed information and caveats about supported source workloads, see Supported Configurations in the User Guide.

5.6 Migrate Agent Utility Enhancements

The Migrate Agent Utility provides a new cleanup command to remove PlateSpin drivers, the OFX controller software, and Migrate Agent related files (if any) from the source workload. See:

5.7 Web Interface Enhancements

  • Provides a new Disk Layout view of storage for Disks and Volumes sections in the Workload Configuration page for migration to all targets except targets for semi-automated (X2P) migration.

  • Provides warning messages with recommended free space required on the source workload when there is insufficient free space on the source workload volumes.

  • Ability to specify multiple IP addresses per NIC on Windows workloads for migrations to VMware, physical machines, and the cloud (AWS, Azure, vCloud). For migrations to VMware, you can also specify IP addresses for multiple default gateways.

  • Ability to add physical targets in the Create Targets dialog in support of semi-automated (X2P) migrations.

  • Ability to configure and execute semi-automated (X2P) full migration of workloads to physical targets. See Prerequisites for Migration to Physical Machines in the User Guide.

5.8 PlateSpin Configuration Settings

  • Ability to Remove or Leave Floppy Devices on Cutover VMs on VMware

    The LeaveVMwareDevicesAtCutover parameter enables Migrate to remove (clean up) or leave floppy devices on cutover VMs on VMware. By default, the devices are removed. An extra reboot is required at every Cutover or Test Cutover to remove the devices. VMware Tools must be installed and running on the cutover VM. For more information, see Cleaning Up Floppy Devices on the Cutover VM on VMware in the User Guide.

6.0 Deprecated Configurations and Functions

PlateSpin Migrate 2019.5 discontinues support for the following configurations and functions.

IMPORTANT:Before you upgrade from PlateSpin Migrate 2019.2 to PlateSpin Migrate 2019.5, ensure that you complete planned migrations that involve configurations and functions that will be deprecated in version 2019.5.

6.1 Deprecated Support for Source Workloads

  • PlateSpin Migrate 2019.5 discontinues support for migration of the following source workloads to any target:

    • Red Hat Enterprise Linux 4 (all versions and service packs), and distributions of CentOS and Oracle Linux based on RHEL 4

    • SUSE Linux Enterprise Server 9 (all versions and service packs)

    • SUSE Linux Enterprise Server 10 (all versions and service packs)

    • SUSE Linux Enterprise Server 12 SP2

  • PlateSpin Migrate 2019.5 discontinues support for Windows Server 2008 (non-R2, 64 bit and 32 bit) for migrations to all non-cloud platforms, including VMware, Hyper-V, and KVM.

  • PlateSpin Migrate 2019.5 discontinues support for Windows Server 2008 (non-R2, 64 bit and 32 bit) for migrations to the following cloud platforms: AWS, vCloud, and VMware Cloud on AWS.

6.2 Deprecated Support for Target Platforms

PlateSpin Migrate 2019.5 discontinues support for VMware DRS Clusters hosted on VMware Cloud (VMC) on Amazon Web Services.

6.3 Deprecated Function

PlateSpin Migrate 2019.5 discontinues support for migrations of workloads with multipath I/O (MPIO) enabled on the target workload. We recommend that you perform migration with a single path for each target disk, and then enable MPIO on the cutover workload.

6.4 Deprecated National Language Support

PlateSpin Migrate 2019.5 discontinues support for the Japanese national language.

7.0 Known Issues

Micro Focus strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Micro Focus Support and Services.

For information about known issues in previous releases, see Previous Releases.

7.1 Known Issue for Installation

Script for Install PlateSpin Migrate Prerequisites Does Not Launch

Issue: The Install PlateSpin Migrate Prerequisites script does not launch when you double-click the .bat file. Depending on your security settings, Windows security might block opening or running the downloaded files to help protect your computer.

Workaround: Ensure that you unblock the .bat file and .ps file, then try again to launch the script.

To unblock the .bat or .ps file:

  1. In Windows Explorer browser, right-click the file and select Properties.

  2. On the General tab, look for a Security field with an option to Unblock the file.

    This field and option are displayed only if the file is currently blocked by Windows.

  3. Click Unblock, then click OK.

7.2 Known Issues for Upgrade

Script for Install PlateSpin Migrate Prerequisites Does Not Launch

Issue: The Install PlateSpin Migrate Prerequisites script does not launch when you double-click the .bat file. Depending on your security settings, Windows security might block opening or running the downloaded files to help protect your computer.

Workaround: Ensure that you unblock the .bat file and .ps file, then try again to launch the script.

To unblock the .bat or .ps file:

  1. In Windows Explorer browser, right-click the file and select Properties.

  2. On the General tab, look for a Security field with an option to Unblock the file.

    This field and option are displayed only if the file is currently blocked by Windows.

  3. Click Unblock, then click OK.

After Upgrade, Migrations Fail for Deprecated Source Workloads

Issue: After you upgrade to PlateSpin Migrate 2019.5, existing migrations might fail if they have been configured for deprecated source workloads. See Deprecated Support for Source Workloads.

Workaround: Before you upgrade your Migrate Server to version 2019.5, ensure that you complete planned migrations for source workloads that are not supported for 2019.5.

Refresh of VMware ESXi Server Target Fails After Upgrade or Export and Import of Data

Issue: When you refresh a VMware ESXi Server target after you upgrade to PlateSpin Migrate 2019.5 or have exported and imported the migration data, the VMware ESXi Server target might fail to refresh in the very first refresh attempt because of a timeout issue or failure to discover this target server. Consequently, you cannot migrate a workload to this target unless it is successfully refreshed. (Bug 1137557)

Workaround: Refresh the VMware ESXi Server target a couple of times until it successfully refreshes.

7.3 Known Issues for Migration to AWS

Recent AWS Nitro System Based Cloud Instance Sizes Are Not Available for Selection

Issue: On the Workload Configuration page for migration to AWS, the Cloud Instance Size list does not include recently released Nitro System based cloud instances sizes.

Workaround: For each release, PlateSpin Migrate adds support for new cloud instances and instance families that AWS has released up to a stipulated date prior to the PlateSpin Migrate release. After that date, any new AWS instances are not available by default in the Cloud Instance Size list.

The AWS Cloud Instance Size list displays only instances that are defined in the AWS-Instances.ini file in the following package found on the PlateSpin Server:

<install-drive>:\Program Files\PlateSpin Migrate Server\Packages\B9059B80-55E4-4B9C-B85B-EFEFC85EAAE2\1.package\

You can add definitions to this file for new AWS Nitro Based instances and instance families to make the instances available in the AWS Cloud Instance Sizes list when you configure workloads for migration to AWS.

  1. Log in to the PlateSpin Migrate Server host machine as the Administrator user.

  2. Navigate to the PlateSpin Migrate installation directory, such as C:\Program Files\PlateSpin Migrate Server\.

  3. Open the .\Packages\B9059B80-55E4-4B9C-B85B-EFEFC85EAAE2\ folder and copy the 1.package file out of this folder to a temporary directory.

  4. Rename 1.package with the .zip file extension (1.zip), then extract the contents of the file to the temporary directory.

  5. Edit the file named AWS-Instances.ini to add an entry for the new instance or instance family that you want to support by using one of the following applicable formats:

    • If the instance or the instance family supports both NVMe EBS volumes and enhanced networking:

      [Instance name or Instance family name]
      Device.Storage = nvme
      Device.Network = ena
    • If the instance or the instance family supports only enhanced networking:

      [Instance name or Instance family name]
      Device.Network = ena

    NOTE:If the network and storage capabilities of an instance is not the same as that of the family it belongs to, you must have a separate entry for the instance and the support details listed within this entry takes precedence for the instance instead of its instance family entry.

  6. Repackage the modified file as 1.package.

Migration of a Linux Workload Having Combination of Nitro and Non-Nitro Instances Configured for the Target Workload and Target Workload Test Settings Fails

Issue: When you perform migration of a Linux workload that has been configured to use a Nitro instance during run cutover and a non-Nitro instance during test cutover, or the opposite mixed-type usage, the migration of the Linux workload to AWS target fails with a recoverable error. (Bug 1133056)

Workaround: When you configure migration of a Linux workload to AWS, you must ensure that the instance type you select for the Target Workload and Target Workload Test Settings are of the same type: Nitro or non-Nitro instance. You can select instances with different sizes if they are the same instance type.

7.4 Known Issues for Migration to Azure

Azure Managed Disks Settings Should Be Read Only at Prepare Workload

Issue: On the Workload Configuration page for migrations to Azure, the Use Managed Disks and Storage Type settings for Azure Managed Disks should be read only after you select Prepare Workload, similar to the behavior for Disk settings. If you deselect Use Managed Disks after Prepare, the Datastore and Path options for Disks are displayed but cannot be set because Disks settings are disabled at Prepare. (Bug 1137376)

Workaround: After you select Prepare Workload, do not modify the configuration settings for Use Managed Disks and Storage Type for Azure Managed Disks.

Non-Volume Storage Is Excluded for Migrations Using Azure Managed Disks

Issue: On the Workload Configuration page for migrations to Azure, if Use Managed Disks is enabled (the default), non-volume storage on the source workload is excluded in the default selection of disks to be migrated. The non-volume storage is not displayed in the Managed Disks list for the target workload. Replication, Test Cutover, and Cutover are successful with this configuration. (Bug 1134799)

Non-volume storage refers to disks that contain a partition, but do not have a mount point. If you select the non-volume disk to include it, replication fails with the following message:

Status:  Failed
Azure managed disk names may be up to 80 characters long. They must begin with an alphanumeric character then may include alphanumeric, underscore, period, or hyphen characters.

Workaround: None. PlateSpin Migrate does not support migration of non-volume storage disks to Azure when using Azure Managed Disks.

7.5 Known Issues for Migration to Physical Targets

X2P Migration Job Using PlateSpin Migrate Web Interface Fails If Target Datastore Has Insufficient Space

Issue: When you use the PlateSpin Migrate Web Interface to migrate a workload to a physical target that has almost the same storage space as the source workload, the Web Interface executes the migration job without validating for sufficient disk space on the physical target datastore. Consequently, the migration job fails with the following error: There is not enough space on target disk. (Bug 1136920)

Workaround: Before you use PlateSpin Migrate Web Interface to migrate a workload to a physical target, ensure that the datastore on the physical target has at least 1 GB more storage space than the workload you want to migrate.

Migration of a RHEL 7.x Workload to a Physical Target Fails With Recoverable Error

Issue: When you migrate a RHEL, OEL, or CentOS 7.x workload to a physical target, the migration job fails with a recoverable error in Shutdown source step even though the source workload has been successfully shutdown. (Bug 1137115)

Workaround: Ignore the error and abort the job because the workload has been successfully migrated.

Missing Driver Warning Message in Web Interface For X2P Migration Jobs Is Incomplete and Does Not Display the Names of the Missing Drivers

Issue: When you use the PlateSpin Migrate Web Interface to migrate workloads to physical targets, the warning message displayed in the interface for any missing drivers is not complete and does not list the names of the missing drivers. (Bug 1136409)

Workaround: For information about the missing drivers, see the diagnostic reports.

Diagnostic Reports in Web Interface For X2P Migration Job Displays Variables for Source and Target Hostnames

Issue: When you use the PlateSpin Migrate Web Interface to migrate workloads to physical targets and generate a diagnostic report for the job, the introduction paragraph and header in the report displays the source and target hostnames as variables instead of displaying the correct hostnames. (Bug 1136442)

Workaround: Ignore the hostnames in the introduction paragraph and header in the report. The source and target hostnames are correctly displaced in the instructions in the report.

7.6 Known Issues for Migrate API

Cutover Options to Shut Down Source or Target Are Ignored After Cutover for First Full Replication with Cutover

Issue: When you use Migrate API to execute a First Full Replication with Cutover operation from a Prepared state, the cutover options set to shut down the source or target are ignored. A full replication occurs before the cutover runs and cutover completes successfully; however, the specified shut down action is not performed. (Bug 1138321)

Workaround: After cutover completes, manually shut down the source workload or cutover workload, as appropriate.

Default Incremental Replication Is Ignored on Cutover If Cutover Options to Shut Down Source/Target Are Specified

Issue: When you use Migrate API to execute a Cutover operation from a Replicated state, the default behavior is to run an incremental replication before cutover. If the request body includes cutover options to shut down the source or target, the default setting to perform an incremental replication is ignored. Cutover completes successfully; however, no incremental replication occurs before the cutover runs. The specified shut down action is performed. (Bug 1138331)

Workaround: To successfully perform an incremental replication before cutover, do not specify cutover options for shutdown in the request body. After cutover completes, manually shut down the source workload or cutover workload, as appropriate.

Including the Cutover option to perform an incremental replication with a setting of true ("performIncremental": true) does not achieve the desired outcome of performing the incremental replication and the shut down actions. See Cutover Options to Shut Down Source or Target Are Ignored After Cutover If Perform Incremental Option Is Set to True.

Cutover Options to Shut Down Source or Target Are Ignored After Cutover If Perform Incremental Option Is Set to True

Issue: When you use Migrate API to execute a Cutover operation from a Replicated state, cutover options set to shut down the source or target are ignored if the request body also includes the Cutover option to perform an incremental replication with a setting of true ("performIncremental": true). An incremental replication occurs before the cutover runs and cutover completes successfully; however, the specified shut down action is not performed. (Bug 1138348)

Workaround: After cutover completes, manually shut down the source workload or cutover workload, as appropriate.

First Full Replication Fails If Resource Group Names are Different for Transformations and Storage Disks

Issue: When you use Migrate API to migrate a workload to Azure with Azure Managed Disks enabled (the default), the first full replication fails if the Storage Disks resource group is set to a custom name that does not match the Transformation resource group name. (Bug 1138897)

Workaround: In the current Migrate API, the Transformation resource group setting and Storage Disk resource group setting must have the same value. You can keep the default resource group name for both settings, or use the Migrate API to modify both settings to use the same custom name.

7.7 General Known Issues

Cannot Adjust the Target Volume Size for File-Based Migrations in the Web Interface

Issue: In the Migrate Web Interface, you could previously modify the Volumes > Free Space parameter to adjust the target volume size for Windows file-based migrations. However, the new Disk Layout view for Volumes currently does not allow you to adjust the volume size. You cannot adjust the target volume size for file-based migrations in the Web Interface when the Disk Layout view is enabled.

Workaround: Disable the Disk Layout view and use the legacy storage view to configure target disks and volumes. You can modify the Free Space value for the target volume to adjust its volume size.

To disable the Disk Layout view and use the legacy storage view instead:

  1. Go to the PlateSpin Configuration page:

    https://Your_PlateSpin_Server/PlateSpinConfiguration

  2. Locate the EnableDiskLayoutOptions parameter, then click Edit.

  3. Set the value to False.

  4. Save your settings and exit the page.

8.0 Resolved Issues

PlateSpin Migrate 2019.5 resolves the following previously known issues.

8.1 Migration of a Workload to a KVM Virtual Machine Having One or More Virtio Disk Fails When the Target VM Has Multiple NICs

Issue: When you migrate a Windows workload to a KVM virtual machine having one or more Virtio disks, the migration of the workload fails with recoverable error at configuring operating system step if the target VM has more than one NIC. (Bug 1085105)

Fix: You can now use Virtio disks in the target VM that has multiple NICs and is hosted on a KVM machine.

8.2 RHEL 6.10 Source Workloads Crash During Incremental Replication

Issue: During incremental replications, a system crash occurs for source Red Hat Enterprise Linux (RHEL) 6.10 workloads running Linux kernel 2.6.32-754.6.3.el6.x86_64. (Bug 1119323)

Fix: The system crash is a Red Hat known issue for RHEL 6.10 running Linux kernel version 2.6.32-754.6.3.el6.x86_64. See RHEL 6.10 Source Workloads Crash During Incremental Replication in the User Guide.

8.3 Subsequent Replication of a Workload to a VMware Target Might Fail If a Previous Replication Attempt of the Workload to the Same Target Failed

Issue: If the replication of a workload to a VMware target fails after a cutover VM is created on the VMware target, then any subsequent replication of the workload to the same VMware target might fail again if the target datastore does not have sufficient space. This is because even though PlateSpin Migrate removes the cutover VM from the target during the subsequent replication, the VMware target is not refreshed. Consequently, the space that is released after the deletion of the cutover VM does not reflect in the target VMware datastore and replication might fail due to insufficient space. (Bug 1113189)

Fix: PlateSpin Migrate now refreshes the target VM during replication. Consequently, the space released from the deletion of the target cutover VM now correctly reflects in the target datastore.

8.4 Windows Power Service Removed from the Target Workload Post Migration of the Workload

Issue: After the migration of a Windows workload, the Windows Power service is removed from the target workload. This is because the registry entry for the Windows Power service is removed during the deletion of the registry entry for a PlateSpin Migrate configuration service named PowerP2Vconfiguration, which has a matching initial name as the Windows Power service. (Bug 1121171)

Fix: PlateSpin Migrate now renames the PlateSpin Migrate PowerP2Vconfiguration service such that deleting the renamed service no longer deletes the Windows Power service from the target workload.

8.5 Unable to Configure Static IP Address and DNS Servers on the Cutover vCloud Target VM for a Linux 7.x Workload

Issue: When you perform cutover of a supported Linux 7.x BIOS workload to vCloud, the cutover is successful and the static IP address that you configured in the migration job correctly displays in the vCloud Director. However, the configured static IP address and DNS servers are not set on the cutover target VM and the VM uses a DHCP address instead. This issue is not seen when you perform a test cutover of the Linux workload. (Bug 1124879)

Fix: PlateSpin Migrate configures the static IP address and DNS servers on the cutover target VM.

8.6 Copy Target Workload Settings Might Not Copy the Host Setting For Dedicated Hosts in AWS Government Cloud

Issue: Consider that you want to migrate a workload to a dedicated host on AWS Government Cloud and you configure the target workload settings to launch the target instance on the dedicated host with the Host option set to Use auto-placement. Subsequently, if you use the Copy Target Workload Settings option to automatically copy the same settings to Target Workload Test Settings section, the value of the Host option in the Target Workload Test Settings section might not set to Use auto-placement. (Bug 1127351)

Fix: PlateSpin Migrate updates the Copy Target Workload Settings option to ensure that all the settings in the Target Workload Settings section are automatically copied to the Target Workload Test Settings section.

8.7 Migration Job Fails in PrepOsToBoot Step While Scanning the Registry File That Contains Registry Entry With Hexadecimal Value

Issue: During the PrepOsToBoot step of a migration job, the job fails with an error while scanning and importing changes from a registry file that contains registry entries with a hexadecimal value. (Bug 1123086)

Fix: PlateSpin Migrate now allows the registry file to contain entries with hexadecimal value.

9.0 Installing or Updating PlateSpin Migrate

PlateSpin Migrate 2019.5 provides the Install PlateSpin Migrate Prerequisites PowerShell script to check for and install prerequisite software and apply the appropriate configuration: ASP.NET, IIS, and .NET Framework. See Installing Prerequisite Software in the Installation and Upgrade Guide.

To install PlateSpin Migrate 2019.5, see Installing PlateSpin Migrate in the Installation and Upgrade Guide.

To apply PlateSpin Migrate 2019.5 to your PlateSpin Server, you must have an existing installation of PlateSpin Migrate 2019.2 on a supported Windows platform. See Upgrading Migrate in the Installation and Upgrade Guide.

NOTE:To upgrade from an existing installation of PlateSpin Migrate 2019.2 Server to a supported new host platform, see Upgrading Migrate to a New Host Platform in the Installation and Upgrade Guide.

10.0 Licensing Information

For information about activating a new license, see PlateSpin Migrate Product Licensing in the User Guide.

11.0 Previous Releases

For documentation that accompanied earlier releases, visit the PlateSpin Documentation website and scroll to the release that you are looking for.

12.0 Contacting Micro Focus

For specific product issues, contact Micro Focus Support at https://support.microfocus.com/contact/.

Additional technical information or advice is available from several sources:

13.0 Legal Notice

For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.microfocus.com/about/legal/.

© Copyright 2007 – 2019 Micro Focus or one of its affiliates.

The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.