programming4us
programming4us
DESKTOP

Windows Server 2003 : Distributing Software with Group Policy (part 2) - Setting Windows Installer Package Properties

11/19/2013 8:31:54 PM

6. Adding Windows Installer Packages to the GPO and Selecting Package Deployment Method

In this step, you specify the software applications you want to deploy by adding Windows Installer packages to the GPO. Then you specify how the package is deployed (either assigned or published).

Note

The procedures in this step assume that you have chosen the Display The Deploy Software Dialog Box option (the default option that allows you to choose whether to assign or publish the application) in the software deployment properties for the GPO.


To modify or update the software application, any modifications must be associated with the Windows Installer package at deployment time rather than when the Windows Installer is actually using the package. Transform (.mst) and patch (.msp) files are applied to Windows Installer packages (which have the .msi extension) in an order specified by the administrator. This order must be determined before the application is assigned or published.

To add Windows Installer packages to the GPO and select a package deployment method, complete the following steps:

1.
Open the GPO console for the software deployment. In the Computer Configuration or User Configuration node, open Software Settings.

2.
Right-click the Software Installation node, click New, and then click Package.

3.
In the Open dialog box, in the File Name list, type the UNC path (\\servername\sharename) to the SDP for the Windows Installer packages (.msi files), and press ENTER. Select the .msi file, and then click Open.

Caution

Be sure to enter the UNC path to the SDP in the File Name list. If you merely browse and select the Windows Installer package to be added to the GPO, you have entered only the local path and clients will not be able to find the Windows Installer package.

4.
In the Deploy Software dialog box (shown in Figure 5), click one of the following options:

  • Published, which publishes the Windows Installer package to users without applying modifications to the package.

    Note

    If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the Published option is unavailable, because packages can only be assigned to computers, not published.

  • Assigned, which assigns the Windows Installer package to users or computers without applying modifications to the package.

  • Advanced, which sets properties for the Windows Installer package, including published or assigned options and modifications.

Figure 5. Deploy Software dialog box


5.
Click OK. If you selected Published or Assigned, the Windows Installer package has been successfully added to the GPO and appears in the details pane. If you selected Advanced, the Properties dialog box for the Windows Installer package opens, where you can set properties for the Windows Installer package, such as deployment options and modifications. Setting Windows Installer package properties is covered in the next section.

7. Setting Windows Installer Package Properties

In this step, you can fine-tune the deployment of each application by setting Windows Installer package properties in the Properties dialog box for the package. The Properties dialog box for the Windows Installer package contains the following tabs:

  • General tab You can change the default name of the package and designate a support URL. Users can select a support URL from the Add Or Remove Programs window to be directed to a support Web page. A support URL can contain helpful information such as frequently asked questions (FAQs) and can assist in reducing calls to a help desk or support team.

  • Deployment tab You can designate the deployment type, deployment options, and installation user interface options. In the Upgrades tab, you can deploy a package that upgrades an existing package.

  • Upgrades tab This tab does not appear for packages created from application files (.zap files).

  • Categories tab You can select the categories under which the application is listed for users in Add Or Remove Programs in Control Panel, making it easier for users to find the application. Categories you set generally pertain to published applications only, as assigned applications do not appear in Add Or Remove Programs.

  • Modifications You can indicate the modifications (transforms or patches) you want to apply to the package and specify the order in which the modifications apply to the package.

  • Security You can indicate permissions for the software installation. Permissions set for software installation pertain only to the package installation.

Note

Some settings in the Properties dialog box for the Windows Installer package can be set at the GPO level by editing the Software Installation Properties dialog box.


To set Windows Installer package properties, complete the following steps:

1.
Open the GPO console for the software deployment. In the Computer Configuration or User Configuration node, open Software Settings.

2.
Click the Software Installation node.

3.
In the details pane, right-click the package for which you want to set properties and then click Properties.

4.
In the General tab of the Properties dialog box for the package, shown in Figure 6, you can type a new name for the package in the Name box, if desired. You can also type a URL that provides user support in the URL box.

Figure 6. Properties dialog box for a package, General tab


5.
Click the Deployment tab. In the Deployment tab of the Properties dialog box for the package, shown in Figure 7, select one of the following options in the Deployment Type area:

  • Published, which allows users in the selected site, domain, or OU to install the application by using either Add Or Remove Programs in Control Panel or application installation by file activation. If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the Published option is unavailable, because packages can only be assigned to computers, not published.

  • Assigned, which allows users in the selected site, domain, or OU to receive this application the next time they log on (for assignment to users) or when the computer restarts (for assignment to computers).

Figure 7. Properties dialog box for a package, Deployment tab


6.
In the Deployment Options area, select one of the following options:

  • Auto-Install This Application By File Extension Activation, which uses the application precedence for the filename extension as determined in the File Extensions tab of the Software Installation Properties dialog box. If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the check box appears dimmed and selected, because by default the application is installed automatically.

  • Uninstall This Application When It Falls Out Of The Scope Of Management, which removes the application when users log on or computers start up in the event of relocation to a site, domain, or OU for which the application is not deployed.

  • Do Not Display This Package In The Add/Remove Programs Control Panel, which specifies that this package should not be displayed in Add Or Remove Programs in Control Panel.

  • Install This Application At Logon, which specifies that this package should be fully installed rather than just advertised by a shortcut. This option is available only for assigned applications. Avoid this option if the computer or user to which the application is assigned has a slow connection because the startup and logon procedures require a large amount of time when the application is first assigned.

7.
In the Installation User Interface Options area, select one of the following options:

  • Basic, which provides only a basic display to users during the install process.

  • Maximum, which provides all installation messages and screens to users during the package installation.

8.
Click Advanced to display the Advanced Deployment Options dialog box, shown in Figure 8. In the Advanced Deployment Options area, select any of the following check boxes:

  • Ignore Language When Deploying This Package, which specifies whether to deploy the package even if it is in a different language.

  • Make This 32-Bit X86 Application Available To Win64 Machines, which specifies whether the 32-bit program is assigned or published to 64-bit computers.

  • Include OLE Class And Product Information, which specifies whether to deploy information about COM components with the package.

Figure 8. Advanced Deployment Options dialog box


9.
Click OK.

10.
Click the Categories tab. In the Categories tab of the Properties dialog box for the package, shown in Figure 9, click the category under which you want to display this application to users from the Available Categories list, and then click Select.

Figure 9. Properties dialog box for a package, Categories tab


11.
Click the Modifications tab. In the Modifications tab, shown in Figure 10, do any of the following:

  • To add modifications, click Add. In the Open dialog box, browse to find the transform file (.mst) or patch file (.msp), and then click Open. You can add multiple modifications.

  • To remove modifications, select the modification you want to remove and then click Remove. Repeat until each unwanted modification has been removed.

  • To set the order of modifications, select a modification and then click Move Up or Move Down. Modifications are applied according to the order specified in the list.

Figure 10. Properties dialog box for a package, Modifications tab


Important

Do not click OK in the Modifications tab until you have finished configuring the modifications. When you click OK, the package is assigned or published immediately. If the modifications are not properly configured, you will have to uninstall the package or upgrade the package with a correctly configured version.

12.
Click the Security tab. In the Security tab of the Properties dialog box for the package, shown in Figure 11, click the security group on which to set permissions. Administrators who manage the application installation should have the Full Control permission set to Allow. Users who use the software assigned or published by the application should have the Read permission set to Allow.

Figure 11. Properties dialog box for a package, Security tab


13.
Click OK.
Other  
  •  Windows 7 : Tweaking Your WDS Server - Using WDS to Name Machines
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Deploying Your First Image
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Creating and Populating a Deployment Share (part 6) - Updating the Deployment Share
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Creating and Populating a Deployment Share (part 5) - Creating a Task Sequence
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Creating and Populating a Deployment Share (part 4) - Populating the Deployment Share - Importing Drivers, Importing Packages
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Creating and Populating a Deployment Share (part 3) - Populating the Deployment Share - Importing Applications
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Creating and Populating a Deployment Share (part 2) - Populating the Deployment Share - Importing Operating Systems
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Creating and Populating a Deployment Share (part 1)
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Installing MDT 2010 Update 1
  •  Windows 7 : Microsoft Deployment Toolkit 2010 - Setting Up Your Deployment Server
  •  
    video
     
    Video tutorials
    - How To Install Windows 8

    - How To Install Windows Server 2012

    - How To Install Windows Server 2012 On VirtualBox

    - How To Disable Windows 8 Metro UI

    - How To Install Windows Store Apps From Windows 8 Classic Desktop

    - How To Disable Windows Update in Windows 8

    - How To Disable Windows 8 Metro UI

    - How To Add Widgets To Windows 8 Lock Screen

    - How to create your first Swimlane Diagram or Cross-Functional Flowchart Diagram by using Microsoft Visio 2010
    programming4us programming4us
    programming4us
     
     
    programming4us