Difference between revisions of "Active Directory/Documentation/Packaging Notes"

From WolfTech
Jump to navigation Jump to search
Line 1: Line 1:
 
==Upgrading Packages in Group Policy==
 
==Upgrading Packages in Group Policy==
 
* When upgrading a software package from another group policy, the new group policy must be ahead of the upgraded group policy in the link order (i.e. the new policy must have a higher precedence than the old policy).
 
* When upgrading a software package from another group policy, the new group policy must be ahead of the upgraded group policy in the link order (i.e. the new policy must have a higher precedence than the old policy).
 +
 +
==Custom Actions==
 +
 
* MSI Custom Actions do not support the WScript object model (see the example below).
 
* MSI Custom Actions do not support the WScript object model (see the example below).
  
*    Set WShell = WScript.CreateObject("WScript.Shell")
+
Set WShell = WScript.CreateObject("WScript.Shell")
  
 
instead of
 
instead of
  
 
  Set WShell = CreateObject("WScript.Shell")
 
  Set WShell = CreateObject("WScript.Shell")
* Blah
+
* To only run action during installation, add the following condition:
 +
NOT Installed
 +
* To only run action during uninstallation, add the following condition:
 +
Installed AND REMOVE="ALL"

Revision as of 11:32, 30 June 2006

Upgrading Packages in Group Policy

  • When upgrading a software package from another group policy, the new group policy must be ahead of the upgraded group policy in the link order (i.e. the new policy must have a higher precedence than the old policy).

Custom Actions

  • MSI Custom Actions do not support the WScript object model (see the example below).
Set WShell = WScript.CreateObject("WScript.Shell")

instead of

Set WShell = CreateObject("WScript.Shell")
  • To only run action during installation, add the following condition:
NOT Installed
  • To only run action during uninstallation, add the following condition:
Installed AND REMOVE="ALL"