Portability Suite Server is the runtime execution engine underlying both PlateSpin® Migrate and PlateSpin® Protect products. For trouble-free operation of the Portability Suite Server, it is recommended that you install it on a dedicated physical or virtual machine. Specifically, do not install the Portability Suite Server on a machine that is:
A potential source workload
Your domain controller host
The following topics provide additional information about installation prerequisites for Portability Suite Server hosts.
Before starting the installation of the Portability Suite Server on a Windows Server 2003 system, ensure that the following prerequisite software components are installed on the intended Portability Suite Server host, in the specified order:
Microsoft IIS 5.0/6.0 (with ASP.NET)
Microsoft .NET Framework 2.0, SP2 and later. Download a copy from the Microsoft Download Center.
If you are installing the Portability Suite Server on a 64-bit Windows Server 2003 system, you must configure IIS to run in 32-bit mode. For details, see Knowledge Base article 20915.
Before starting the installation of the Portability Suite Server on a Windows Server 2008 system, ensure that the prerequisite .NET Framework and Web Server (IIS 7.0) features, roles, and services are installed on the intended Portability Suite Server host.
Download Microsoft .NET Framework 3.5 SP1 from the Microsoft Download Center.
The following procedures assume that you are installing the required items for the first time following the installation of the operating system. For detailed information, see your Windows documentation.
Log in to your intended Portability Suite Server host using the built-in Administrator account, also known as Local User Administrator (LUA), and launch the Server Manager (
> > ).Use the Server Manager’s Add Roles Wizard to install the hostname) tree in the left pane, right-click and select ).
role (in the (At the wizard’s prompt, select to install also the required Web Server dependencies (
along with the and items).On the wizard’s Role Services page, select to install the following services:
In the
group:Items under the
node: , , , , and .Items under the
node: , , , and .Items under the
node: , , , , , , , and .In the
group:
Items under the
node: , , ,Review your selections and complete the installation.
Log in to your intended Portability Suite Server host using the built-in Administrator account, also known as Local User Administrator (LUA), and launch the Server Manager (
> > ).Use the Server Manager’s Add Features Wizard to install the required .NET Framework 3.0 features (in the hostname) tree in the left pane, right-click and select ).
(On the wizard’s Select Features page, select the
item.This automatically selects all items in that group:
, , and (along with the and subitems).Review your selections and complete the installation.
Portability Suite 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 Portability Suite Server host prior to the installation of the Portability Suite Server. This is because Portability Suite 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:
On your Portability Suite Server host, install the Microsoft .NET Framework security update KB928365 released on July 10 2007.
Enable FIPS-compliant algorithms in the security options of your Portability Suite host’s local security policies:
Run secpol.msc and browse to .
Enable the
security option.Configure ASP.NET for FIPS support:
Access the machine.config file located in the following directory of your Portability Suite Server host:
..Windows\Microsoft.Net\Framework\vX.X.XXXXX\Config
Add the following under the <system.web> element:
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
Save the machine.config file.