cancel
Showing results for 
Search instead for 
Did you mean: 
steven_donovan1
Active participant

FNMS move all Logs, Readers, and intermediate data to a data drive.

Hi,

On the FNMS Application server is there a way to move all logs and folders to another data drive? Most customers do not want anything installed on the C drive.

 

Thanks,

Steve

8 Replies
Flexera BradAkers
Flexera

Re: FNMS move all Logs, Readers, and intermediate data to a data drive.

Steven, 

FlexNet Manager is tied to .Net and such some logs and other items cannot be moved off of the C drive for the Application and Beacon servers. 

 

For FNMS agents you can control where the logs are written to however by updating the config.ini during install. Please let me know if you have any other questions. 

 

Thanks

Brad

Community Manager ChrisG Community Manager
Community Manager

Re: FNMS move all Logs, Readers, and intermediate data to a data drive.

Much FlexNet application data (like data for other applications) is stored under the system %ProgramData% directory. Organizations typically configure this directory to be on the C: drive, but it could be placed elsewhere if people want application data stored somewhere different. This is something that would be configured at the operating system level, not something configured just for FlexNet or any other specific application.

Some selected data directories can be configured at installation time to not be placed under %ProgramData%. I think [at least some of] these can be configured in the install wizard UI, but I typically do installs using an msiexec command line so know the settings to configure on the command line better than what can be done in the install wizard UI:

  • Alternate location for %ProgramData%\Flexera Software\Beacon: BASEDIR=D:\Beacon
  • Alternate location for %ProgramData%\Flexera Software\FlexNet Manager Platform\DataImport: DATAIMPORTDIR=D:\DataImport
  • Alternate location for %ProgramData%\Flexera Software\WarehouseWAREHOUSEDIR=D:\Warehouse
  • Alternate location for %ProgramData%\Flexera Software\IncomingINCOMINGDIR=D:\Incoming

For example:

msiexec /i "FlexNet Manager Suite Server.Msi" /l*v install.log BASEDIR=D:\Beacon DATAIMPORTDIR=D:\DataImport WAREHOUSEDIR=D:\Warehouse INCOMINGDIR=D:\Incoming

After installation there are some registry entries which can be set (or changed) to point to alternate locations:

  • HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Beacon\CurrentVersion\BaseDirectory (default location if not changed: %ProgramData%\Flexera Software\Beacon)
  • HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\LoggingBaseDirectory and HKLM\SOFTWARE\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\LoggingBaseDirectory (default location if not changed: %ProgramData%\Flexera Software\Compliance\Logging)

I would recommend stopping services and moving current original directory contents at the same time as changing these settings in the registry.

(Thanks @mrichardson  for the registry settings tips.)

(Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)
steven_donovan1
Active participant

Re: FNMS move all Logs, Readers, and intermediate data to a data drive.

Maybe there needs to be an enhancement request to include in the installer which Drive you want all pieces of the application to get installed.
0 Kudos
Highlighted
Flexera mrichardson
Flexera

Re: FNMS move all Logs, Readers, and intermediate data to a data drive.

Hi @steven_donovan1, There are a couple of enhancements for this, one of the main ones being FNMS-18451: Beacon ProgramData folder should be customizable at install time There are some registry settings which help: BaseDirectory string in [HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Beacon\CurrentVersion] refers to "C:\ProgramData\Flexera Software\Beacon" and changing this to another directory does work. LoggingBaseDirectory string in [HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion] refers to "C:\ProgramData\Flexera Software\Compliance\Logging" and changing this seems to work for all logs except CompliancReader. The reason it doesn't work for ComplianceReader is that executable is 64 bit so if you modify in the 64 bit registry, that should also work.
(Anything expressed here is my own view and not necessarily that of my employer, Flexera)
If the solution provided has helped, please mark it as such as this helps everyone to know what works.