To run an installer in silent mode, specify the /silent switch on the command line. We highly recommend that you specify a file that will receive a report, for example:
NiniteInstaller.exe /silent report.txt
Without this there will be no indication of failure or debugging information, apart from the return code of the installer.
You can also specify . as the report file to output the report on stdout (standard output):
NiniteInstaller.exe /silent .
That will work great in batch (.bat) files with Ninite installers, but if you're working interactively on the command-line you'll probably want to wait for the Ninite Installer to complete with something like:
cmd /c NiniteInstaller.exe /silent .
By default, Ninite skips the installation of applications that are already up to date on the system. The /repair switch can be used to force the re-installation of applications that are up to date. Here's an example:
NiniteInstaller.exe /silent report.txt /repair
If you are behind a proxy server that needs a user name and password, use the following switch in combination with the silent switch:
/proxyauth <user> <password>
When run on a single machine the report will be a text file. With remote mode it is in comma separated value (CSV) format and can be viewed in Excel.
The first line is the overall status, which can be:
This is followed by per-app status information in the format "App Name : [status]"
In audit mode the status can be:
In install/update mode, there are many different potential messages. It is impossible to list them all because some of them can contain error codes from the operating system or from the installer programs.
For example, the line:
Chrome : Install failed - Could not verify installation (1), 1 – 2271
Means Ninite failed to install Chrome, or at least it could not find it after running the installer.
To summarize, in audit mode, the message is always one of the five listed messages. In install mode, there are many different potential messages, so it's probably best to use the following approach: