1.1 Preparing to Install PlateSpin Migrate

For trouble-free installation and operation of PlateSpin Migrate, you should review the system requirements and plan your installation.

1.1.1 System Requirements for PlateSpin Server

PlateSpin Server hosts must meet the system requirements in Table 1-1. See also General Guidelines for Server Installation.

Table 1-1 Host Requirements for PlateSpin Server

Requirement

Details

Dedicated host

Physical or virtual server

Operating System

Any of the following Windows Server versions:

  • Windows Server 2016

  • Windows Server 2012 R2

NOTE:You must activate the Microsoft license for your Windows operating system prior to installing PlateSpin Migrate.

Processor

Recommended (physical): multi-core, 2 GHz or higher

Recommended (VM): 2 or more Virtual CPUs

Memory

Recommended: 8 GB RAM

Disk Space

Minimum 50 GB

Database Server

A dedicated Microsoft SQL Server database instance, running on one of the following:

  • Microsoft SQL Server 2017 Express Edition

    A copy of this database software is included in your PlateSpin Migrate software distribution.

    NOTE:For upgrades of PlateSpin Migrate Server, your existing installation of Microsoft SQL Server 2014 Express is supported. The SQL Server Express software is not updated as part of the upgrade.

  • Microsoft SQL Server 2016

  • Microsoft SQL Server 2014

  • Microsoft SQL Server 2008 R2

For remote database instances, the following additional requirements must be met:

While multiple PlateSpin Migrate Servers can use the same remote database server, each Migrate Server requires a separate dedicated database instance.

NOTE:Prior to installing the product, ensure that your existing SQL Server database server and named database instance meet the Database guidelines.

Prerequisite Software

NOTE:You can install prerequisite software manually or use the PowerShell script provided on the PlateSpin Migrate Download site. See Installing Prerequisite Software.

  • To perform a batch-file installation of PlateSpin Migrate, you must install Visual C++ 2013 on the host server. See Installing Visual C++ 2013 for Batch-File Installation of PlateSpin Migrate.

  • To use a remote database instance with PlateSpin Migrate, you must install Microsoft SQL Server Native Client on the host server. You can download the software from Microsoft website.

    See Installing SQL Server Native Client on the Host Server.

    NOTE: During the Migrate server installation, the Validate Credentials action fails on the Database Administrative Credentials dialog with error if Microsoft SQL Server 2012 Native Client is not installed. See Microsoft SQL Server 2012 Native Client Is required.

  • All Windows hosts (recommended)

    • Ensure that a licensed version of the OS is installed and the license has been activated.

    • Apply the latest applicable OS updates (service packs, cumulative security updates, drivers, and so on).

  • For Windows Server 2016 systems:

    • Disable User Account Control (UAC).

    • Install Microsoft .NET Framework 4.7.1. You can download.NET software from Microsoft:

    • Install Microsoft IIS 10.0

    For more details, see Installing Prerequisite Software on Windows Server 2016 Systems.

  • For Windows Server 2012 R2 systems:

    • Disable User Account Control (UAC).

    • Install Microsoft .NET Framework 4.7.1. You can download.NET software from Microsoft:

    • Install Microsoft IIS 8.0

    For more details, see Installing Prerequisite Software on Windows Server 2012 R2 Systems.

  • For Migrate API:

    Install Microsoft .NET Core Hosting Bundle (version 2.2 or greater). The Prerequisites script downloads and installs .NET Core Hosting Bundle 2.2.3.

    NOTE:If you install Microsoft .NET Framework on the Migrate Server host, you must reboot the server to complete the .NET Framework installation before you install the .NET Core Hosting Bundle.

TLS Protocol

PlateSpin Migrate Server supports connections using Transport Layer Security (TLS) 1.0, 1.1, and 1.2 protocols, according to the protocols enabled in the Windows Registry settings on the Migrate Server host operating system. Installation and upgrade do not modify the existing host OS settings for the TLS protocol.

Remote database: Ensure that the appropriate TLS settings are enabled for the operating systems on the intended Migrate Server host and the Microsoft SQL Server host before you install Migrate Server. See Database Server.

Source workloads: The TLS settings on the Migrate Server host OS must allow connections appropriate for the source workloads. See Configuring TLS Protocols for Migrate Hosts.

NOTE:If the source workload does not support TLS 1.2 or if TLS 1.2 is disabled on the source workload, you must enable TLS 1.0 and 1.1 on the Migrate server host to be able to migrate them.

Some Windows operating systems do not support TLS 1.2 by default. To use TLS 1.2, Windows requires you to update the OS and Microsoft .NET Framework on the source workload, then configure its Windows Registry settings to use TLS 1.2. A reboot is required. See Configuring Source Workloads to Connect Using TLS 1.2 in the PlateSpin Migrate 2020.2 User Guide.

1.1.2 System Requirements for PlateSpin Migrate Client

You can install the PlateSpin Migrate Client on the PlateSpin Server host or on a separate computer. For information about migration tasks supported by Migrate Client, see Deciding on the Migration Interface in the PlateSpin Migrate 2020.2 User Guide.

A standalone PlateSpin Migrate Client host must meet the system requirements in Table 1-2.

Table 1-2 Host Requirements for PlateSpin Migrate Client

Requirement

Details

Operating System

Any of the following, running on dedicated hardware or in a virtual machine:

  • Windows Server 2016

  • Windows 8.1, 8

  • Windows Server 2012, Windows Server 2012 R2

  • Windows 7

  • Windows Server 2008, Windows Server 2008 R2

NOTE:You must activate the Microsoft license for your Windows operating system prior to installing PlateSpin Migrate Client.

Disk Space

Minimum 3 GB

Windows Software Components

Microsoft .NET Framework 2 SP2, 3.5 SP1, and 4.7.1. You can download.NET software from Microsoft:

TLS Protocol

PlateSpin Migrate Client supports Transport Layer Security (TLS) 1.0, 1.1, and 1.2.

Enable the same TLS protocols that you allow for the operating system on the PlateSpin Migrate Server host. See Configuring TLS Protocols for Migrate Hosts.

1.1.3 System Requirements for PlateSpin Migrate Web Interface

PlateSpin Migrate provides a Web Interface that you can use to plan and execute automated migrations of workloads. The PlateSpin Migrate Web Interface is automatically installed when you install the PlateSpin Migrate Server. For information about migration tasks supported by Migrate Web Interface, see Deciding on the Migration Interface in the PlateSpin Migrate 2020.2 User Guide.

For information about supported web browsers and browser configuration requirements, see Supported Web Browsers in the PlateSpin Migrate 2020.2 User Guide.

For more information about working with the PlateSpin Migrate Web Interface, see About the PlateSpin Migrate Web Interface in the PlateSpin Migrate 2020.2 User Guide.

1.1.4 General Guidelines for Server Installation

Follow installation guidelines in Table 1-3 for trouble-free installation and operation of PlateSpin Migrate.

Table 1-3 Pre-Installation Checklist

Guideline

Remarks

Dedicated Host

Install the PlateSpin Server on a dedicated physical or virtual machine. See also Co-location.

Credentials

Perform all installation procedures using an account with administrative privileges.

When you install PlateSpin Migrate Server on a domain computer, you must log in to the PlateSpin Server during installation, removal, or upgrade as a domain user who is a member of the Domain Admin group and the local Admin group.

Windows Authentication for your Microsoft SQL Server Standard Edition or Enterprise Edition database server is supported in domain environments. If you use Windows Authentication for your database server, when you perform the PlateSpin Migrate Server installation or upgrade, you must log in to the PlateSpin Server as the domain user with SQL Admin rights. This user must also have local administrator rights to the PlateSpin Server. In addition, the Service User you specify for SQL Server credentials must have local administrator rights.

IP Address

Assign the PlateSpin Server host a static IP address.

Co-location

Do not co-locate the PlateSpin Server with:

  • Your domain controller

  • Existing web servers with IIS applications

  • A workload that you intend to migrate by using the product

  • Other PlateSpin software (PlateSpin Protect and PlateSpin Recon)

Database

The Microsoft SQL Server Express Edition included with PlateSpin Migrate cannot be installed on a domain controller in accordance with Microsoft Developer Network recommendations.

If you intend to use your own Microsoft SQL Server database (instead of the Microsoft SQL Server 2017 Express Edition included in your software distribution), ensure that it is supported and conforms to the product’s database requirements. See SQL Server Installation Requirements for Platespin Protect and Migrate (KB Article 7009809).

While multiple PlateSpin Migrate Servers can use the same remote database server, each Migrate Server requires a separate database instance.

For deployment guidelines based on your operational needs, see Database Server in the PlateSpin Migrate 2020.2 User Guide.

The database server and database instance for the Migrate Server must be available and configured to work with PlateSpin Migrate before you attempt to install the product. See Installing the Database Server.

UAC

Disable the User Account Control (UAC) during installation, removal, or upgrade.

Installation Workflow

Install the prerequisite software in the indicated order. Below is a high-level workflow for a typical PlateSpin Migrate installation:

  1. Supported operating system, followed by corresponding Windows Updates

  2. ASP.NET/IIS, followed by corresponding Windows Updates

  3. (Optional) Enable FIPS-Compliant Data Encryption

  4. SQL Server database, followed by applicable Microsoft updates

  5. PlateSpin Server

  6. (Conditional on your migration goals) PlateSpin Migrate Client