The following sections cover information relating to the minimum tested configurations of Archive Shuttle. If these requirements do not match the environment where Archive Shuttle is being installed, then the differences should first be discussed with Quadrotech Support.

Operating System

For a list of supported operating systems, see the Archive Shuttle Compatibility Guide.
Install the components below on this server.
Note: The Archive Shuttle installer will check for pre-requisites and assist with information about next steps.

*Not part of pre-requisites checks due to the fact this is required for Cargo Bay.

Internet Information Services (IIS) 7.5 or later

IIS 7.5 or later is required on the Archive Shuttle core server.
The Archive Shuttle installer will install two new Web Applications to the Default Website and create two new Application Pools. It is not necessary to configure these manually.
The following Web Server (IIS) Role services are required by Archive Shuttle:

Group Role / Service
Common HTTP Features
  • Static Content
  • Default Document
  • Directory Browsing
  • HTTP Errors
  • HTTP Redirection
Application Development
  • ASP.NET
  • .NET Extensibility
  • ISAPI Extensions
  • ISAPI Filters
Health and Diagnostics
  • HTTP Logging
  • Request Monitor
Security
  • Windows Authentication
  • Request Filtering
Performance
  • Static Content Compression
  • Dynamic Content Compression
Management Tools
  • IIS Management Console

The simplest way to install these components is to select the options to install:

  • Application Server
  • Web Server

The details of how to do this for different operating systems is described below:

Windows Server 2012

To ensure the required components are installed, perform the following steps in Server Manager:

  • In Server Roles, select “Web Server (IIS)”. When “Web Server (IIS)” is selected, a pop-up will appear describing additional components that will be installed.
  • In “Features” ensure that .Net Framework 4.5 > WCF Services > HTTP Activation is selected; a pop-up will appear showing additional components that will also be installed
  • For “Web Server Role (IIS)” > “Role Services”, make sure that the following options are selected in addition to those already shown:
    • Common HTTP Features > HTTP Redirection
    • Performance > Dynamic Content Compression
    • Security > Windows Authentication

Server Manager will then need to be run a second time in order to add .Net Framework 3.5. This is necessary because the installation path specification for Windows 2012 legacy components is not the same as new Windows 2012 components.
When running Server Manager for the second time, make the following selections:

  • It is not necessary to make any changes to the Server Roles; Web Server (IIS) should still be selected.
  • In “Features”, make sure that “.Net Framework 3.5 Features” is selected, and inside that option, also select “HTTP Activation”. When that option is selected, a pop-up will appear showing additional components that will be installed.

Finally .Net Framework needs to be activated within IIS. To enable this feature, perform the following steps in Server Manager:

  • In “Server Roles” navigate to “Web Server (IIS)”, expand that section to locate ASP.NET 3.5, and select it as shown below:


In Windows 2012, it is possible to install these required components using the following PowerShell command:
Install-WindowsFeature Web-Server -Source WIM:D:\Sources\Install.wim:4 ; Install-WindowsFeature Net-Framework-Features, NET-Framework-45-Features -Source D:\Sources\SxS ; Install-WindowsFeature Web-Asp-Net, Web-Net-Ext45, Web-Mgmt-Tools, Web-Windows-Auth, Web-Dyn-Compression, Web-Http-Redirect, NET-HTTP-Activation -Source WIM:D:\Sources\Install.wim:4 ;
Note: Ensure you adjust the command line to the correct paths required for the media on your system.

Windows Server 2012 R2

To ensure the required components are installed, perform the following steps in Server Manager:

  • In Server Roles, select “Web Server (IIS)”. When “Web Server (IIS)” is selected, a pop-up will appear describing additional components that will be installed.
  • In Features, make sure that .Net Framework 4.5 > WCF Services -> HTTP Activation is selected; a pop-up will appear showing additional components that will also be installed
  • For Web Server Role (IIS) > Role Services, make sure that the following options are selected in addition to those already shown:Common HTTP Features > HTTP Redirection
    • Performance > Dynamic Content Compression
    • Security > Windows Authentication

Server Manager will then need to be run a second time in order to add .Net Framework 3.5. This is necessary because the installation path specification for Windows 2012 legacy components is not the same as new Windows 2012 components.
When running Server Manager for the second time, make the following selections:

  • It is not necessary to make any changes to the Server Roles; Web Server (IIS) should still be selected.
  • In Features, make sure that .Net Framework 3.5 Features is selected, and inside that option, also select HTTP Activation. When that option is selected, a pop-up will appear showing additional components that will be installed.

Finally .Net Framework needs to be activated within IIS. To enable this feature, perform the following steps in Server Manager:

  • In Server Roles, navigate to Web Server (IIS), expand that section to locate ASP.NET 3.5, and select it as shown below:


In Windows 2012 R2, it is possible to install these required components using the following PowerShell command:
Install-WindowsFeature Web-Server -Source WIM:D:\Sources\Install.wim:4 ; Install-WindowsFeature Net-Framework-Features, NET-Framework-45-Features -Source D:\Sources\SxS ; Install-WindowsFeature Web-Asp-Net, Web-Net-Ext45, Web-Mgmt-Tools, Web-Windows-Auth, Web-Dyn-Compression, Web-Http-Redirect, NET-HTTP-Activation -Source WIM:D:\Sources\Install.wim:4 ;
Note: Ensure you adjust the command line to the correct paths required for the media on your system.

Windows Server 2008 R2

To ensure the required components are installed, perform the following steps in Server Manager:

  • In Roles, add the following:
    • Application Server
    • Web Server (IIS)

When “Application Server” is selected, a pop-up will appear that lists some additional components and features that will be installed.

  • For the Application Server “Role Services”, make sure “Web Server (IIS)” is selected.


When Web Server (IIS) is selected, a pop-up will appear which lists some additional components and features that will be installed. After that selection is confirmed, “HTTP Activation” will be automatically selected under “Windows Process Activation Service Support”.

  • For the Web Server (IIS) “Role Services”, no additional selections are needed.

Note: When installing the required Windows 2008 R2 components, make sure that you have the installation media available and configured/specified in Server Manager if required.
.Net Framework 4.5 or later should then be installed. A link to this is provided in the Archive Shuttle Core installer.
Following the installation of these components on Windows 2008 R2, a system restart may be needed.

Internet Explorer 9 or later

We recommend that you have Internet Explorer 9 or higher installed in order to successfully configure and use Archive Shuttle.
Note: If Internet Explorer is to be used to manage Archive Shuttle, then the machine names and IP addresses that will be used should be added to the Internet Explorer Trusted Sites.

ASP.NET State Service

The ASP.NET State Service needs to be set to “Automatic” start. The default setting for this service is manual.

SQL Server

For a list of supported versions of SQL Server, see the Archive Shuttle Compatibility Guide.
Note: It is recommended to have the latest SQL Server service pack installed.

SQL Server Editions

Although Enterprise Edition of Microsoft SQL Server is recommended, Standard Edition may be used if the SQL instance uses the recommended (not minimum) resources associated with the size of migration you are performing. Planning for additional time will be required to accommodate regularly required offline maintenance.

SQL Collation

The collation for the SQL Server installation must be case-insensitive, accent-sensitive (CI, AS); case-sensitive and accent-insensitive installations are not supported.
We recommend using latin1_General_CI_AS.

SQL Server CLR Types

Install a supported version of the Microsoft SQL Server CLR Types (64-bit) using the Microsoft supplied installation files. The Archive Shuttle installer has a download option for a supported version.
The download link used in the installer is:
http://go.microsoft.com/fwlink/?LinkID=239644&clcid=0x409

SQL Server Management Objects

Install a supported version of the Microsoft SQL Server Management Objects (64-bit) using the Microsoft supplied installation files. The Archive Shuttleinstaller has a download option for a supported version.
The download link used in the installer is:
http://go.microsoft.com/fwlink/?LinkID=239659&clcid=0x409
Note: The links are given in the sections above in case the files are to be downloaded to a staging area. For example, when the Archive Shuttle server will not have direct internet access.

SQL Server Software Configuration

Both Windows Authentication mode and Mixed Mode Authentication are supported.
The SQL installation must be case-insensitive; case-sensitive SQL installations are not supported.

Print Friendly, PDF & Email