PSS MSI RFC Triage for Thursday October 27th, 2005
Second installment of general notes from the PSS MSI RFC Triage weekly conference call. For further context, see the first installment.
Let’s say I have a product and patch set RTM, QFE1, QFE2, SP1, where all upgrades target RTM. 0x922 was used as my ProductValidateFlags setting when generating the patches. If I install SP1 directly on RTM to bring my Installed version to 188.8.131.52 and then install QFE1 or QFE2, patch sequencing allows me to do this successfully.
I am assuming that it is the patch sequencer that first orders the patches logically and then makes the product version relationship comparison (Installed vs. Base) against a “virtual” Installed version (in this case RTM’s version).
For more details, refer to Windows Installer 3.0 Patch Sequencing Whitepaper Section named The Sequencing Process (page 15):
The Sequencing Process
The actions MSI takes when sequencing patches can be broken down into a few core steps.
- Create a framework of ProductVersion values.
As described earlier, minor update patches (which change the ProductVersion) create the framework for sequencing patches. The ProductVersion value that is created by each patch indicates the logical ordering of the patch relative to other minor update patches, so the first step in sequencing a set of patches is to examine these patches and sort them based on the ProductVersion value that each creates.
- Group patches by ProductVersion.
All remaining unsorted patches do not change the ProductVersion value, and are thus small-update (QFE) patches. Each QFE indicates in its targeting data the ProductVersion values that would allow the patch to apply. This targeting data provides the next level of sequencing for the patches. The QFEs are examined and grouped by their target ProductVersion. QFEs that apply to more than one ProductVersion value are assigned to the highest possible ProductVersion value targeted by the patch. Patches which apply to no ProductVersion values are discarded as inapplicable.
- Group by Family within each ProductVersion.
Once the patches have been grouped together by ProductVersion target, the MsiPatchSequence table is examined and patches are divided again into smaller groups by membership in each PatchFamily. In contrast to the grouping by ProductVersion, a patch may belong to multiple families and thus may be placed in several family groups.
- Sort each Family group.
Members of each family group are then sorted by their sequence value. Patches which belong to multiple families are sorted independently in each family.
- Combine Families in each ProductVersion.
The sorted families within a ProductVersion are then combined to generate a single ordered list for the ProductVersion value. Patches which belong to multiple families are cross-referenced to ensure that the final ordered list includes the sorting results from all families.
- Combine ProductVersion groups.
Next, the sorted groups for each ProductVersion value are combined with the minor update patches to create a single list of ordered patches which apply to the product.
- Eliminate superseded patches.
Finally, the relationships between patches are evaluated to determine whether one or more patches are no longer required. Patches which are no longer needed are marked as “superseded” and will no longer apply to the product, although they remain applied to the product in case they are needed in the future.
I Noticed in a log file a line beginning with MSI (a), I know MSI (c) is Client and MSI (s) is Server but what is MSI (a)?
The (a) is for CustomAction Server.
No. By definition, it is not a nested installation. It is not a nested installation because it's not a nested custom action and additionally it does not end up having a parent/child relationship after installation. Among the other issues your customer will face include:
- They will not be able to install silently as the UI Sequence does not run and therefore his 2nd MSI would not run.
- They will not able to install using Group Policy and the SMS may not work in all scenarios
Is there something akin to MSI 3.0's patch supersedence in MSI 2.0? We've got a requirement to operate on MSI 2.0.
No, not directly. The closest in MSI 2.0 is obsoleting patches set via the Revision Number summary information stream property. You can do this in the PCP file by using the ListOfPatchGUIDsToReplace property in the PatchWiz.dll Properties table.
Obsolescence Across Upgrade Types:
- 2.0-style small updates can obsolete patches using obsolescence.
- 2.0-style minor updates can do that as well but by changing the ProductVersion those previous patches should not be applicable anyway if default product validation flags are used.
- This could cause a problem so you should be sure to list all package codes for the replaced patches in the SP.
There was this great thread asking for an Orientation to Patching software under UAP/LUA.
Dig into http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=111453 to get some great context on Patching software under UAP/LUA.
Content credit also belongs to
- Carolyn, MSI Team Dev Lead. You can get other Carolyn insights about developing for Windows Installer from the Windows Installer Chat Archives
- Hem, MSI Team Dev. You can get other Hem insights about developing for Windows Installer from the Windows Installer Chat Archives
- Nitin, Phil, Alden, and Erik, Microsoft Support Team
- Heath, Microsoft Dev. You can get other Heath insights about developing for Windows Installer from Heath's blog
[Author: Robert Flaming]
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm.