Running a Scripted Installation

Before running the scripted upgrade:

All related database must exist (see Upgrade/Create Databases)
If you are encrypting identities needed in the upgrade, you must have configured and distributed both the certificate store and the certificate validating those identities (see Prepare Encrypted Credentials for Upgrade)
You must have prepared the local copy of the answer file, correctly configured for the type of server undergoing upgrade (see Prepare Answer File)
From the current server, you must have access (either through a network share, or using a local copy) to the complete unzipped archive of the upgrade resources (do not attempt to extract portions, as many scripts and files interact in this process).

When all is ready, triggering a scripted upgrade is a simple matter of invoking the supplied PowerShell script with the correct parameters. The command line can optionally be simplified by first declaring some PowerShell variables to contain those parameters.

To configure variables and trigger scripted installation:

Ensure that you are running an elevated PowerShell session (that is, started with the Run as administrator option).

Optionally, declare PowerShell variables to contain the various parameters.

This simplifies the final command line. Declaring PowerShell variables is as simple as identifying them (with a leading dollar sign) and their values at the command prompt. All parameters for this script default to the string type; but if you are cautious, you can also enforce the cast to the string type by prepending the [string] literal before the variable name. Therefore both of the following forms of variable declaration are acceptable:

$greet = "Hello"
[string]$greet = "Hello"

The following parameters are mandatory for the command line you will use later, and may be declared as string variables in the above manner. Of course, the suggested variable names can be modified to suit your preferences, as long as you reference them accurately in the command line. Remember to enclose the path values in double quotation marks:

Required Argument	Description
`$FnmpInstallerMsi`	Fully qualified path to the installation .msi for FlexNet Manager Suite. This is typically: `drive-and-path\FlexNet Manager Suite\Installers\FlexNet Manager Suite\FlexNet Manager Suite Server.msi`
`$AnswerFile`	Fully qualified path to the answer file that you have customized and saved for this server. Once again, check that this answer file has the correct setting for the `FEATURES` parameter, as this entirely determines the kind of server that is installed on this device.
`$FNMSConfigFile`	Fully qualified path to the Configuration file to be passed to `Config.ps1`. This is typically: `drive-and-path\FlexNet Manager Suite\Support\Config\FNMS Windows Authentication Config.xml`

In addition, the following parameter is optional, and is relevant only for second and subsequent attempts at upgrade on this server:

Optional Parameter	Description
`$configMode`	If present, must have one of the following two string values: `updateConfig` (default) — Modifies the upgrade only with new settings that have been changed in the answer file `forceUpdateConfig` — Overwrite all settings for this upgrade.

Enter the command line to trigger the upgrade script.
CAUTION:
The order of parameters is critical. There are no keys or labels to indicate which parameter is which.
This example uses the three mandatory parameters as saved in the PowerShell variables suggested above:
```
cd drive-and-path\FlexNet Manager Suite\Support
.\InstallFNMS.ps1 $FnmpInstallerMsi $AnswerFile $FNMSConfigFile
```
This example shows the full text for the paths used in the correct order (normally all on the same line, but here formatted for easier reading):
```
cd drive-and-path\FlexNet Manager Suite\Support
.\InstallFNMS.ps1 
     "drive-and-path\FlexNet Manager Suite\Installers\FlexNet Manager Suite\FlexNet Manager Suite Server.msi"
     "drive-and-path\FlexNet Manager Platform\Support\answerfile.txt"
     "drive-and-path\FlexNet Manager Suite\Support\Config\FNMS Windows Authentication Config.xml"
```

The upgrade is triggered, and immediately followed by configuration appropriate to this server type.

Remember: If a required parameter is missing from the answer file, a dialog appears during the process to request the missing value.