flxconfig Command Line

IT Asset Management (Cloud)

The agent configuration component is responsible for checking and applying agent configuration on the managed device.

The agent configuration component retrieves a single json configuration file from the appropriate inventory beacon, then processes the file and applies any settings contained in the file.

During adoption, the agent configuration component attempts to retrieve agent configuration and its operating schedule from the bootstrapping inventory beacon (which has collected these from the central application server).

The agent configuration component (flxconfig) can ordinarily be run without any command line parameters to check for and retrieve agent configuration. This will use the last configured list of failover inventory beacon server addresses, and will sort the servers according to the current network selector SelectorAlgorithm setting.

Synopsis

flxconfig [options...]

Options:

--download-server server

Type	Value	Description
--download-server	server	An inventory beacon server URL to retrieve agent configuration from. This URL can include or omit the ManageSoftDL virtual path. Examples: flxconfig --download-server http://beacon-url or flxconfig --download-server http://beacon-url/ManageSoftDL Note that using this option disables the Net Selector algorithms and downloads only from the specified server.

--dry-run true

Type	Value	Description
--dry-run	true (Default is false	This option will log to the agent_configuration.log file but not actually install or change anything in the system. The following log entry will appear in the logs: “Agent configuration is currently running in dry-run mode; no changes will be made to the local agent.” No agent installation changes or upgrades will be processed. InventorySettings.xml will not be requested or processed. No schedule from the configuration will be installed to the local system. No net selector algorithms will be processed or applied. Example: flxconfig --dry-run true

--disable-inventorysettings true

Type	Value	Description
--disable-inventorysettings	true (Default is false	This option disables the processing and application of inventory settings or encryption settings from the downloaded configuration. Example: flxconfig --disable-inventorysettings true

--disable-schedule true

Type	Value	Description
--disable-schedule	true (Default is false	This option disables the processing and application of any schedule settings from the downloaded configuration. Example: flxconfig --disable-schedule true

--disable-failover true

Type	Value	Description
--disable-failover	true (Default is false	This option disables the processing and application of failover settings (Download and Upload settings) from the downloaded configuration. Example: flxconfig --disable-failover true

--disable-upgrade true

Type	Value	Description
--disable-upgrade	true (Default is false	This option disables the processing of agent upgrade packages from the downloaded configuration. Example: flxconfig --disable-upgrade true

--disable-netselector true

Type	Value	Description
--disable-netselector	true (Default is false	This option disables the processing of net selector algorithms from the downloaded configuration. Example: flxconfig --disable-netselector true

--local-config-file filename

Type	Value	Description
--local-config-file	filename (Default is empty or not set)	This option will use the specified local json configuration file instead of retrieving the configuration from a beacon. Example: flxconfig --local-config-file agent_config.json

-o <PREFERENCE>=<VALUE>

Type	Value	Description
-o <PREFERENCE>=<VALUE>		This option is used to set preferences for flxconfig. Example: -o LogFileSize=4000000

Troubleshooting

The configuration component logs to the path specified by the LogFile setting, typically %temp%\ManageSoft\agent_configuration.log on Windows and /var/opt/managesoft/log/agent_configuration.log on Unix platforms. The log can be used to determine success or failure of flxconfig, including any information on what settings were applied from configuration and what files were downloaded.

Additional logging can be obtained by enabling the +Configuration tracing category in etcp.trace. The information in Agent Third-Party Deployment: Troubleshooting Inventory can be applied to enabling tracing for flxconfig, using +Configuration to enable agent configuration specific tracing.