Populate the Downloadable Libraries
- For the ARL: https://www.managesoft.com:443/support/Compliance/RecognitionAfter82.cab
- For the EOSL library: https://www.managesoft.com:443/support/Compliance/EOSL.cab
- For the SKU library: https://www.managesoft.com:443/support/Compliance/PURL.cab
- For the PURLs: https://update.managesoft.com:443/ProductUseRights, including access to any sub-directories of this that may be returned to your server in response to its initial request.
If neither direct access nor access through a proxy server can be provided, you can use an alternative process to manage library updates manually, as described in Manual Updates of Library Data.
At installation time, you need to trigger download of the libraries to create a baseline ready for product use. Library downloads check the terms of your Flexera license. That is why this task cannot be attempted before a current license is installed (see Importing an Updated Flexera License), and must occur on the same server where your license was imported to activate the product.
In summary, the process downloads several different files to which you are entitled, saving them into staging locations on your batch server (or the server hosting that functionality). When the downloads are all completed successfully, the files are imported into the compliance database as required. The staging locations are subdirectories of %PROGRAMDATA%\Flexera Software\FlexNet Manager Platform\DataImport\Content. If necessary, you may customize this by saving your preferred path in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\Recognition\ContentImportDirectory.
For details of log files, see the end of the following procedure.
Complete this procedure as administrator (fnms-admin
), having database rights as described in earlier
sections.
To trigger a download of the current libraries:
- mgsImportRecognition*.log
- recognition*.log (for the Application Recognition Library)
- importPURL*.log.
maxSizeRollBackups
in the .config
files). You cannot modify the file path for logging within the
.config files, but you could if necessary customize the
file name(s). If you really need a different file path for these logs, you can
change the value used for %property{ComplianceLoggingPath}
in
the .config files by creating a REG_SZ
registry key at SOFTWARE\WoW6432Node\ManageSoft
Corp\ManageSoft\Compliance\CurrentVersion\LoggingBaseDirectory on
your batch server (or in smaller implementations, the server hosting
this functionality), and setting the registry key to your preferred path.
(Removing this key again restores the default value.)