Upgrading Applications Deployed with Group Policy
Several events in the life cycle of the software can trigger an upgrade, including the following:
The original developer of the software might release a new version with new and
improved features.
The organization might choose to use a different vendor’s application.
Upgrades typically involve major changes to the software and normally  have new version numbers. Usually a substantial number of files change  for an upgrade. To establish the procedure to upgrade an existing  application to the current release, you must first create a Windows  Installer package that contains the upgrade and then configure the  upgrade in the Upgrades tab in the Properties dialog box for the  package.
Note   The Upgrades tab is not available for packages created from application files (.zap files).
To upgrade applications deployed with Group Policy, complete the following steps:
1.Open the Group Policy Object Editor console. In the Computer Configuration or User Configuration node, open Software Settings.
2.Click the Software Installation node.
3.Create a new Windows Installer package that contains the upgrade. Assign or publish this new package.
4.In the details pane, right-click the Windows Installer package that  will function as the upgrade (not the package to be upgraded), and then  click Properties.
In the Upgrades tab of the Properties dialog box for the upgrade package, shown in Figure 12-13, click Add.
6. In the Add Upgrade Package dialog box, shown in plus benefits, select one of the following:
Current Group Policy Object (GPO), if you want to upgrade a package in the current GPO.
A Specific GPO, if you want to upgrade a package in another GPO. Then  click Browse, select the GPO you want, and then in the Browse For A  Group Policy Object dialog box, click OK.
A list of all the packages assigned or published within the selected GPO  appears in the Package To Upgrade list. Depending on the GPO, this list  can have zero or more entries.
7.Select the package you want to upgrade in the Package To Upgrade list.
8.Select one of the following:
Uninstall The Existing Package, Then Install The Upgrade Package, to  remove the existing package before the upgrade is installed. This option  is used if you want to replace an application with a completely  different one (perhaps from a different vendor).
Package Can Upgrade Over The Existing Package, to install the upgrade  with-out removing the previous version. This option is used if you want  to install a newer version of the same product while retaining the  user’s application preferences, document type associations, and so on.
In the Upgrades tab in the Properties dialog box for the package, select  the Required Upgrade For Existing Packages check box if you want the  upgrade to be mandatory, and then click OK. If this is an upgrade under  the Computer Configuration node of the Group Policy Object Editor  console, the check box appears dimmed and selected, because packages can  only be assigned to computers, not published.
Note If the Required Upgrade For Existing comptia network Packages check box is not selected, users have the option of applying  the upgrade, which could cause application version variances within an  organization.

 Processing your request, Please wait....
 Processing your request, Please wait....
	