This step-by-step article describes how to use Group Policy
to automatically distribute programs to client computers or users. You can use
Group Policy to distribute computer programs by using the following methods:
Assigning Software You can assign a program distribution to users or computers.
If you assign the program to a user, it is installed when the user logs on to
the computer. When the user first runs the program, the installation is
finalized. If you assign the program to a computer, it is installed when the
computer starts, and it is available to all users who log on to the computer.
When a user first runs the program, the installation is finalized.
Publishing Software You can publish a program distribution to users. When the
user logs on to the computer, the published program is displayed in the
Add or Remove Programs dialog box, and it can be installed
from there.
Note Windows Server 2003 Group Policy automated-program installation
requires client computers that are running Microsoft Windows 2000 or
later.
To publish or assign a computer program, you must create a
distribution point on the publishing server:
Log on to the server computer as an
administrator.
Create a shared network folder where you will put the
Microsoft Windows Installer package (.msi file) that you want to distribute.
Set permissions on the share to allow access to the
distribution package.
Copy or install the package to the distribution point. For
example, to distribute Microsoft Office XP, run the administrative installation
(setup.exe /a) to copy the files to the distribution
point.
To create a Group Policy object (GPO) to use to distribute the
software package:
Start the Active Directory Users and Computers snap-in. To
do this, click Start, point to Administrative
Tools, and then click Active Directory Users and
Computers.
In the console tree, right-click your domain, and then
click Properties.
Click the Group Policy tab, and then click
New.
Type a name for this new policy (for example,
Office XP distribution), and then press
ENTER.
Click Properties, and then click the
Security tab.
Click to clear the Apply Group Policy
check box for the security groups that you want to prevent from having this
policy applied.
Click to select the Apply Group Policy
check box for the groups that you want this policy to apply to.
To assign a program to computers that are running Windows Server
2003, Windows 2000, or Microsoft Windows XP Professional, or to users who are
logging on to one of these workstations:
Start the Active Directory Users and Computers snap-in. To
do this, click Start, point to Administrative
Tools, and then click Active Directory Users and
Computers.
In the console tree, right-click your domain, and then
click Properties.
Click the Group Policy tab, select the
group policy object that you want, and then click
Edit.
Under Computer Configuration, expand
Software Settings.
Right-click Software installation, point
to New, and then click Package.
In the Open dialog box, type the full
Universal Naming Convention (UNC) path of the shared installer package that you
want. For example, \\file
server\share\file
name.msi.
Important Do not use the Browse button to access the location. Make sure that you use the UNC
path to the shared installer package.
Click Open.
Click Assigned, and then click
OK. The package is listed in the right pane of the
Group Policy window.
Close the Group Policy snap-in, click
OK, and then quit the Active Directory Users and Computers
snap-in.
When the client computer starts, the managed software
package is automatically installed.
To publish a package to computer users and make it available for
installation from the Add or Remove Programs tool in
Control Panel:
Start the Active Directory Users and Computers snap-in. To
do this, click Start, point to Administrative
Tools, and then click Active Directory Users and
Computers.
In the console tree, right-click your domain, and then
click Properties.
Click the Group Policy tab, click the
group policy object that you want, and then click
Edit.
Under User Configuration, expand
Software Settings.
Right-click Software installation, point
to New, and then click Package.
In the Open dialog box, type the full UNC
path of the shared installer package that you want. For example,
\\file
server\share\file
name.msi.
Important Do not use the Browse button to access the location. Make sure that you use the UNC
path to the shared installer package.
Click Open.
Click Publish, and then click
OK.
The package is listed in the right pane of the
Group Policy window.
Close the Group Policy snap-in, click OK,
and then quit the Active Directory Users and Computers snap-in.
Test the package:
Note Because there are several versions of Microsoft Windows, the
following steps may be different on your computer. If they are, see your
product documentation to complete these steps.
Log on to a workstation that is running Windows 2000
Professional or Windows XP Professional by using an account that you published
the package to.
In Windows XP, click Start, and then
click Control Panel.
Double-click Add or Remove Programs,
and then click Add New Programs.
In the Add programs from your network
list, click the program that you published, and then click
Add. The program is installed.
In some cases you may want to redeploy a software package. For
example, if you upgrade or modify the package. To redeploy a package:
Start the Active Directory Users and Computers snap-in. To
do this, click Start, point to Administrative
Tools, and then click Active Directory Users and
Computers.
In the console tree, right-click your domain, and then
click Properties.
Click the Group Policy tab, click the
Group Policy object that you used to deploy the package, and then click
Edit.
Expand the Software Settings container
that contains the software installation item that you used to deploy the
package.
Click the software installation container that contains the
package.
In the right pane of the Group Policy
window, right-click the program, point to All Tasks, and then
click Redeploy application. You will receive the following
message:
Redeploying this application will reinstall
the application everywhere it is already installed. Do you want to
continue?
Click Yes.
Quit the Group Policy snap-in, click OK,
and then quit the Active Directory Users and Computers snap-in.
Start the Active Directory Users and Computers snap-in. To
do this, click Start, point to Administrative
Tools, and then click Active Directory Users and
Computers.
In the console tree, right-click your domain, and then
click Properties.
Click the Group Policy tab, click the
Group Policy object that you used to deploy the package, and then click
Edit.
Expand the Software Settings container
that contains the software installation item that you used to deploy the
package.
Click the software installation container that contains the
package.
In the right pane of the Group Policy
window, right-click the program, point to All Tasks, and then
click Remove.
Do one of the following:
Click Immediately uninstall the software from
users and computers, and then click OK.
Click Allow users to continue to use the
software but prevent new installations, and then click
OK.
Quit the Group Policy snap-in, click OK,
and then quit the Active Directory Users and Computers snap-in.
Published Packages Are Displayed on a Client Computer After You Use a Group Policy to Remove Them
This situation can occur when a user has installed the program
but has not used it. When the user first starts the published program, the
installation is finalized. Group Policy then removes the
program.
For more information about how to use a Group Policy to deploy software, click the following article numbers to view the articles in the Microsoft Knowledge Base:
304953
(http://support.microsoft.com/kb/304953/
)
How to deploy Office XP over a network
302430
(http://support.microsoft.com/kb/302430/
)
How to assign software to a specific group by using Group Policy