1.2 Installing Prerequisite Software

This section provides information on installing the required ASP.NET, IIS, and .NET Framework software components. Because the packaging and distribution of these software components varies among different versions of the supported Windows Server platforms, procedures slightly. Use the indicated order of installation and setup.

1.2.1 Installing Prerequisite Software on Windows Server 2003 Systems

These procedures apply to Windows Server 2003 (32-bit, 64-bit) and Windows Server 2003 R2 (32-bit, 64-bit) systems. Differences, where applicable, are called out inline.

  1. Familiarize with system requirements and general guidelines (see Preparing to Install PlateSpin Migrate).

  2. Use an account with administrative privileges to log in to your intended PlateSpin Server host, then add the following Windows Components (Start > Run > appwiz.cpl > Add/Remove Windows Components):

    • Windows Server 2003: Application Server along with the ASP.NET and Internet Information Server (IIT) subcomponents.

    • Windows Server 2003 R2: Application Server along with the Internet Information Server (IIT) subcomponent only.

  3. Download and install the Microsoft .NET Framework 3.5 SP1 package.

  4. (Conditional) On Windows Server 2003 R2 systems, ensure that ASP.NET is properly registered with IIS by executing the following command at the command prompt:

    "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe" -i

  5. (Conditional) On all 64-bit hosts, ensure that IIS is configured to run in 32-bit mode. See Knowledgebase Article 20915.

1.2.2 Installing Prerequisite Software on Windows Server 2008 Systems

These procedures apply to Windows Server 2008 (32-bit, 64-bit) and Windows Server 2008 R2 systems. Differences, where applicable, are called out inline.

  1. Familiarize with system requirements and general guidelines (see Preparing to Install PlateSpin Migrate).

  2. Use the Local User Administrator (LUA) account to log in to your intended PlateSpin Server host, then add the Web Server (IIS) Role along with the following role services and their sub-roles (Server Manager > Roles > Add Role):

    — Common HTTP Features

    — ASP .NET

    ----—.NET Extensibility

    — ISAPI Extensions

    — ISAPI Filters

    — Security

    — Management Tools

  3. (Conditional, Windows Server 2008 only) Download and install Microsoft .NET Framework 3.5 SP1.

  4. Add these .Net Framework Features along with all sub-items (Server Manager > Features > Add: Feature):

    • .NET Framework

    • XPS Viewer

    • WCF Activation along with its HTTP Activation and Non-HTTP Activation sub-items.

  5. On 64-bit hosts (Windows Server 2008 x64 and Windows Server 2008 R2), ensure that IIS is configured to run in 32-bit mode. See Knowledgebase Article 20915.

1.2.3 Enabling Support for FIPS-Compliant Data Encryption Algorithms (Optional)

PlateSpin Migrate supports data encryption algorithms that are compliant with FIPS (Federal Information Processing Standards, Publication 140-2).

If compliance with FIPS is required, it must be enabled on the intended PlateSpin Server host prior to the installation of the PlateSpin Server. This is because PlateSpin Migrate runs in FIPS-compliant mode only if it detects that a workload’s operating system is running in FIPS-compliant mode.

NOTE:FIPS-compliant mode has a performance impact and might slow down the data transfer rate up to 30%.

To enable FIPS-compliant algorithms:

  1. Enable FIPS-compliant algorithms in the security options of your PlateSpin Migrate host’s local security policies:

    1. Run secpol.msc and browse to Local Policies > Security Options.

    2. Enable the System cryptography: Use FIPS compliant algorithms for encryption security option.

  2. Configure ASP.NET for FIPS support:

    1. Access the machine.config file located in the following directory of your PlateSpin Server host:

      ..Windows\Microsoft.Net\Framework\vX.X.XXXXX\Config

    2. Add the following under the <system.web> element:

      <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

  3. Save the machine.config file.