Configuration File

All settings that can be modified by LAUNCHER Office administrator, are present into the launcher.ini file.

LAUNCHER Office uses launcher.ini file to know the configuration.

LAUNCHER Office Control Program indicates on the main Tab the exact path to launcher.ini file currently used.

When Launcher is started the first time (from the Start/LAUNCHER<x>/Launcher<x> menu), the launcher.ini file used is:

C:\Users\<user>\AppData\Roaming\launcher.ini.

It will be created here if changes to the Launcher configuration are made, and no launcher.ini file exists.

Otherwise in descending order of priority, launcher.ini is searched in the following locations:
- C:\Program Files (x86)\LAUNCHER<x> (or C:\Program Files\LAUNCHER<x>)
- C:\Windows
- C:\Users\<user>\AppData\Roaming

If the profile used to open the Windows session does not have the rights to modify the launcher.ini file, then the boxes of the configuration are grayed out: no modification possible. You have to run Launcher "as administrator" to change the configuration.

If Launcher is started as a Windows service, launcher.ini is searched in the following locations in descending order of priority:
- C:\Program Files (x86)\LAUNCHER<x> (or C:\Program Files\LAUNCHER<x>)
- C:\Windows

It will be created in "C:\Windows" if changes in the Launcher configuration are made, and no launcher.ini file exists.

If the configuration of a Launcher server is changed remotely with "Launcher<x> - Administration" (from the Start/LAUNCHER<x> menu), launcher.ini is searched in the following locations:
- C:\Program Files (x86)\LAUNCHER<x> (or C:\Program Files\LAUNCHER<x>)
- C:\Windows
- C:\Users\<user>\AppData\Roaming

Since the 2.6.1.22 version, it is possible to put the launcher.ini file as parameter.
Example: lncsrv.exe /ini "C:\temp\launcher.ini"

LAUNCHER Office Control Program modifies launcher.ini content but some options are available only if the file is directly modified.

Those options are as follow :

o Section [CONFIG]

• MaxThreads=n

Define the simultaneous connections maximum number. Default Value : 1 (see : Multiple connection mode.)

o Section [NETWORK]

• PortNumber=n

LAUNCHER Office TCP/IP port number. Default value : 6078

• LNCD_PortNumber=n

LAUNCHERD TCP/IP port number. Default value : 5681

• Admin_PortNumber=n

TCP/IP (UDP) port number used for LAUNCHER Office remote control. Default value : 6079

• Admin_PortNumber2=n

TCP/IP (UDP) port number used for LAUNCHER Office remote control. Default value : 6080

• Admin_PortNumber2End

TCP/IP (UDP) maximum port number used for LAUNCHER Office remote control. Default value : 6085. Used in case of multiple control on TSE server. This number can be increased to allow more simultaneous controls on the server.

• RetriesDelay

Delay in second between two connections tries to LAUNCHERD. Default Value : 30. Used in TSE mode only.

• AdminFromIPAllowxx=ipaddress

Indicates one or several IP addresses enabling LAUNCHER Office station control. This is useful in order to control a machine from different network mask. Several addresses or full network can be listed, in this case the prefix next to option must be incremented.

Example:
[NetWork]
AdminFromIpAllow1=192.206.160.5
AdminFromIpAllow2=192.206.161.255

In the above example, the '192.206.160.5' machine and all machines beginning from '192.206.161.' are allowed to remotely control this particular machine.

N.B. In any cases, all machines from the local network branch are allowed to operate remote control.
AdminToIpxx option can also be used on the control machine.

• AdminToIPxx=ipaddress

Indicates one or several IP machines addresses to be remotely controlled.
By default, LAUNCHER Office administrator can access to LAUNCHER Office instances located on the same network mask as the local machine. This option allows control of other machines if they accept connection from the machine where LAUNCHER Office controller run (see option 'AdminFromIPAllowxx').

Example :
[Network]
AdminToIP1=192.206.162.4
AdminToIP2=192.206.162.5

In the above example, we want to be able to control the 192.206.162.4 and 192.206.162.5 machines.
Notice: No generic address are allowed in this case (example 192.206.162.255)