Menu

#54 MSI query

v1.0_(example)
pending
nobody
5
2012-08-24
2012-01-16
No

When an update is published that is an MSI it adds default MSI query rules on the installable and installed pages. There are times that I want to use a different rule so I delete the default rules. After the update is created and published machines will report back that the product is already installed...it seems to report based on the MSI query. Some products when they release a new version (such as vmware tools) use the same MSI product code, but have different version numbers in the requstry. So when I publish an update from vmware that is an MSI without changing any rules it shows as installed. If I remove the default rules and instead add rules for registry string version the update seems to ignore that rule and instead use the MSI query rules that I removed.

Discussion

  • Bryan Dam

    Bryan Dam - 2012-01-17

    First, please post the XML for the update you revised. Second, if you publish a new update without MSI rules is it still detected? That is to say, does this only happen when you revise an update?

     
  • Adam Esslinger

    Adam Esslinger - 2012-01-17

    It happens with a new update and with a revised update. Below is the XML

    <sdp:softwaredistributionpackage xmlns="http://www.w3.org/2001/XMLSchema" xmlns:bar="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/BaseApplicabilityRules.xsd" xmlns:bt="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/BaseTypes.xsd" xmlns:cmd="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/Installers/CommandLineInstallation.xsd" xmlns:lar="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/LogicalApplicabilityRules.xsd" xmlns:msi="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/Installers/MsiInstallation.xsd" xmlns:msiar="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/MsiApplicabilityRules.xsd" xmlns:msp="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/Installers/MspInstallation.xsd" xmlns:sdp="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/SoftwareDistributionPackage.xsd" xmlns:uei="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/Installers/UpdateExeInstallation.xsd" xmlns:usp="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/UpdateServicesPackage.xsd" xmlns:drv="http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/Installers/WindowsDriver.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" schemaversion="1.2">
    <sdp:properties packageid="c80d8276-6c71-42d6-802a-8109c0c72736" creationdate="2012-01-17T12:07:47.012Z" vendorname="VMware, Inc." publicationstate="Published" cansourceberequired="false" updatetype="Software">
    <sdp:productname>VMware Tools</sdp:productname>
    </sdp:properties>
    <sdp:localizedproperties>
    <sdp:language>en</sdp:language>
    <sdp:title>VMware Tools</sdp:title>
    <sdp:description>VMware Tools</sdp:description>
    </sdp:localizedproperties>
    <sdp:applicationspecificdata>
    <sdp:isinstallable>
    <bar:regkeyexists key="HKEY_LOCAL_MACHINE" subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FE2F6A2C-196E-4210-9C04-2B1BC21F07EF}">
    </bar:regkeyexists></sdp:isinstallable>
    <sdp:isinstalled>
    <bar:regsztoversion key="HKEY_LOCAL_MACHINE" subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FE2F6A2C-196E-4210-9C04-2B1BC21F07EF}" value="DisplayVersion" comparison="GreaterThanOrEqualTo" data="8.3.12.8191">
    </bar:regsztoversion></sdp:isinstalled>
    <sdp:installableitem id="user-content-f5bfbefc-b438-421c-ac5b-11b4a7999aa8">
    <sdp:applicabilityrules>
    <sdp:isinstalled>
    <msiar:msiapplicationinstalled>
    </msiar:msiapplicationinstalled></sdp:isinstalled>
    <sdp:issuperseded>
    <msiar:msiapplicationsuperseded>
    </msiar:msiapplicationsuperseded></sdp:issuperseded>
    <sdp:isinstallable>
    <msiar:msiapplicationinstallable>
    </msiar:msiapplicationinstallable></sdp:isinstallable>
    <sdp:metadata>
    <msiar:msiapplicationmetadata>
    <msiar:productcode>{fe2f6a2c-196e-4210-9c04-2b1bc21f07ef}</msiar:productcode>
    </msiar:msiapplicationmetadata>
    </sdp:metadata>
    </sdp:applicabilityrules>
    <sdp:installproperties canrequestuserinput="false" requiresnetworkconnectivity="false" impact="Normal" rebootbehavior="CanRequestReboot">
    <sdp:uninstallproperties canrequestuserinput="false" requiresnetworkconnectivity="false" impact="Normal" rebootbehavior="CanRequestReboot">
    <msi:msiinstallerdata productcode="{fe2f6a2c-196e-4210-9c04-2b1bc21f07ef}" msifile="VMware Tools64.msi">
    </msi:msiinstallerdata></sdp:uninstallproperties></sdp:installproperties></sdp:installableitem>
    </sdp:applicationspecificdata></sdp:softwaredistributionpackage>

     
  • Adam Esslinger

    Adam Esslinger - 2012-01-17

    As you can see fro the XML it shows the MSI product code even though I removed the MSI rules and replaced them with Registry Version in SZ for the Installed rule and Registry key exists for the installable rule.

     
  • Bryan Dam

    Bryan Dam - 2012-01-17

    This isn't a bug per-se, you just need to remove the rules from the Installable Item level. Enable editing, remove the rules, and you should be fine.

    This goes back to a somewhat misguided decision I made early on to place rules in the package level rather than the installable item level.

     
  • Bryan Dam

    Bryan Dam - 2012-01-17

    This isn't a bug per-se, you just need to remove the rules from the Installable Item level. Enable editing, remove the rules, and you should be fine.

    This goes back to a somewhat misguided decision I made early on to place rules in the package level rather than the installable item level.

     

Log in to post a comment.

MongoDB Logo MongoDB