Difference between revisions of "Active Directory/Documentation/Packaging Notes"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
==Custom Actions== | ==Custom Actions== | ||
| + | * For script based actions, I usually choose *Stored in custom action*. | ||
| + | * For most actions, it makes sense to sequence them in the *Install Exec Sequence* after all the other 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). | ||
Revision as of 10:36, 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
- For script based actions, I usually choose *Stored in custom action*.
- For most actions, it makes sense to sequence them in the *Install Exec Sequence* after all the other 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"