Command Line

The windows command line invocation is used to register products in automatic installation process.
Make sure to Run As Administrator when running the Inlite Control Center (ICC)

On 32-bit Windows invoke:

"C:\Program Files\Common Files\Inlite\InliteControlCenter.exe" [options]

On 64-bit Windows invoke:

"C:\Program Files (x86)\Common Files\Inlite\InliteControlCenter.exe" [options]

Note:   If no options are specified ICC starts with the standard User Interface (UI mode).

Options

/c:"certificate"

Register a product using specified certificate. Several /c options can be used on a command line. The /c option can be combined with /f option.  
 

/f:"certificate-file.txt"

Register products with certificates stored in a text file.  File names and certificated values should be enclosed by double quotes.  If no folders are specified in the file name, file should be in the current directory.
Each line in the file should list one certificate string.  Text on each line after # is treated as comments.
This option can be used with a file with transfer certificates generated by clicking the Export button on Licensing Tab.


/l:"log-file.xml"

Results of the ICC transaction are stored in a default log file:  My Documents/ICC_Log.xml
The /l option allows to specify an additional custom log file.  The file must have a  .xml extension.
 If no folders are specified in the file name, file will be created in the current directory.
Note: A Log file is the only output of ICC command line invocation.   No command window output is produced.

/o

Forces the creation of a Request LAR file if online transaction fails (see Offline Licensing Action) conditions are detected.   If this option is omitted, ICC will generate an error in the log file.  If this option is included on command line, the log file will contain name of the Request LAR file.  To complete the transaction follow the instructions offline action procedure .

/s

Show the log file produced by ICC. The default application associated with XML extension is launched.

Exit codes

If no errors were detected during execution, the exit code is set to 0.   
If a Request LAR file was created (see /o option), then the exit code is set to 1.
If any error was detected, the exit code is set to 2 or higher.