Difference between revisions of "Active Directory/Documentation/Packaging Notes"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
==Converting To Cabs== | ==Converting To Cabs== | ||
| + | |||
| + | *Use WiMakCab.vbs script | ||
| + | cscript WiMakCab.vbs <msi> <cab name> /C /U /S | ||
| + | |||
| + | *Notes: | ||
| + | |||
[http://windowssdk.msdn.microsoft.com/en-us/library/ms710799.aspx Word Count Summary] = 2 | [http://windowssdk.msdn.microsoft.com/en-us/library/ms710799.aspx Word Count Summary] = 2 | ||
Revision as of 17:05, 8 March 2007
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"
Converting To Cabs
- Use WiMakCab.vbs script
cscript WiMakCab.vbs <msi> <cab name> /C /U /S
- Notes:
File Table Attributes = 16384
cabarc -r N data.cab *