Using Login Scripts

In an NT or AD domain, you can write login scripts that check for the presence of the client. When the user logs in and finds the Client missing, it can automatically access the Client installer from a specified location on a global file share.

If you plan to add new computers to your network from time-to-time, this approach ensures that the Server discovers and manages new machines automatically. However, in some networks using Windows 2000 or XP, users must log in with Administrator privileges for this technique to work.

The login scripts pass arguments to the Windows Installer- based setup. For more information about command line options for setup.exe, see the InstallShield’s support website at http://kb.flexerasoftware.com/doc/Helpnet/isxhelp12/IHelpSetup_EXECmdLine.htm. Here are some examples of command line switches for the Client installer that can be used in a login script:

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

    setup.exe /s /v/l*voicewarmup \"C:\besclientinstall.log\" SETUPEXE=1 /qn?

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

    setup.exe /s /v/l*voicewarmup \"C:\besclientinstall.log\" INSTALLDIR=\<InstallPath>\ SETUPEXE=1 /qn?

    Where <InstallPath> 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 and must be able to write a log file to the same folder that contains the “setup.exe" file, otherwise the installation fails and a log file is not created.