How to change the MSI file location in the Software Deployment GPO (Mutilple UNC paths for same package)

Article translations Article translations
Close Close
Article ID: 2395088 - View products that this article applies to.
Expand all | Collapse all

SUMMARY

Scenario: 1

===========

You create a GPO for deploying an MSI Package, and need to change the location of the MSI package (UNC path). You need to create a new GPO for the package and this new GPO would be applied to all the machines in the OU, which will further end up redeploying the same package on the machines already having the software (installed from the previous GPO).

Scenario: 2

===========

You want to provide multiple paths for the same installation package and push it through viaGPO, but the GUI only gives you one option to select the package location.

MORE INFORMATION

You can work around this using the following methods:

========================

1) Open the GPO the Package Object it is defined in and right-click the Package Object and select Properties.

2) Click the Deployment tab, then click the Advanced button. Note the Script Name location. You will need the CLSID (long alphanumeric number) directly after the \Policies notation.

3) Open the ADSI editor, connect to your domain and navigate to the System\Policies tree on the left side of the window. Locate the CLSID you noted above.

4) Expand this CLSID tree and then expand the following trees to get to the actual defined Package Object: CN=Machine \ CN=Class Store \ CN=Packages.

5) Right click on the Package Object and select Properties. Navigate to the Optional property ‘msiFileList’. This property contains the UNC path of the location of the MSI Installer file. Edit this value to represent the new UNC path.

NOTE: It is possible to have multiple UNC paths defined for a Package Object, starting with 0:, then 1: and so on. If you are changing the UNC path, type in the new UNC path, prefixed with 0: and click the Add button. Select the old UNC path and click the Remove button.

6) The UNC path for the Package Object has now been updated to reflect the new UNC path.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2395088 - Last Review: September 1, 2010 - Revision: 2.0
APPLIES TO
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Keywords: 
KB2395088

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com