Deploy software with group strategies, and save effort!
As a network administrator, is you often plagued by some software installations? For example, install software in a network environment! In the face of many users in the network environment, different requirements, the hardware configuration is different, the use of different computers, almost every day, have a variety of software installation requirements, do you feel tired, is it? The Group Policy Software Deployment in Windows 2000 can help us solve this trouble, so that these troublesome things make it easy, so that our major network administrators are completely free to get rid of software deployment, and save effort!
First, prepare to install the file package
The first step in implementing Group Policy Software Deployment is to get installation files with ZAP or MSI to extension.
The MSI installation file package is Microsoft specializes in software deployment. These two files Some software installations will be provided directly, and some software installations are not available. For software that does not provide MSI file we can create a packaging tool called WinInstall Le, By using it to generate an MSI file with software packages that do not provide MSI files to implement Group Policy Software deployment. WinInstallle Tool We can find from the Windows 2000 installation disc / valueadd / 3rdparty / mgmt directory, but the effect of the software is not ideal, recommend conditional friends using its upgraded version of WinInstall Le2003. The software interface is shown in Figure 1. Can be downloaded at http://www.ondemandsoftware.com/.
Figure 1 (Click to see the big picture)
Second, create software distribution points
The second step in implementing the deployment of Group Policy Software is to create a software distribution point on the network.
The software distribution point is the shared folder containing the MSI package file. That is, create a shared folder on the file server, below this folder, then create subdirectory you want to deploy software, then put the MSI package file and all required installation source files therein. The corresponding permissions are set to the shared folder, and the user has only the permissions of only read. If you are worried about the contents of some users illegally browse the distribution point, you can use the hidden shared folder, ie, add $ symbol after sharing name.
Third, create group strategic objects
Implementation Group Policy Software Deployment Step 3 is to create a corresponding group policy object.
Software deployment is set by group policies in AD, so we must create a group policy object (GPO) to distribute software packages, or modify a set of GPOs that already exist and add software deployment. When configuring GPO, we need to consider which people needed in the network are the same. Who needs the software that needs to be different, or what software needs, and then make a plan, which determines the creation of GPO, general In case we are created or modified on the container OU. The configuration is as follows:
1. Launch the "Active Directory User and Computer" management unit in the management tool. 2. In the console tree, right-click the OU you want to distribute, and then click the "Group Policy" tab, and then click New to create a group policy. 3. Type the group policy name you want to use, such as "Office2000 Distribution", and then carriage return. 4. Select the newly created Group Policy, click "Edit" below to enter the group policy editing state. 5. Setting the software to the user or the computer is set in the corresponding "User Configuration" or "Computer Configuration". Figure 2.
Figure 2 (Click to see the big picture)
Fourth, software deployment
After three steps above, we can set the software deployment itself.
Software deployment has two types, which are issued and assigned, see Figure 3. The difference between these two deployments is:
Figure 3 (Click to see the big picture)
4.1 The issued software deployment method
It should be noted that the issued method can only be deployed to the user, which is not deployed to the computer, that is, only the user configuration in the group policy can use this deployment method. The released software deployment method can guarantee: 1. When the user logs in to the computer, the software will not be installed automatically, only when the user double-click the file associated with the application, the software will automatically install. If we double-click a PPT document or Doc document, you will automatically install Office. 2. For software issued, users can install or delete in "Add / Delete" in the control panel, that is, the user can install it, or uninstall.
The benefit of this deployment method is that for some software that cannot be determined to use the user, it can be deployed in a release method, 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 then click Package. Select the MSI package file in Software Distribution Point in the Open Dialog box, and then click Open. 2. In the Select the deployment method, select "Issued".
4.2 Assignment Software Deployment Method
Assigned methods can deploy software to users and computers, that is, this deployment method can be used in the user policy and computer policies in Group Policy. This needs to be distinguished from the issuance method.
When we use this method to assign the software to the user:
1. Software is always available for users, regardless of which computer login from users, software will appear on the start menu or desktop, but the software is not installed, only if the user double-click the application icon or and application The software will be installed when the file is associated. 2. If the user deletes the installed software, the software will appear on the start menu or on the desktop when the user is logged in, and is activated when the user doubles the associated file.
The benefit of this deployment is that for some uncommon, some people must use the software we need to use, we don't have to install each computer, as long as the user is assigned, no matter which computer is operating, Can guarantee that the software to use is available.
Methods as below:
1. Right-click Software Installation in User Configuration, select New, and then click Package. Select the MSI package file in Software Distribution Point in the Open Dialog box, and then click Open. 2. In the selection deployment method, select "Assigned".
When we use this method to assign the software to the user:
1. For the assigned computer, the software is always available, no matter which user login can use the assigned software. 2. The software will not be installed by files, but is installed when the computer is started. 3. Users cannot delete software assigned installed, only administrators can.
The advantage of this deployment method is that some of the software to be used to be assigned to the computer, and the software assigned to the computer is available to all users.
The configuration method is assigned to the user, it is only to change the "user configuration" to "Computer Configuration".
Five changes deployed package options
After deploying a software with a group policy, you can modify the option to be deployed to accommodate our needs:
1. Click on the software installation to find the package to be deployed on the right, click Right click to select Properties, select Deployment in the Dialog box that appears, as shown in Figure 4.
Figure 4 (Click to see the big picture)
2. The deployment type has been introduced before, no longer repeated. The "Automatically Installing the Application By Extension" option in the deployment option can be installed through documentation to install the deployed software. This option is gray in Figure 4 because the deployment type is "assigned", which is selected by default. 3. "When this application is no longer within management scope, it is intended that the deployed software will be uninstalled when a user or computer is moved from the deployed OU. 4. "Do not display this package in the Add / Remove Programs" Control Panel "This option allows deployment software to prevent the user to operate the software in" Add / Remove Programs ". 5. The installation interface of "Basic Options" in the Installation User Interface Options is installed with the default value, "Maximum Option" allows the user to choose from during the installation process, you can enter information. Six-Deleted deployment package
To delete the issued or assigned package, you can right click on the package to select "All Tasks", "Delete". Select "Immediately from User and Computer Uninstall Software" or "Allow users to continue using software, but click OK.
W2000 software deployment can effectively meet the various needs of the software in the domain environment, and avoid the rushing of the network administrator to run. I hope everyone will try, exchange experience, and improve each other.