ScaleOut StateServer®

Instructions for Unattended Setup


Please note that important changes have been made to unattended installations in version 5.0 to allow for added flexibility and customization. As a result, the
INSTALLTYPE and TARGETDIR properties that were used in earlier versions of the installer are no longer available. Customers upgrading to 5.0 should review this document and update their deployment scripts.

Quiet Mode

Installations can be run in "quiet mode" with no user interaction by running msiexec.exe from the command line with the /quiet switch.

For example, to install the 32-bit version of ScaleOut StateServer with all features, run the following command:
msiexec.exe /i soss_setup32.msi /quiet
To install the x64 version of ScaleOut StateServer with all features, run the following command:
msiexec.exe /i soss_setup64.msi /quiet
When running an unattended installation with UAC enabled (on Windows Vista/2008 or higher), you must run the setup using the Administrator account or run it from a command prompt that was started with "Run as Administrator..." privileges. It is not sufficient for your user to be part of the Administrators group if UAC is enabled.

After installation, a pre-configured soss_params.txt file should be copied over the unconfigured one in the StateServer installation directory. Restart the ScaleOut StateServer service (using the Windows sc.exe utility or the net start and net stop commands) for the new host configuration settings to take effect.

If no other options or properties are specified then the setup will install the ScaleOut StateServer service with all available features.

Customizing the Installation

There are two approaches to specifying which product features are installed. You can either use the standard INSTALLLEVEL property to select an installation type, or you can specify the individual features that you'd like installed using the ADDLOCAL property. If both the INSTALLLEVEL and ADDLOCAL properties are specified then the INSTALLLEVEL value will be ignored. Note that the INSTALLTYPE property that was used in earlier versions of the installer (prior to 5.0) is no longer available.

Using INSTALLLEVEL

Specifying an INSTALLLEVEL from the command line is equivalent to clicking one of the setup type buttons in the installer's wizard UI (i.e., the "SOSS Full Install" and "Remote Client" buttons). For example, to install the remote client components you would run the following command:
msiexec.exe /i soss_setup64.msi /quiet INSTALLLEVEL=500
The INSTALLLEVEL values supported by the setup are defined as follows:

500 Remote client installation
1000 Full server installation, including all features (Default)

If you do not specify an INSTALLLEVEL or an ADDLOCAL property (see below) then a full server installation will be performed.

Using ADDLOCAL

Individual features can be selected for installation from the command line using the ADDLOCAL property, where each feature is separated by a comma (and no spaces). This is equivalent to going into the installer's wizard UI and clicking the "Custom" setup type button to select the desired features from a list. For example, to install just the management tools and the Java libraries, you would run the following command:
msiexec.exe /i soss_setup64.msi /quiet ADDLOCAL=ManagementTools,JavaLibs
The following feature identifiers are supported:

Feature ID Description
Server The ScaleOut StateServer service. Do not include this feature if you want a remote client installation.
SamplesSamples for .NET, Java, and C development
ManagementTools(Recommended) Graphical and command line tools for managing the ScaleOut server and remote client configuration
DotNet20LibsLibraries to support .NET 2.0 client applications
DotNet35LibsLibraries to support .NET 3.5 client applications
DotNet40LibsLibraries to support .NET 4.0 client applications
JavaLibsLibraries to support Java client applications
NativeLibsHeaders and libs for building native C/C++ client applications

If you do not specify an ADDLOCAL property or an INSTALLLEVEL (see prior section) then all product features will be installed.

Installation Location

To set the directory that the product will be installed in, use the APPLICATIONFOLDER property. So, for example, to perform a 32-bit remote client installation to the non-default "e:\SOSS" directory, you would run:
msiexec.exe /i soss_setup32.msi /quiet INSTALLLEVEL=500 APPLICATIONFOLDER="e:\SOSS"

Many additional properties are defined by Windows Installer. Consult the Microsoft Developer Network's Property Reference for a complete list.