Microsoft® Active Directory® technology provides the capability for software to be remotely installed from a server distribution point to client computers. The client computers must be members of an organizational unit (OU) in the Active Directory. Software deployment is controlled by configuring the software installation policy of the group policy object (GPO) associated with that OU. The software installation occurs automatically at boot time; no user intervention is required.
Disclaimer
The description of methods presented here is provided to aid those looking for a straight forward, Microsoft supported means for deployment of software over a Local Area Network. If the Microsoft Group Policy based mechanism does not provide sufficient control or features for the size or complexity of your network environment, we recommend that you consider more advanced Microsoft solutions, or other third party solutions.
Prerequisites
- Active Directory must be installed and configured.
- Client computers must have Microsoft Installer (MSI) version 3.0 or newer installed.
Configure for group policies
- Create a Distribution Point.
- Assign the application to client computers.
- Verify the installation.
Note Consult Microsoft Knowledge Base Article #816102 for more details, including information on how to redeploy or remove a package.
Create a distribution point
A distribution point is a shared network location containing the package(s) to install.
Create a distribution list
- Log on to the appointed server as Administrator.
- Create a shared network folder.
- Grant permissions as appropriate. Permission to modify the contents of this folder is typically granted to an administrator or select group of users. All other users are restricted to read access.
- Copy the .msi files for the package(s) to be deployed into this folder.
Assign a package to client computers
The Software Installation section of the group policy object specifies the software packages to be deployed.
Assign a package for deployment
- On the Windows menu on the server, click .
- Browse to the organizational unit (OU) in the Active Directory tree, right-click, and click . The Properties dialog box for the OU selected displays.
Note For the Group Policy Object to take effect, the client computer objects must be members of the OU selected.
- On the Group Policy tab, click . Enter a name for the GPO (for example, Alias Computer Assigned Installation). The GPO is created and added to the Group Policy Object Links list.
- In the Group Policy Object Links list, click the GPO you created, then click.
- In the Group Policy Object Editor, left pane, under computer Configuration, click the plus sign (+) next to the Software Settings folder to expand it.
- Under Software Settings, right-click Software Installation, then click .
- Enter the UNC path to the desired package located in the distribution point created in the previous section, then click . For example, \\server\share\Alias.msi
Note Do not browse to the network location. Enter the UNC path into the File name box.
- Select , and click . Wait until an entry for the package displays in the right pane of the Group Policy window.
- Repeat steps 7 and 8 for all packages to be deployed.
- Close the Group Policy window and any other open Active Directory windows.
The package is now assigned to all computers that are members of the OU for which the GPO was created. The next time a computer in the OU restarts, the program installs and is available for all users of the computer.
Note Windows® XP is shipped with Fast Logon Optimization enabled. Due to this feature, two reboots are required before the software is installed. Microsoft Knowledge Base Article #305293 describes the Fast Logon Optimization feature, along with instructions on how to disable it.
Test and verify the deployment
When a computer restarts, the operating system displays messages about group policy, usually before or after the Windows Login dialog box displays. These messages include the following:
- Windows starting up.
- Applying computer settings.
- Installing managed software.
- Applying software installation settings.
- Loading your personal settings.
- Applying your personal settings.
To verify that the package is correctly assigned to a computer, restart a computer that is in the OU for which the GPO was created. The program installs during the boot sequence, before the login prompt displays. After login, the application is located in the Programs menu in the same location as if it was installed locally.
Note If problems arise, an entry is logged in the system Event Viewer, under Applications.
References
- Microsoft Knowledge Base Article #816102: How to use Group Policy to Remotely Install Software in Windows Server 2003.
- Microsoft Knowledge Base Article #305293: Description of Windows XP Professional Fast Logon Optimization Feature.