Prepare the Answer File(s)

An answer file provides all the details required for installation of your server(s).

Tip: If you miss a setting from the answer file that is required for one of your servers, a dialog box appears during the installation process to request the missing value.

To customize your answer file:

From your downloaded and unzipped archive, and using a flat text editor, open the following file:
```
drive-and-path\FlexNet Manager Suite\Support\sample-fnms-answer.txt
```
Save a working copy on your local drive for editing.
It may be helpful in a multi-server implementation to use a file naming convention that identifies which server this answer file copy is intended for.
If you have set up encryption for credentials used in this answer file, uncomment (by removing the leading hash or pound character) both the Security section header and the Store parameter, providing the path and file name for your credential store on this server:
Example:
```
[Security]
Store = drive:\path-to-file\fnms.password.store.xml
```

Adjust the FEATURES parameter to suit the type of server being installed and configured. (Come back and adjust this value for each server in a multi-server implementation, saving a separate answer file for each server type.)

Use one (or more) of the following values, depending on the server type:

Server type	Value
Single-server implementation	Use either of: `ALL` `FleNetManagerPlatform` Alternatively, you may list all of the following component identifiers, separating each with a comma and space.
The web application server	`WebUI`
The batch server	`BatchScheduler, BatchProcessor` (Use both labels on your batch server.)
The inventory server	`InventoryServer`

Tip: Although these notes continue to provide guidance about which parameters apply to which server type, the remaining values in the answer file may all be completed in a single editing pass. The controlling script extracts only the parameters required for each server type, as declared by the FEATURES parameter that you have just customized. Therefore, other than configuring the FEATURES parameter for each server type, the remainder of the answer file is portable across the various types of server that you may be installing.

The four settings for directories (in the middle of the [Installation] section) may be left commented out if you are satisfied with the default values; or else you may uncomment the parameter and add a fully qualified path.

The parameters, the server type applicable for each one, and the default values are as follows:

Parameter	Applies to	Default
`INSTALLDIR`	All server types	`C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\`
`DATAIMPORTDIR`	The batch server, and web application server	`C:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\`
`WAREHOUSEDIR`	Inventory server	`C:\ProgramData\Flexera Software\Warehouse\`
`INCOMINGDIR`	Inventory server	`C:\ProgramData\Flexera Software\Incoming\`

When preparing the answer file for your batch server, do one of the following:
- If you have implemented a credential store, uncomment the BatchProcessStoreReference parameter and provide the store reference for this credential. (When you provide a store reference, any values in the BATCHPROCESSUSERNAME and BATCHPROCESSPASSWORD are ignored.)
- Otherwise, complete the values for the BATCHPROCESSUSERNAME and BATCHPROCESSPASSWORD parameters, identifying the service account (example: svc-flexnet) you already configured (see Authorize the Service Account).

For the following set of identities, do one of the following for each separate [Identity]:

If you have implemented a credential store, uncomment the StoreReference parameter and add the store reference for the credential. (When you provide the store reference, any values for Username and Password are ignored. Be certain not to modify the Name parameter that specifies the purpose for each identity.)
Otherwise, insert the account name and password for each identity. This is normally the service account (example: svc-flexnet) you already configured (see Authorize the Service Account). Recommended format for the Username parameter is domain\username, such as:
```
Username = exampleDomain\svc-flexnet
```

All the identities for which the name includes "Pool" are used to configure Microsoft IIS on the respective server. Two others are used to run scheduled tasks. The identities and the server type to which they apply are:

Identity names	Apply to
`SuiteAppPoolUser` `ExternalAPIAppPoolUser`	The web application server
`BeaconAppPoolUser` `BusinessReportingAuthUser` (also for IIS configuration) `ReconciliationScheduledTaskUser`	The batch server
`RLAppPoolUser` `DLAppPoolUser` `InventoryScheduledTaskUser`	The inventory server

The [Parameters] section gives the servers in a multi-server implementation information about accessing each other, and are also used with Microsoft Message Queueing (MSMQ). In a single server implementation, you still need to provide these values, even though they refer to functionality on the same physical server. You do not need to specify the web application server here, as this is the component that manages intercommunication, once it receives these other values.
For ReconciliationServer, enter the fully qualified hostname of your batch server ("reconciliation server" is a legacy name for the batch server); and enter a full URL for the same server in ReconciliationServerURL. For your inventory server, only the URL version is required.
Tip: In a single server implementation, in the URL versions you may use localhost within the URL.
Identify the database server and database names with which each of your implementation servers must communicate. For your on-premises implementation, use the "single database group setup".
In all but the largest implementations, the databases all run on the same database server, so that the values for these four "DatabaseServer" names are identical. (You may, of course, vary the values if you have implemented multiple separate database servers.) Use the same format for identifying your database server as would appear inside a connection string. For example, if your database server hosts multiple database instances, and your operations databases are not in the default instance, use a format like:
```
serverName\instanceName
```
The suggested database names proposed in Create Databases are:
```
FNMSDatabaseName = FNMSCompliance
IMDatabaseName = FNMSInventory
DWDatabaseName = FNMSDataWarehouse
SnapshotDatabaseName = FNMSSnapshot
```
To configure optional security scanning of uploaded documents being attached to licenses, contracts, purchases and the like, find and edit this section in the answer file for your web application server:
```
# Enable/ Disable file scanning feature
# EnableFileUploadScan = Replace_EnableFileUploadScan_Here
# Path to Filescanner.ps1 that will be used to perform file scanning
# FileUploadScannerPath = Replace_FileUploadScannerPath_Here
```
For information about setting up on-demand anti-virus scanning of documents, see the section Preventing Uploads of Malicious Files in the FlexNet Manager Suite System Reference (on-premises edition for release 2020 R2 or later), available through http:/docs.flexera.com in either PDF or HTML format. The two registry settings described here form only a part of the required configuration, and the values depend on your design decisions, file names and paths. Configuring these settings through the answer file is optional: if you prefer, you may return to your web application server after installation is complete, and modify the settings manually. An example of an edited section of the answer file for the web application server that turns on document scanning with the recommended anti-virus tool is:
```
# Enable/ Disable file scanning feature
EnableFileUploadScan = true
# Path to Filescanner.ps1 that will be used to perform file scanning
FileUploadScannerPath = C:\ClamAV\Filescanner_ClamAV.ps1
```
Be sure to update the example with the correct path to your PowerShell script for integrating your chosen anti-virus tool; but keep in mind that EnableFileUploadScan = true is a mandatory setting to allow document scanning.
Save your edited answer file.
For a multi-server implementation, re-edit the values for the FEATURES parameter (near the top of the file) to suit each different target server, and save a renamed copy that follows your file naming convention linking the answer file with the target server type. Ensure that each answer file is accessible from its intended target server.

Important: The supplied sample answer file does not contain an ADDLOCAL parameter, because this parameter is now deprecated. Do not re-insert this parameter into your answer file, since this forces legacy behavior which limits the flexibility of multi-server implementations.

Parameter values

Use a flat text editor to prepare your answer file with the parameters you require from the following table.

In this table, each section is listed in the order they should appear in the answer file. Within each section are the parameters that may appear there, together with permitted or sample values and other notes. Parameters are in alphabetic order here, and may appear in any order with the correct section.

Section (ordered)	Parameter (alphabetical)	Values/Notes
`[Installation]`	`ADDLOCAL`	A selection of the application server functionality to be installed on the current computer server. For a single server implementation, use the keyword `ALL`. Otherwise, the value may be a comma-separated list of any combination of the following values: `BatchScheduler` — known in this document as the batch server `InventoryServer` — the server for the inventory functionality within FlexNet Manager Suite `WebUI` — the web application server.
`[Installation]`	`BATCHPROCESSPASSWORD`	The password for the account nominated in `BATCHPROCESSUSERNAME`.
`[Installation]`	`BATCHPROCESSUSERNAME`	The account used for reconciliation calculations and other batch processing on the batch server. If the account is an Active Directory account, you may specify the name alone. If it is a machine account on the batch server, specify the machine name and account separated by a backslash, such as `BATCH-SCHEDULING-MACHINE\AccountName`.
`[Installation]`	`DATAIMPORTDIR`	Only applicable for installation of central servers. A staging folder for data imported through the web interface for FlexNet Manager Suite being transferred to the batch server for processing. Typical value: `C:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport`
`[Installation]`	`FNMPDATABASENAME`	The name of the main compliance database for the system. The default value is `FNMP`.
`[Installation]`	`FNMPDBAUTHMODE`	Authentication mode for each of the databases may have one of these values: `SQLServer` — The connection uses SQL Server authentication. In this mode, you must supply the matching account name and password for the SQL Server account used. `WindowsNT` — The connection uses integrated Windows authentication.
`[Installation]`	`FNMPDBPASSWORD`	The password for the SQL Server account specified in `FNMPDBUSERNAME` (required only when `FNMPDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`FNMPDBSERVERNAME`	The name of the database server running the compliance database. You may use any of the following: `.` (dot) when the database is installed on the current server where the installation is occurring An IP address A fully-qualified domain name The simple server name (provided that the DNS is correctly configured to resolve this name when used from the installing server).
`[Installation]`	`FNMPDBUSERNAME`	The SQL Server account to access the compliance database (required only when `FNMPDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`FNMPDWDATABASENAME`	The name of the main data warehouse database for the system. The default value is `FNMPDataWarehouse`.
`[Installation]`	`FNMPDWDBAUTHMODE`	Authentication mode for each of the databases may have one of these values: `SQLServer` — The connection uses SQL Server authentication. In this mode, you must supply the matching account name and password for the SQL Server account used. `WindowsNT` — The connection uses integrated Windows authentication.
`[Installation]`	`FNMPDWDBPASSWORD`	The password for the SQL Server account specified in `FNMPDWDBUSERNAME` (required only when `FNMPDWDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`FNMPDWDBSERVERNAME`	The name of the database server running the data warehouse database. You may use any of the following: `.` (dot) when the database is installed on the current server where the installation is occurring An IP address A fully-qualified domain name The simple server name (provided that the DNS is correctly configured to resolve this name when used from the installing server).
`[Installation]`	`FNMPDWDBUSERNAME`	The SQL Server account to access the data warehouse database (required only when `FNMPDWDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`IMDATABASENAME`	The name of the main FlexNet inventory database for the system. The default value is `IM`.
`[Installation]`	`IMDBAUTHMODE`	Authentication mode for each of the databases may have one of these values: `SQLServer` — The connection uses SQL Server authentication. In this mode, you must supply the matching account name and password for the SQL Server account used. `WindowsNT` — The connection uses integrated Windows authentication.
`[Installation]`	`IMDBPASSWORD`	The password for the SQL Server account specified in `IMDBUSERNAME` (required only when `IMDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`IMDBSERVERNAME`	The name of the database server running the FlexNet inventory database. You may use any of the following: `.` (dot) when the database is installed on the current server where the installation is occurring An IP address A fully-qualified domain name The simple server name (provided that the DNS is correctly configured to resolve this name when used from the installing server).
`[Installation]`	`IMDBUSERNAME`	The SQL Server account to access the FlexNet inventory database (required only when `IMDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`INCOMINGDIR`	Identifies the folder (on the inventory server) where a range of incoming data is stored in sub-folders. The default value is `$WAREHOUSEDIR\Incoming` (that is, a subfolder of the location declared in `WAREHOUSEDIR`). Examples of folders nested inside `INCOMINGDIR` include: `BeaconStatus` for the state of the beacon itself (enabled, disabled, and so on) Inventories for storage of FlexNet inventory agent files (`.ndi` files) `Logs` contains log files generated by inventory agents on managed devices.
`[Installation]`	`INSTALLDIR`	The folder where the software is to be installed. The default values are as follows, with `ProgFiles` being C:\Program Files on 32-bit systems, and C:\Program Files (x86) on 64-bit systems: web application server functionality: `ProgFiles`\Flexera Software\FlexNet Manager Platform\WebUI batch server functionality: `ProgFiles`\Flexera Software\FlexNet Manager Platform\DotNet\bin Inventory server functionality: `ProgFiles`\Flexera Software\FlexNet Manager Platform\Importers Inventory beacon: `ProgFiles`\Flexera Software\Inventory Beacon
`[Installation]`	`SNAPSHOTDATABASENAME`	The name of the snapshot database used for the system reports and performance optimization. The default value is `Snapshots`.
`[Installation]`	`SNAPSHOTDBAUTHMODE`	Authentication mode for each of the databases may have one of these values: `SQLServer` — The connection uses SQL Server authentication. In this mode, you must supply the matching account name and password for the SQL Server account used. `WindowsNT` — The connection uses integrated Windows authentication.
`[Installation]`	`SNAPSHOTDBPASSWORD`	The password for the SQL Server account specified in `SNAPSHOTDBUSERNAME` (required only when `SNAPSHOTDBAUTHMODE` is set to `SQLServer`).
`[Installation]`	`SNAPSHOTDBSERVERNAME`	The name of the database server running the snapshot database. You may use any of the following: `.` (dot) when the database is installed on the current server where the installation is occurring An IP address A fully-qualified domain name The simple server name (provided that the DNS is correctly configured to resolve this name when used from the installing server).
`[Installation]`	`SNAPSHOTDBUSERNAME`	The SQL Server account to access the snapshot database (required only when `SNAPSHOTDBAUTHMODE` is set to `SQLServer`).
`[Configurations]`	-	A container for the following four sections: `[Skip]` `[Identity]` `[Parameters]` `[Register Flexera Service Gateway]` The `[Configurations]` section does not directly contain any parameters of its own.
`[Skip]`	`Step`	Add to this section any steps in the installation process that you want to bypass entirely. For example, if you do not want to use your system with other Flexera products (such as App Portal / App Broker), you can use: `Step = Register Flexera Service Gateway`
`[Identity]`	(see below)	An `[Identity]` group specifies an application pool identity for Microsoft IIS. Each group identifies a single `Name`, `Username`, and `Password` for the application pool. Since several of these pools are required, specify a separate `[Identity]` group for each of them.
`[Identity]`	`Name`	The name for a user in a given application pool, in the form `BeaconAppPoolUser`. The names must match the names available in IIS on an operational beacon (or on the central application server, as the case may be). The relevant user name parameters are: `BeaconAppPoolUser` `BusinessReportingAuthUser` `DLAppPoolUser` `ExternalAPIAppPoolUser` `RLAppPoolUser` `ScheduledTaskUser` `SuiteAppPoolUser`
`[Identity]`	`Password`	The (optional) password for the `Username` for this `[Identity]` group.
`[Identity]`	`Username`	The account named in the IIS application pool. If the account is an Active Directory account, you may specify the name alone. If it is a machine account on the inventory beacon, specify the machine name and account separated by a backslash, such as `BEACON-MACHINE\AccountName`.
`[Parameters]`	`InventoryServerURL`	The base URL at which other devices may contact the inventory server component of the system. Where multiple parts of the server functionality coexist on a single computer, you still need to declare each of the URLs separately.
`[Parameters]`	`ReconciliationServerURL`	The base URL at which other devices may contact the batch server component of the system. Where multiple parts of the server functionality coexist on a single computer, you still need to declare each of the URLs separately.
`[Parameters]`	`WebServerURL`	The base URL at which other devices may contact the web application server component of the system. Do not include the folder `/Suite`. Where multiple parts of the server functionality coexist on a single computer, you still need to declare each of the URLs separately.
`[Register Flexera Service Gateway]`	`GatewayHost`	Omit for inventory beacons; use only for application servers. Do not provide a full URL, as this is generated automatically. Instead, provide one of: An IP address A fully qualified domain name such as `fsgserver.tmnis.org` A machine name (assuming that your DNS is fully configured and accessible) `localhost` if the Gateway is co-located on your web application server.
`[Register Flexera Service Gateway]`	`GatewayPassword`	Omit for inventory beacons; use only for application servers. Provide the password for the account specified in `GatewayUsername`.
`[Register Flexera Service Gateway]`	`GatewayPort`	Omit for inventory beacons; use only for application servers. The default port for Flexera Service Gateway is 9443. Match the configured port for the Gateway.
`[Register Flexera Service Gateway]`	`GatewayUsername`	Omit for inventory beacons; use only for application servers. Provide the account name for the administrator account configured on Flexera Service Gateway.
`[Beacon Links]`	`BEACONSVCENDPOINT`	The URL to which the beacon service on this inventory beacon should connect. For a beacon at the top level of your beacon hierarchy, this points to the batch server; for beacons further down the hierarchy, it points to their parent inventory beacon. Include the protocol. Sample format: `http://Batch-server.myDomain.com`
`[Beacon Links]`	`FNMPWEBUIURL`	On a child inventory beacon that reports to another inventory beacon, omit this setting. For an inventory beacon at the top level of your beacon hierarchy, specify the URL for the central web application server. Top-level beacons collect configuration files and the like from this server, both for their own use and for dissemination through the beacon hierarchy.
`[Scheduled Tasks]`	`CONFIGURESCHEDS`	Boolean, with values either `TRUE` or `FALSE`. When true, the installer tries to configure the Windows Scheduled Tasks appropriately for this installation. When false, scheduled task configuration is left as an exercise for the installing operator.
`[Scheduled Tasks]`	`SCHEDPASSWORD`	The password for the account named in `SCHEDUSERNAME`.
`[Scheduled Tasks]`	`SCHEDUSERNAME`	The account name used to run Windows Scheduled Tasks when `SCHEDUSERNAMEMODE` is set to `OTHER`.
`[Scheduled Tasks]`	`SCHEDUSERNAMEMODE`	May be set to either: `SYSTEM`, so that scheduled tasks are run by the local SYSTEM account (most often the account running the inventory beacon services as well) `OTHER`, in which case the account credentials must be specified in `SCHEDUSERNAME` and `SCHEDPASSWORD`.
`[Ports]`	`HTTP_PORT`	Provide the port for the HTTP proxy server. Example: `HTTP_PORT = 3128`
`[Ports]`	`HTTP_PROXY`	Provide the proxy server name for HTTP connections to be used by the installer when installing the inventory agent. The default value is blank, meaning not to use a proxy. Multiple names may be separated by semi-colons. Example: `HTTP_PROXY = tmnis.com;tmnis.com.de`
`[Ports]`	`NO_PROXY`	The valid URLs (which may include fully qualified domain names of servers) for which the installation agent, while installing the inventory agent on a target device, should ignore the proxy setting(s) declared in `HTTP_PROXY`. There is no default value. Multiple names may be separated by semi-colons. Example: `NO_PROXY = tmnis.com;tmnis.com.de`
`[Folders]`	`DATADIR`	For installation of stand-alone inventory beacons, this specifies the parent folder for inventory beacon logs and configuration files. After installation/update, this value is saved in the `DistributionLocation` registry value. If this parameter is omitted, the parent folder is taken from the first available of: `ImportXMLDirectory` registry value `BaseDirectory` registry value The default location C:\%CommonAppData%\Flexera Software. Tip: This value cannot be specified for an inventory beacon that is co-located on your batch server (or, in smaller implementations, the server hosting this functionality). For a co-located inventory beacon, FlexNet Manager Suite automatically uses the appropriate paths to suit the batch server.
`[Folders]`	`STAGEDIR`	Applies to installations of the central application server and inventory beacons. Identifies the staging folder where packages for installing and upgrading inventory agents on managed devices and inventory beacons are stored, awaiting automatic distribution. If this parameter is omitted, the path is created from the first available of: `DATADIR` if declared (see above) `DistributionLocation` registry value (if this answer file is being used for an upgrade, and the registry has been previously set, such as through an earlier declaration of `DATADIR`) The default %CommonAppData%\Flexera Software\Staging\Common\.
`[Folders]`	`UPLOADDIR`	For installation of inventory beacons, use this to specify the destination URL on this beacon for files being uploaded from managed devices (inventory targets using the FlexNet Inventory Agent). Include the protocol, which may be HTTP, FTP, or FILE. If this parameter is omitted, the path is created from the first available of: `DATADIR` if declared (see above) The default %CommonAppData%\Flexera Software\Incoming\Inventories.
`[Folders]`	`WAREHOUSEDIR`	This is base folder containing other locations for data uploads. Where this is not declared, the base folder name is taken from the first available of the following: `DistributionLocation` registry value (see `DATADIR` above) `RepositoryLocation` registry value `ImportXMLDirectory` registry value `BaseDirectory` registry value The default value, read from the `%CommonAppData%` environment variable.