Local installation scenario

You have a new Laser Printer yyyy. 50 users need the printer software installed on their computers. Most of the users are comfortable launching a batch file from an e-mail client.

  1. Using a text editor, create a script. For a sample script, see Creating install scripts.

  2. Copy the script to your LAN drive in a folder created to house install scripts and the log files they generate.

    J:\source\scripts\yyyy.isf
  3. Create an image of the extracted Package Builder contents.

    J:\source\driverscd
  4. Create a batch file to use your script as a guide for running Script Install. For more information, see Using install scripts with batch files.

  5. Send an e-mail to your 50 users with the batch file attached.

  6. Occasionally check the output file yyyy.log. It accumulates time-stamped summary of installations.

    Note: Local installations only work when the user accounts running the local installation have administrative privileges.

Suppose your users are not comfortable using their computers for unfamiliar tasks. Rather than having your users launch a batch file themselves from an e-mail client, you can customize their network login script to launch Script Install for them when they log in to their accounts.

The following lines, if added to a network login script, automatically runs Script Install for each user. This is only true if Script Install is not yet running.

if exist C:\dunscrpt.out goto continue
J:\source\driverscd\install\x86\InstallGui.exe 
/I:J:\source\scripts\yyyy.isf
/O:J:\source\scripts\yyyy.log
Note: You may need to use the x64 path instead of x86 depending on your system requirements.
>C:\dunscrpt.out echo Installation already attempted on this workstation
:continue