PlateSpin Migrate 2018.11 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 2018.11 Documentation website.
This product contains undocumented utilities that the Technical Support team might use to diagnose or correct problems.
The following changes have been made to this document since the release of PlateSpin Migrate 2018.11 in November 2018.
|
Location |
Change |
|---|---|
|
PlateSpin Migrate discontinues support for migrations of workloads with multipath I/O (MPIO) enabled. We recommend that you perform migration with a single path, and then enable MPIO on the cutover workload. |
|
Location |
Change |
|---|---|
|
NOTE:Effective May 16, 2019, PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.2 server on the AWS Cloud. Refer to the PlateSpin Migrate 2019.2 Documentation website. |
|
Location |
Change |
|---|---|
|
This section is new. |
|
|
NOTE:Effective March 25, 2019, the Migrate Server in Azure Cloud is PlateSpin Migrate 2019.2. Refer to the PlateSpin Migrate 2019.2 Documentation website. |
|
|
|
This section is new. |
|
Location |
Change |
|---|---|
|
PlateSpin Migrate 2018.11 discontinues support for the following:
|
|
Location |
Change |
|---|---|
|
This section is new. |
|
|
This section is new. |
|
|
This section is new. |
PlateSpin Migrate adds support for AWS Quick Start to help you quickly and easily deploy PlateSpin Migrate 2018.11 Server on the AWS Cloud. For more information about the Quick Start, see Micro Focus PlateSpin Migrate on AWS.
NOTE:Effective May 16, 2019, PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.2 server on the AWS Cloud. Refer to the PlateSpin Migrate 2019.2 Documentation website.
PlateSpin Migrate 2018.11 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.
NOTE:Effective March 25, 2019, the Migrate Server in Azure Cloud is PlateSpin Migrate 2019.2. Refer to the PlateSpin Migrate 2019.2 Documentation website.
PlateSpin Migrate 2018.11 Patch Update 1 is available for download on Micro Focus Patch Finder. This patch resolves the issue described in After VMware Maintenance or Update, VMware Target No Longer Appears in the Web Interface and Its Associated Workloads Go into an Unsupported State.
PlateSpin Migrate 2018.11 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.
Support for C5/M5 Instance Types
PlateSpin Migrate adds support for AWS C5, C5d, M5, and M5d instance types as target VMs for the following workloads:
Windows workload: Windows Server 2008 R2 and later
Linux workloads: RHEL 7.4, CentOS 7.0, OEL 7.0, and later versions of these distributions
Support for Dedicated Instances and Dedicated Hosts
Migration of workloads to Amazon EC2 Dedicated Hosts and Amazon EC2 Dedicated Instances are now supported in addition to the existing support for migration of workloads to Amazon EC2 Shared Instances.
Support for Multiple Azure Environments
PlateSpin Migrate now supports multiple Microsoft Azure environments as target platforms on the same server. You select the target Azure environment and a location within that environment for each target Azure platform:
Azure China Cloud
Azure Germany Cloud
Azure Global Cloud (default)
Azure Government Cloud
Expanded Support for Sovereign Cloud
Sovereign cloud support has been expanded:
Azure Germany Cloud
Azure Government Cloud
Enhanced Azure Cloud Instance Size Settings
You can now specify the Cloud Instance Size in Target Workload Settings and Target Workload Test Settings. The settings are independent and can be set to different instance sizes.
SLES 12 PRE for vCloud
PlateSpin Migrate provides a SLES 12 PlateSpin Replication Environment that is used for migrating UEFI workloads to target VMware vCloud platforms. This PRE also enables migration of UEFI workloads with XFS v5 file systems. For information about creating the virtual appliance for the SLES 12 PRE, see Understanding PlateSpin Replication Environment Used for Migration of Workloads to vCloud
in the User Guide.
Support for Migration of UEFI Workloads to Hyper-V
PlateSpin Migrate adds support for UEFI-to-UEFI and BIOS-to-UEFI conversions of workloads to target Hyper-V Server 2016 and Windows Server 2016 Hyper-V platforms.
Support for Migration of UEFI Workloads to vCloud
PlateSpin Migrate add support for migrations of source Windows and Linux UEFI workloads to target VMware vCloud platforms. This capability includes source Linux UEFI workloads with an XFS v5 file system.
Supported Linux Workloads
PlateSpin Migrate adds support for the following source Linux workloads. For information about precompiled blkwatch drivers, see List of Distributions
in the User Guide.
|
Platform |
Versions |
Remarks |
|---|---|---|
|
Red Hat Enterprise Linux (RHEL) |
7.5 |
The XFS version 5 (v5) file system is supported on RHEL 7.3 and later, and on distributions based on those versions. However, this support does not apply for BIOS source workloads to vCloud target containers. Migration of UEFI workloads with XFS v5 file systems to vCloud requires the vCloud PRE (PlateSpin Replication Environment) based on SLES 12 SP3. Migration of BIOS workloads with XFS v5 file systems to vCloud is not supported. |
|
Oracle Linux |
Distributions based on RHEL. |
Use precompiled blkwatch drivers for the Oracle Unbreakable Enterprise Kernel (UEK) and standard kernel. |
|
CentOS |
Distributions based on RHEL. |
Use RHEL precompiled blkwatch drivers. |
For detailed information and caveats about supported source workloads, see Supported Configurations
in the User Guide.
Support of BBT for Migration of Workloads with Volumes on iSCSI SANs
PlateSpin Migrate adds support for driver-based block-based data transfer for workloads with volumes on iSCSI SANs, including Windows Clusters with shared storage on iSCSI SANs.
Support for Windows Cluster Migration to VMware VMs with RDM Disks
PlateSpin Migrate supports the semi-automated (X2P) migration of a Microsoft Windows Server Failover Cluster (WSFC) to VMware virtual machines (VMs) with shared RDM (raw device mapping) disks. See Advanced Windows Cluster Migration to VMware VMs with RDM Disks
in the User Guide.
Support for Target VMware 6.7 Platforms
VMware vCenter 6.7
VMware ESXi 6.7
vSAN 6.7
Support for NFS Volumes on Target VMware Platforms
NFS v4.1: For all supported versions of VMware vCenter 6.x and ESXi 6.x platforms
NFS v3: For all supported versions of VMware vCenter and ESXi platforms
For detailed information and caveats about supported target virtualization platforms, see Supported Target Virtualization Platforms
in the User Guide.
Secure Storage for Credentials
Credential passwords for workloads and target platforms are stored encrypted in the PlateSpin database. Each PlateSpin Migrate server has a unique, randomly generated encryption key. See Security of Credentials
in the User Guide.
Secure Export for Credentials
The Import/Export utility (ImportExportAll.bat) enables you to optionally provide an encryption password to encrypt Credential passwords for workloads and target platforms in exported data and decrypt them on import. See Exporting Workload Migration Data
and Importing Workload Migration Data
in the Installation and Upgrade Guide.
PlateSpin Migrate enhances the Web Interface with the following:
Ability to View License Designations
The Licensing page includes a new License Designations tab that lets you view the workload license information.
Ability to Copy Target Workload Settings to Target Workload Test Settings
The Migration Configuration page provides a Copy Target Workload Settings option that allows you to copy the workload settings from Target Workload Settings section to Target Workload Test Settings section. See the following information in the User Guide:
Copy Target Workload Settings in Configuring Migration of a Workload to Amazon Web Services
Copy Target Workload Settings in Configuring Migration of a Workload to Microsoft Azure
Copy Target Workload Settings in Configuring Migration of a Workload to VMware vCloud Director
Copy Target Workload Settings in Automated Migration to VMware Using Migrate Web Interface
Ability to Choose Volumes for Incremental Replication
Migrate Client enables you to optionally choose which volumes to sync for incremental replications when you configure a Server Sync job.
PlateSpin Migrate 2018.11 no longer supports the following server-level PlateSpin Configuration settings:
AzureAuthenticationAddress
AzureCloudAddress
AzureStorageEndpointSuffix
Instead, you configure each Azure target platform with the appropriate target Azure environment. See Support for Multiple Azure Environments
.
PlateSpin Migrate 2018.11 discontinues support for the following functions:
Multipath I/O (MPIO) support
For migrations of workloads with multipath I/O (MPIO) enabled, we recommend that you perform migration with a single path, and then enable MPIO on the cutover workload.
VLAN tagging support for target workloads for X2P migrations
For X2P migrations, PlateSpin Migrate supports only untagged network packets on any network interface that is used during the migration process. However, VLAN IDs continue to be supported for migrations to Microsoft Hyper-V.
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
.
How to Export and Import PlateSpin Database Data
Issue:
During an upgrade from PlateSpin Migrate 12.3 to PlateSpin Migrate 2018.11, the Export the Data documentation link to KB Article 7921083 How to Export and Import PlateSpin Database Data
goes to the location, but receives an error message: Document is not available. (Bug 1116641)
Workaround:
The Knowledge Base for PlateSpin Migrate has been moved to our Micro Focus website and some articles have been renumbered. For information about exporting the data before an upgrade, see How to Export and Import PlateSpin Database Data
(KB Article 7013175) at https://support.microfocus.com/kb/doc.php?id=7023175.
Issue: After you upgrade the Migrate server from version 12.3 or 12.3 Patch Update 1 to version 2018.11, If you choose to edit the configuration of a source workload that was configured for migration to vCloud prior to upgrade, the PlateSpin Migrate Web Interface incorrectly displays a warning message that/bootvolume is required for successful migration. (Bugs 1117060, 1117069)
Workaround: Ignore the warning message. You must not select the /boot/efi partition when you edit the configuration of source workload to vCloud target after you have upgraded the Migrate server.
Issue: PlateSpin Migrate 2018.11 provides a new block-based transfer (BBT) driver. After the upgrade, Migrate should display a notification in the Tasks column on the Workloads page of the PlateSpin Migrate Web Interface to upgrade the BBT driver for each workload that already has the previous BBT driver installed. The Workloads page does not display the upgrade task notification. However, an Upgrade Component button is displayed on the Command Details page for the impacted workloads. (Bug 1119196)
Workaround: To initiate the display of the upgrade task notification as needed for any workload being migrated to a target platform, go to the Targets page of the PlateSpin Migrate Web Interface and click Refresh next to the target. The task message is available for impacted workloads:
New version of the block-based component is available for this workload.
When you are ready to upgrade the BBT driver, click Upgrade Component in the task. You can also view the Commands Details page of any workload to check if it displays the Upgrade Component button, then click it to initiate the BBT driver upgrade for the workload.
IMPORTANT:Before you upgrade the BBT driver for workloads that were in a Prepared state before the Migrate upgrade, ensure that you run a full replication on the workload. See After Upgrade: Previously Prepared Workloads Fail on Replication after BBT Driver Upgrade
.
Issue: After you upgrade to PlateSpin Migrate 2018.11, you are notified to upgrade the BBT driver on workloads where the previous BBT driver was already installed. However, for workloads that were in a Prepared state before the Migrate upgrade, after you upgrade the BBT driver, the workload state is incorrectly reported as Replicated instead of Prepared, even when no first full replication has been run. Any subsequent attempt to replicate this workload fails. This issue does not affect workloads that were in a Replicated state before the Migrate upgrade. (Bug 1119342)
Workaround: Before you upgrade the BBT driver for workloads that were in a Prepared state before the Migrate upgrade, ensure that you run a full replication on the workload.
If you have already upgraded the BBT drivers for the previously Prepared workloads and any subsequent attempted replications have failed, you must remove the workload with the option Preserve Source enabled, and then reconfigure and prepare the workload.
Issue: For Azure instances Standard_E20_v3 and Standard_E20s_v3, Migrate displays 1 as the value for the maximum number of NICs, but the value should be 8. (Bug 1117699)
Workaround: None. For information about the Azure Ev3-series and Esv3-series instance sizes, refer to Memory Optimized Virtual Machine Sizes in the Microsoft Azure documentation.
Issue: When you migrate a workload to Microsoft Azure with a configuration set to shut down the target workload after cutover, PlateSpin Migrate shuts down the guest operating system after a successful cutover. The migrated workload is in a Stopped (Allocated) status in Azure. Although the workload guest operating system is powered off, the Azure VM continues to incur Azure charges for the allocated VM resources. (Bug 977144)
Workaround: To stop charges for VM resources, you can use the Azure Portal to shut down the VM. The VM will then be in a Stopped (Deallocated) state, which incurs no charges from Azure.
Go to the appropriate Azure Portal and log in to your Azure account:
Navigate to the Virtual Machine and select Stop.
For more information on shutting down the Azure VM, see Properly Shutdown Azure VM to Save Money.
Issue: When you migrate C5 or M5 instance type source workloads from AWS to Citrix XenServer, the conversion is successful. However, the AWS drivers are not removed from the target workload after the conversion. (Bug 1110919)
Workaround: None. There is no impact to the functionality.
Issue: The migration of a CentOS 7 or 7.1 workload to AWS target stalls with a recoverable error. This is because the NVMe driver causes a kernel panic due to the reboot of the workload. (Bugs 1112284, 1113304)
Workaround: To successfully complete the migration of the CentOS workload to AWS, manually stop the target workload instance and then start it again.
Issue: When you configure migrations to AWS target, If you select an instance type that AWS does not support launching in a placement group, then PlateSpin Migrate displays a error message when you select a placement group. However, this error message might not list all the unsupported instance types. (Bug 1116718)
Workaround: None. Placement Group configuration in Migrate is limited to cloud instance types supported by Amazon EC2. Refer to AWS EC2 Documentation for the latest information about placement groups and AWS rules and limitations for using them:
Placement Groups
in the AWS EC2: User Guide for Windows Instances.
Placement Groups
in the AWS EC2: User Guide for Linux Instances.
Issue: When you configure a workload for migration to AWS, if validation messages are being displayed in the Target Workload Settings panel when you click Copy Target Workload Settings, the same validator messages are triggered in the Target Workload Test Settings panel, but they are displayed in duplicate. (Bug 1118536)
Workaround: None. There is no impact to functionality.
Issue: When you configure migration of a workload to AWS, PlateSpin Migrate might recommend an EC2 Instance (such as A1) that is powered by ARM-Based AWS Graviton Processors if it matches the source workload's settings for cores, memory, volumes, and NICs. However, PlateSpin Migrate does not support the instance types that are powered by ARM-Based AWS Graviton Processor. (Bug 1122166)
Workaround: Use a supported instance type based on x86 and x64 processor architectures.
Issue:
When you use the X2P workflow to migrate a workload to VMware, you are required to set up the VMware Tools for the target workload before you perform the conversion so that the configuration service can install the tools on the target VM when the target VM contacts the PlateSpin Server. See Setting Up VMware Tools for the Target Workload
in the User Guide.
However, the VMware tools might not get automatically copied if the firmware on the source and target workloads are not the same. (Bug 1117874)
Workaround: After conversion, manually uninstall the older version of VMware tools on the target workload and install the newer version.
Issue: If the password for a cloud account includes special characters or is blank, replications to that account fail with the following error:
Failed to Authenticate user root. Permission denied (password).
Migrate is unable to take control of the replication environment because authentication fails. (Bugs 1128247, 1127892)
Workaround: This issue is resolved in PlateSpin Migrate 2019.2. Contact Technical Support to get a solution for PlateSpin Migrate 2018.11.
Issue: After you install the Migrate block-based transfer (BBT) driver on the source Windows workload, block-based operations stall. The source machine fails to start and displays the following boot error because it cannot verify the digital certificate for the BBT driver file psmon.sys. (Bug 1117642)
File: \Windows\system32\DRIVERS\psmon.sys status :0xc0000428 Info: Windows cannot verify the digital signature for this file.
Workaround: The latest Windows updates are required for Windows to verify the Microsoft SHA256 certificate for PlateSpin Migrate block-based transfer drivers. Before you install block-based transfer drivers on source Windows workloads, ensure that you have applied the latest Windows updates on the workload.
The following is a list of issues that were resolved for this release:
Issue: If PlateSpin Migrate 2018.11 refreshes a VMware target’s information during a VMware maintenance window or update, the VMware target can disappear from the Migrate Web Interface and its associated workloads go into an unsupported state. (Bug 1117364)
Fix: PlateSpin Migrate 2018.11 Patch Update 1 provides a patch that prevents this issue from occurring.
Go to Micro Focus Patch Finder, then download PlateSpin Migrate 2018.11 Patch Update 1.
Apply the patch to your PlateSpin Migrate 2018.11 Server.
After you apply the patch, PlateSpin Migrate ensures that the VMware target does not get removed if a target refresh occurs during VMware maintenance or update. After the maintenance or update completes, you must refresh the target in Migrate before you resume migrations. See Best Practices for Maintaining or Updating VMware Environments That Are Configured as Migration Targets
in the User Guide.
If the error has already occurred and the VMware target was removed, you must do one of the following:
Restore your migration database by importing the database backup file that you exported before you began the VMware maintenance or update.
-OR-
Re-add the VMware target, then re-create all contracts associated with that target.
Issue: If you choose to discover a source workload by its host name when an already discovered under control target has a matching host name, the discovery fails. (Bug 1061695)
Issue: If you chose to migrate a RHEL 5.x source workload that is on a VMware host to an AWS target, the migration failed if VMware tools were not installed on the source workload. (Bugs 1069538,1069540)
Fix: This issue is fixed with support of AWS migration in Web Interface. You are no longer required to install the VMware tools on the source workload before migrating the workload.
Issue: When you use the Migrate Client to perform Server Sync operation to synchronize the source changes to the target workload on a ESX server, the target VM name includes the (under PlateSpin control) string even after the Server Sync operation is successfully completed. (Bug 1102407)
Fix: The target VM name correctly displays after the Server Sync operation completes.
Issue: When Shut Down is set as the post-migration end state for a Windows Server 2016 Cluster, the PlateSpin Migrate Web Interface shuts down only the active node of the cluster; the passive nodes are not shut down. Migrate Client properly shuts down all source nodes. (Bug 1087669)
Fix:
See Source Passive Node Does Not Shut Down at Cutover for Windows Server 2016 Cluster
in the User Guide.
Issue: If you choose to migrate a Windows Small Business Server 2011 workload to Azure, the cutover completes but the target VM in Azure is launched in Safe Mode. (Bug 978131)
Fix:
See Azure Target VM Launched in Safe Mode After Successful Cutover of a Workload
in the User Guide.
Issue: When you chose to migrate a UEFI or BIOS Windows workload to Windows Server 2016 Hyper-V or Microsoft Hyper-V Server 2016 target, the Virtual Machine generation type in the Hyper-V Virtual Machine Configuration dialog is set by default to Generation 1 and you cannot edit the generation type. (Bug 1087212)
Fix: Migrate Client now supports UEFI-to-UEFI or BIOS-to-UEFI conversions for migrations to Windows Server Hyper-V 2016 or Microsoft Hyper-V Server 2016.
Issue: For Windows source workloads with dynamic disk types of Simple, Spanned, Striped, Mirrored, and RAID5, the target workload configuration assigns non-sequential numbers in disk names and disk indexes. The non-sequential numbering is an artifact of the types of dynamic disks on the source workload. All necessary disks are present for the target workload. This issue occurs for target workloads in the Web Interface. (Bug 973266)
Fix: See Disk Numbers and DiskIndex Numbers Are Not Sequential for Discovered Dynamic Disk Workloads
in the User Guide.
Issue: When you migrate a workload to a VMware 5.5 target, the migration completes successfully. However, the following message is displayed in the vSphere Web Client: (Bug 1090278)
vSphere Web Client Configuration Issue: Virtual Machine Disks Consolidation is needed.
vSphere Web Client Triggered Alarm: Virtual machine Consolidation Needed status
Fix:
See vSphere Alarm: Virtual Machine Consolidation Needed
in the User Guide.
Issue: When you migrate a source workload with disks that have more than 15 file system volumes, the migration fails at the Creating and Partitioning Volumes step (Bug 1020176)
Fix:
See Planning For Migrating Workloads to Amazon Web Services
in the User Guide.
Issue: After successful cutover of a workload to Azure, the Virtual Machine Settings page of the Azure Portal does not display the size of the Azure VM if the VM belongs to DSX_v2 series. Although the VM size is not shown on the settings page, the underlying VM configuration contains the VM size.(Bug 977497)
Fix: Azure Portal properly displays size information for VMs in theDSX_v2 series.
Issue: When you migrate a Windows Server 2008 SP2 or Windows Server 2008 R2 source workload to Microsoft Windows Server 2016 Hyper-V, the following job warning message displays if Migrate cannot use the C:\Windows\system32\vmguest.iso file to install the Hyper-V Integration Services driver on the Hyper-V target VM during the migration:
"InstallHyperVIntegrationServices" (Failed: Non-Critical Error)
The migration completes successfully, but Migrate does not automatically install the Hyper-V Integration Services driver on the target VM. (Bug 1084987)
Fix:
Before you begin migrations to Hyper-V, ensure that you have properly prepared your migration environment. See Planning for Migration to Microsoft Hyper-V
in the User Guide.
Issue: When you prepare the replication environment in Azure, a 403 Forbidden error displays if the date and time on the Migrate server has drifted out of sync with time in the Azure environment. Typically, the error occurs for time drifts greater than 15 minutes. (Bug 1077308)
Fix: Ensure that the date and time settings on the Migrate server are within the time-sync requirements of the target Azure environment, then retry the replication.
Issue: For RHEL 7.3 and distributions based on RHEL 7.3, incremental replications fail for UEFI to BIOS migrations during Preparing Target Machine.to Boot Operating System because it cannot determine the location of the grub.cfg configuration file. This error occurs in Azure and vCloud. (Bug 1066071)
Fix: Migrate can properly determine the location of the grub.cfg configuration file.
Issue: The test cutover or cutover of a source Linux workload (running RHEL, CentOS, or Oracle Linux RHCK Linux distributions) from AWS to VMware vCloud hangs with the following message in the Web Interface:
Configuration services is taking a long time to start
In VMware vCloud Director (vApps\vAppname\virtual Machine\vmName), a dialog box requiring user intervention displays stating that the guest OS has locked the CDROM on the target VM and prompts you to override the CD-ROM lock. In the Web Interface, the cutover hang continues until you manually override the CDROM lockout in the VMware vCloud Director for the target environment. (Bug 1087949)
Fix: This issue is fixed and you are no longer prompted for overriding the lock.
Issue: After a successful Abort action during cutover of a source Linux VM on VMware to a target Linux VM in Azure, a subsequent cutover attempt fails with an error:
Under-control conversion of a Linux source with LVM snapshots is not supported: See /dev/<source-hostname>/root-PS-snapshot
This error occurs because the root-PS-snapshot symbolic link was not removed during the clean up process for the Abort action. (Bug 1016619)
Fix:
Clean up the link manually. See Cutover Fails If root-PS-snapshot on the Source Linux Workload Is Not Cleaned Up Properly
in the User Guide.
Issue: Commands executed using the PlateSpin Migrate Client Command Line Interface fails with the error: missing parameter value/address.
This error occurs because the configuration file containing the Migrate server details cannot be read. (Bug 1086232)
Fix: The configuration file containing the preconfigured Migrate server values is now renamed as PlateSpin.Migrate.Console.exe.config. CLI can now read this configuration file and use the preconfigured Migrate server values for successfully executing the commands.
PlateSpin Migrate 2018.11 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 2018.11, see Installing PlateSpin Migrate
in the Installation and Upgrade Guide.
To apply PlateSpin Migrate 2018.11 to your PlateSpin Server, you must have an existing installation of PlateSpin Migrate 12.3 on a supported Windows platform, with or without interim patches and hotfixes applied. See Upgrading Migrate
in the Installation and Upgrade Guide.
NOTE:To upgrade from an existing installation of PlateSpin Migrate 12.3 Server to a supported new host platform, see Upgrading Migrate to a New Host Platform
in the Installation and Upgrade Guide.
For information about activating a new license, see PlateSpin Migrate Product Licensing
in the User Guide.
For documentation that accompanied earlier releases, visit the PlateSpin Documentation website and scroll to the release that you are looking for.
We want to hear your comments and suggestions about this book and the other documentation included with this product. You can use the comment on this topic link at the bottom of any HTML page of the English documentation.
For specific product issues, contact Micro Focus Support at https://support.microfocus.com/contact/.
Additional technical information or advice is available from several sources:
Product information and resources:
Micro Focus Customer Center: https://www.microfocus.com/customercenter/
Product knowledge base and videos: https://www.microfocus.com/support-and-services/
Micro Focus Communities: https://www.microfocus.com/communities/
PlateSpin Idea Exchange: https://community.softwaregrp.com/t5/PlateSpin-Idea-Exchange/idb-p/PlateSpin_Ideas/
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 – 2018 Micro Focus or one of its affiliates.