Stage 3: Installing the software on the workstations
You can install the software on the workstations in two main ways:
By having users pull the software from the server image to their workstations
By pushing the software from the server image to the workstations on the users behalf
Pulling the software to the workstations
Workstation users themselves can install (or pull) the software by using one of the following methods:
Browsing to the location of the server image, double-clicking Setup.exe, and following the instructions in the setup. This is the most common method for pulling the software.
Running a command line that installs the software from the server image. Typically, command lines are reserved for push-installation scenarios.
To install the software, workstation users require administrator-levelprivileges. To assign administrator-level access rights to workstationusers, Windows-based networks use Group Policy Objects (or GPOs).
Stored in a central network location, GPOs are used to automatically update the registry settings on each workstation when its user logs in tothe network.
If you want to give user administrator-level access rights (eithertemporarily or permanently), you may need to configure the GPOs for your network. Administrators can configure GPOs by using aGroup Policy Editor. To access the Group Policy Editor that installs with the Windows operating system, do the following:
- In Windows 7 or Windows XP, click Start > Run, and then run the file gpedit.msc.
- In Windows Vista, click the Start button, click All programs > Accessories > Run, and then run the file gpedit.msc.
To successfully install the software on the workstations, users require the following three system policies to be enabled:
- Computer Configuration\Administrative Templates\ Windows Components\Windows Installer\Always install with elevated privileges
- Computer Configuration\Administrative Templates\Windows Components\Windows Installer\ Enable user control over installs
- User Configuration\Administrative Templates\Windows Components\Windows Installer\Always install with elevated privileges
To allow the successful patching of the installed software, users who have limited access rights require the following system policy to be enabled:
- Computer Configuration\Administrative Templates\ Windows Components\Windows Installer\ Enable user to patch elevated products
Pushing the software to the workstations
If you prefer to install the software on behalf of the workstation users,you can push the software from the server image to the workstations.To do this, you use a command line in conjunction with one of the following:
A batch file a text file that can be scripted to run commands automatically. For help with using batch files, please visit the Microsoft website.
A Group Policy Object an item, stored in a central network location, that defines how the workstations are configured. For help with using Group Policy Objects, please refer to your Group Policy Software Development Kit.
A push technology a third-party tool that is specially designed for installing software automatically. For help with using any push technology, please visit the manufacturers website.
The process of creating a command line for installing the software involves the following:
Specifying the setup file on the server image (see page5)
Controlling the setup behavior by using command-line switches (see page6)
pre-configuring the software installed by using public properties (see page8)
Specifying a setup file in command lines
The main item to specify in your command line is the executable file that you want to use the install the software.
This file is Setup.exe, the executable file for the software setup.
Setup.exe is located on the server image, at the installation path that you chose when you created the server image.
The basic syntax for a Setup.exe command line is as follows:
If your server-image path contains spaces, you must place quotation marks around the entire Setup.exe component:
"\\server\path with spaces\Setup.exe"
Using command-line switches
To customize the behavior of the software setup, you can use a variety of command-line switches.
The syntax for a switch consists of a forward slash ( / ) immediately followed by a character or stringfor example, /q or
Some switches have parameters, which let you adjust the settings for the switch. (In fact, some switches let you use multiple parameters for the same switch.) To use a parameter, simply type the parameterimmediately after the switch (that is, without a space), unless otherwise noted. If you do not specify any parameters, the switch uses its default settings.
Switches are available for the following installation options:
Controlling the amount of user interface that is displayed (see page6)
Creating a log file (see page7)
Rebooting after installation (see page8)
Controlling the amount of user interface that is displayed
The /q switch can be used to restrict the amount of the user interface that appears during installation. You can use the switch to prevent users from entering their own registration information, to help enforce specific installation options, or even to perform silent installations (in which no user interface is visible during the setup).
You can specify one of the following parameters for the/q switch.
|n||The user does not see the user interface during the installation. Errors are recorded in a log file (see page7). This is the default parameter.|
|b||The user sees only a progress bar and a Cancel button. If the user pushes the Cancel button, the installation is rolled back.|
|r||The user sees a progress bar, along with a page containing information about the installation. The user can choose to cancel the installation.|
|f||The user sees the full user interface.|
Heres the command-line syntax: