How to deploy software using group policies?

Group PolicyFor the system administrator, making full use of group policies can make the system administrator get twice the result with half the effort. The following is a full example.

As a Network Manager, do you often suffer from software installation problems? For example, install software in a network environment! In the face of a large number of users with different requirements in the network environment, computers with different hardware configurations and different purposes have different requirements for software installation almost every day, are you feeling exhausted and at a loss? Group Policy in Windows 2000Software deploymentIt can help us solve this problem and make it easy to solve these troubles, so that our vast number of network administrators and friends can completely get rid of the troubles of software deployment, worry-free and effort-saving!

1. Prepare the installation package

The first step to implement Group Policy software deployment is to obtain the installation package with the ZAP or MSI extension.

The MSI installation package is developed by Microsoft for software deployment. These two files are provided directly by some software installation programs, and some software installation programs are not provided. We can use a packaging tool named WinINSTALL LE to create software that does not provide MSI files, by using this tool, you can package software that does not provide an MSI file to generate an MSI file to facilitate the deployment of Group Policy software. The WinINSTALLLE tool can be found in the \ VALUEADD \ 3RDPARTY \ MGMT directory of the Windows 2000 installation disc. However, the actual use of the software is not ideal, we recommend that qualified users use the upgraded version WinINSTALL LE2003. Software Interface 1. You can download the repository at http://www.ondemansoftware.com.

Figure 1

2. Create a software distribution point

The second step to implement Group Policy software deployment is to create a software distribution point on the network.

A software distribution point is a shared folder containing MSI package files. Create a shared folder on the file server. Under this folder, create a subdirectory to deploy the software, and then place the MSI package file and all required installation source files in it. Set the corresponding permissions for the shared folder so that the user has the read-only permission. If you are worried that some users may not view the content in the distribution point illegally, you can use hidden shared folders to add the $ symbol after the shared name.

3. Create a group policy object

The third step to implement Group Policy software deployment is to create the corresponding group policy object.

Software deployment depends on the Group Policy in AD. Therefore, we must create a group policy object (GPO) for distributing software packages ), or modify an existing GPO and add the software deployment settings. When configuring GPO, we need to consider analyzing who needs the same software in the network, who needs different software, or what departments need the software, and then make a plan, to determine the location where GPO is created, we generally create or modify GPO on the container OU. The configuration is as follows:

1. Start the "Active Directory users and computers" Management Unit in the management tool.

2. In the console tree, right-click the OU of the software to be distributed, click Properties, select the Group Policy tab, and click Create to create a group policy.

3. type the name of the Group Policy you want to use, for example, "Office2000 distribution", and press Enter.

4. Select the Group Policy you just created and click Edit to enter the Group Policy editing status.

5. Configure the software in "user configuration" or "Computer Configuration" based on whether the software is deployed to the user or computer. 2.

Figure 2

4. software deployment

After the above three steps, we can set the software deployment itself.

There are two types of software deployment: released and assigned, as shown in figure 3. The difference between the two deployment types is:

Figure 3

4.1 released software deployment Method

It should be noted that the released method can only be deployed to the user, not to the computer, that is, only the user configuration in the Group Policy can use this deployment method. The released software deployment method ensures that:

1. When a user logs on to the computer, the software is not automatically installed. The software is automatically installed only when the user double-clicks the file associated with the application. If you double-click a ppt or doc, the system automatically installs the OFFICE.

2. You can install or delete the released software in "Add/Delete" on the control panel, that is, you can install or uninstall the software on your own.

The advantage of this deployment method is that for some software that cannot be determined to use the user, you can deploy it as a release method, and whether the installation is determined by the user.

The configuration method is as follows:

1. Right-click "software installation" in "user configuration", select "new", and click "package ". In the open dialog box, select the MSI package file in the software delivery point and click open ".

2. Select "released" in the deployment method ".

4.2 assigned software deployment methods

The assigned method can deploy the software to the user and the computer. That is to say, both the user policy and the Computer Policy in the Group Policy can use this deployment method. This must be different from the release method.

When we use this method to assign software to users, we can ensure that:

1. the software is always available to users. No matter which computer the user logs on to, the software will appear on the Start Menu or desktop, but the software is not installed at this time, the software is installed only when you double-click an application icon or a file associated with the application.

2. If the user deletes the installed software, why does the software appear on the Start Menu or desktop when the user logs on to the system the next time and is activated and installed when the user double-clicks the associated file.

The advantage of such deployment is that we do not have to install software on every computer for some of the less commonly used software that some people must use, as long as they are assigned to the desired users, regardless of the computer on which the user operates, the software to be used is available.

The method is as follows:

1. Right-click "software installation" in "user configuration", select "new", and click "package ". In the open dialog box, select the MSI package file in the software delivery point and click open ".

2. In the select deployment method, select "assigned ".

When we use this method to assign software to users, we can ensure that:

1. The software is always available for the assigned computer, and the assigned software can be used no matter which user logs on.

2. The software will not be installed through file association, but will be installed when the computer starts.

3. You cannot delete the software to be installed. Only Administrators can delete the software.

The advantage of this deployment method is that you can assign some software that everyone needs to use to a computer, and the software that is assigned to be installed on the computer is available to all users.

The configuration method is as follows: Change "user configuration" to "Computer Configuration.

5. Change the software package options for deployment

After you deploy a software package with a group policy, you can modify the options of the software package to meet our needs:

1. Click software installation, find the software package to be deployed on the right, right-click and select Properties, select deployment in the displayed dialog box, and click 4.

Figure 4

2. The deployment type has been introduced before and will not be repeated. In the deployment option, the "activate automatically install application by extension" option can install the deployed software through document activation. In Figure 4, this option is dimmed because the deployment type is "assigned". In this deployment type, this option is selected by default.

3. "When this application is no longer under management, detach it" means that when a user or computer moves from the deployed OU, the deployed software will be detached.

4. "Do not show this package in the" Add/delete programs "Control Panel" this option can make the deployed software not appear in "Add/delete programs", to prevent users from performing operations on the software.

5. the installation interface of "basic options" in "installation User Interface Options" is installed by default. "Maximum options" allow users to select and enter information during the installation process.

6. Delete the deployed package

To delete a released or assigned package, right-click the package and select "all tasks" and "delete ". In the displayed dialog box, select "detach software from user and computer now" or "allow user to continue using software, but disable new installation", and click OK.

W2000 software deployment in a domain environment can effectively meet the various needs of users on the software, to avoid the network administrator to install the software and the rush. I hope you will try more, share your experiences, and improve your skills together.

Deploying software using group policies is easy and effort-saving. you can do it yourself. More knowledge about group policies remains to be learned and mastered by readers.