Follow

Pass Options To The Agent Installer On The Command Line

The attached file is the confguration file required for passing arguments to the agent installer on the command line. This file can be used to manually configure any of the elements that are set up during install.

The content of the table below lists the elements that can be configured in the attached file for used during install.

Preference

Default

Description

flowserver.host

ft-server

DNS name of the API server

flowserver.protocol

https

The protocol that desktop client will use when talking to the API server

flowserver.port

443

The https port.

flowserver.path

/api/REST/v1.0/

It is part or URL that the desktop client will use when talking to the API server

flowadauthentication.enable

true

True means the agent uses AD authentication to log into the Flow Api Server. False means it does not use AD authentication to log into the Flow Server. Which means that either the flowproxy.enable field must be set to true (with accompanying flowproxy.server and possibly flowproxy.protocol values set), or the logintool must be used. to manually log in a user.

The FileTrekLoginTool.exe is not a standard executable delivered with Filetrek. This tool is used only in a POC or test environment when AD integration is not possible and the purpose is only to test Agent capabilities.

If you just set this value to false (without setting flowproxy.enable to true) the agent will not be able to log in to the Flow Server. Also note that if flowproxy.enable is true, this value is ignored completely (flowproxy login takes precendence over direct AD login).

There is no reason a user would ever set this to false except as a temporary mechanism to login with AD integration.

flowproxy.enable

false

Indicates whether or not the desktop agent should be using Active Directory authenticatio through an authentication proxy server (ADAG).

flowproxy.protocol

https

The protocol that the desktop client will use when talking to the ADAG.

flowproxy.host

ft-server

DNS name of the ADAG.

flowproxy.port

443

The ADAG port.

flowproxy.path

/flowproxy/REST/v1.0/

It is part or URL that the desktop client will use when talking to the ADAG.

agent.catchallwebuploads

true

Indicates whether or not the Web Upload Tracker will report on all websites or restrict itself to only those on our white list of tracked websites.

flowserver.urlroot

<derived field>

Obsolete.

This field overrides the combined values of <protocol>://<host>:<port><path>

 

note: On upgrade from versions 3.0 this field will have been set and will override the values of protocol, host, port and path. For any new deployments, versions 4.0 and later, do not set this parameter.

flowserver.prefsuffix

flowservice

Obsolete.

note: This field was used in earlier versions of the FileTrek Api Server. On an upgrade from 3.0 this value will be set and should be preserved as it was. If this value is changed or the key removed each file and volume the user visits will be treated as new.

 
unauthenticationloginmode false

set true to enable unauthenticated login.

flowadauthentication.enable must be set true.

 

Setting this value to true allows the agent to login without any authentication and will monitor any user logged into a machine with the agent installed - local users, machines/users who do not belong to the AD domain. It will also monitor logged in users when kerberos/Windows authentication fails for any reason.

note: If kerberos/windows authentication is bouncing then the logged in user will bouce as well.

 

When logged in as unauthenticated the user login will be identified as:
Mac: <local user>@<machine name>.<unique machine id>
example:

user1@window7.s-1-5-21-2034612207-653146127-2534476259-1111

windows: <local user>@<machine name>.<unique user id>
example:
user1@mac-mbp-2.ottawa.filetrek.com.2f27b291-1fd0-548f-9e82-51f841a22aea   

As an example, for setting the flowserver.host value, the following will need to be added to the file:

<?xml version="1.0" encoding="UTF-8"?>

<Configuration>
<ConfigParam name=“flow server.host” value=“XXXXXXXXXXXYOURVALUE” />
</Configuration>

If other values are to be configured on install, simply add more ConfigParam lines to the files with their associated values.

When running the installer from command line via MSIEXEC, the config file is passed in as a property called AUTOCONFIGFILE.  The syntax of the command shold look as follows:

msiexec /I FileTrekInstaller.msi /qn AUTOCONFIGFILE=c:/FileTrekAutoConfig.xml

If the config file isn't found then the installer would behave exactly as before.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk