Update the batch server

The batch server is the integration point that correlates all your entitlement records and your consumption revealed in inventory to work out your reconciled license position.

You do not need this process if you have either of:

• A single-server implementation combining the web application server, the batch server, and the inventory server in one; or
• A two-server application implementation where you have combined the batch server and inventory server functionality on one computer and kept the web application server as a second server.

In these two cases, this step is already completed and you should skip ahead to Installing a Free-Standing Studio.

For a three server implementation, continue this process as administrator (fnms-admin) on your batch server.

Tip: Currently MSMQ limits the hostname of the batch server to 15 characters (excluding the domain qualifier).

To install the batch server:

1. On the batch server, open Windows Explorer.
2. Copy the downloaded archive FlexNet Manager Suite 2024 R2 Installer.zip from your staging location to a convenient location on this server (such as C:\temp), and unzip it.
   Tip: Unzipping the archive locally on each of your servers simplifies running the configuration scripts later in the process. After running the installers, PowerShell scripts need to be Run as Administrator. Notice that the entire archive must be present, as scripts reference other elements from the archive.
3. Navigate in the unzipped archive to the FlexNet Manager Suite\Installers\FlexNet Manager Suite folder.
4. Start (double-click) setup.exe.
   Tip: You must start the installation by running setup.exe, rather than running the MSI by any other means. The setup file also installs Visual C++ 2010 Redistributable (if it is not already present), which is a prerequisite for integration with FlexNet Manager for SAP Applications.
5. Select the Custom installation path, and select only the Batch scheduling server for this installation, ensuring that the other options are deselected (displaying a cross).
   Take note of the installation location for future reference.
6. When asked to enter the credentials to be used for running batch processes, be sure that the account you enter already has Logon as a service permission (see Authorize the Service Account).
7. On the same page of the wizard, for Server type, choose either Production for your main server installation, or Failover if this is a stand-by or testing server.
   Tip: On your Production server, the batch scheduler and batch processor are automatically started as part of the installation process, while on a Failover server, both are disabled by default. If you need to switch between your production and stand-by servers, you must manually:

   • Disable the batch scheduler and processor on the product batch server
   • Enable the batch scheduler and processor on the standby batch server.

   These adjustments are made in the Microsoft Services control panel.
8. For the batch processor, you are asked to identify the folder where intermediate packages (uploaded from inventory beacons) are saved prior to processing. The default location is %ProgramData%\Flexera Software\Beacon\IntermediateData. This default is formed by appending IntermediateData to the value of the base directory saved in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Beacon\CurrentVersion\BaseDirectory. This base location is also used by other processes, and should be changed only with care.
   Tip: A second folder, a network share, is used for handing off files uploaded through the web interface (such as inventory spreadsheet imports) for processing by the batch server. For this share, the default path is %ProgramData%\FlexNet Manager Platform\DataImport, and the path is saved in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\DataImportDirectory. There is also a parallel folder for data export. For implementations that separate the web application server from the batch server, these shares must also be configured and accessible from both servers.

   For more information, see Configure Network Shares for Multi-Server.
9. When successful, close the installation wizard.