Prepare Answer File

An answer file provides all the details required for upgrade 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 upgrade 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 Upgrade/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.