Using Login Scripts

In a Windows NT or AD domain, you can write login scripts that check for the presence of the BigFix client. If it is missing, the script can copy the Client installer from a remote location to the local drive.

With your login scripts, you can run the BigFix client installer setup.exe, which is an MSI-based setup created with InstallShield. The setup.exe file can be run silently as described in The /v"..." part of the command line contains the options and properties that are passed to the underlying MSI engine. A list of standard command line options for the Windows Installer is available at

To install the Client silently while writing a log to the directory C:\, run a command of the form:

setup.exe /s /v"/L*vx! \"C:\ClientInstallLog.txt\" SETUPEXE=1 REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn"

To log some more information specific to the InstallShield .exe wrapper:

setup.exe /s /debuglog"C:\ClientInstallLogIS.txt" /v"/L*vx! \"C:\ClientInstallLog.txt\" SETUPEXE=1 REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn"

To change the default installation location, the appropriate form of the command is:

setup.exe /s /v"/L*vx! \"C:\ClientInstallLog.txt\" INSTALLDIR=\"PathToInstallationFolder\" SETUPEXE=1 REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn"

Where "PathToInstallationFolder" is the full windows path to the folder where the Client is to be installed.

Note: The Windows user running setup.exe must have Administrative privileges on the computer, must be able to write to the folder that contains the "setup.exe" and to the chosen log location, otherwise the installation might fail and create no log.