Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - JC-WH

Pages: [1]
Hi.  We've recently started trying to push updated versions of MBAM, but the links used for v4.x all seem to be dead.  The publishing service gets a 404 every time it runs, and looks like it's trying to pull a version from back in February (component version 1173).  I guess MB moves or removes old version installers.

There've been few component version releases since February, (two in March and one in April - but none of those appear to have made it into the PatchMyPC catalog.

The current version as of this morning is component version 1251 and lives at

Ahh, In SCUP, did you happen to open the Jabber update, and click the browse button, then browse to your download?
It seems the rules we had were overwritten, and browsing to the MSI file in the edit wizard will do that...

Yep.  We had added the version number to the filename to try to avoid confusion, since Cisco doesn't, and we already had an older version deployed that was using an un-renamed old msi.

Didn't realize that changing the filename reference would cause SCUP to blow out other, completely unrelated metadata.  WTG, Microsoft :\

Thanks for your help on this, Andrew Jimenez!

Ahhh, cool, thanks!

Code: [Select]
<sdp:SoftwareDistributionPackage xmlns="" xmlns:bar="" xmlns:bt="" xmlns:cmd="" xmlns:lar="" xmlns:msi="" xmlns:msiar="" xmlns:msp="" xmlns:sdp="" xmlns:uei="" xmlns:usp="" xmlns:drv="" xmlns:xsi="" SchemaVersion="1.2">
  <sdp:Properties PackageID="5eef58f4-8326-4b59-af7c-77c2246f485f" CreationDate="2021-03-30T19:38:35.021Z" VendorName="Patch My PC" PublicationState="Expired" CanSourceBeRequired="false" UpdateType="Software">
    <sdp:ProductName>SCUP Updates</sdp:ProductName>
    <sdp:Title>Cisco Jabber</sdp:Title>
    <sdp:Description>This release contains bug fixes, enhancements &amp; security fixes. See "More info URL/Help document" for the full release notes details.</sdp:Description>
  <sdp:UpdateSpecificData MsrcSeverity="Critical" UpdateClassification="Security Updates">
  <sdp:InstallableItem ID="cb683082-119b-49c4-a0df-a8598c3c1ec6">
        <msiar:MsiApplicationInstalled />
        <msiar:MsiApplicationSuperseded />
        <msiar:MsiApplicationInstallable />
    <sdp:InstallProperties CanRequestUserInput="false" RequiresNetworkConnectivity="false" Impact="Normal" RebootBehavior="CanRequestReboot" />
    <msi:MsiInstallerData ProductCode="{00000000-0000-0000-0000-000000000000}" MsiFile="CiscoJabberSetup12.9.5.msi" CommandLine="REBOOT=ReallySuppress" />
    <sdp:OriginFile Digest="4mSG6MRBaMKynmvNp6Xc4rD3z9g=" FileName="CiscoJabberSetup12.9.5.msi" Size="159169536" Modified="2021-03-29T14:38:37.003Z" OriginUri="\\LocalHost\PatchMyPCRepository\CiscoJabberSetup12.9.5.msi"></sdp:OriginFile>

Nope.  That looks like it's referencing the PatchMyPC publishing tool, I'm guessing?  We're using SCUP, and the "Installable Rules" just shows "WSUS Generated MSI installable rule (read only)" with no way I can find yet to see what it actually is.

Hi.  Not sure if we're an anomaly or what, but the most recent Jabber update, 12.9.5.xxxxx, which initially was dependent on having the msi in the local repository, seems to have bad applicability logic.  After deploying it, it didn't just update those workstations that had old versions, it installed on EVERY workstation - even ones that had not Jabber install, prior.

Might be bad metadata?  We're now seeing two instances of supposed, but the download for the newer one appears to actually be the installer for

  • Catalog from the 17th (120.62MB, msi signed on the 11th, MD5 = 379C9A822C918F0D3E681A7689E40413, SHA256 = 5631F17F4155FFA81AA43F71F5927D090D0CDEBB7676CEAC3AB8D7B16121F925 )
  • Catalog from the 23rd - we have not published this one yet, but downloading from the link associated with it gets a different msi file (120.58MB, msi signed on the 19th, MD5 = 6A5C6930275DEDF9809A732DC3D1B45F, SHA256 = 198FE4E80F3F4760B0C1DC127A3399FCE08389E906690F82B33C79A96E34CD93, and internal properties say it's )

Newer one is marked as superseding the one from the 17th/11th.

Cisco's site lists the release from the 19th as version 41.3.5, not 41.3.4.

Ahhh, I guess the RSS post just went out a bit early, then.

At 1:38pm EST, that hit my inbox.  I tried syncing about an hour later at ~2:40pm EST, but apparently that new catalog wasn't actually available yet.  Looks to be sorted out now, though.

Today's catalog release supposedly includes Thunderbird 68.3, WinSCP 5.15.9, etc.
Sync is successful, but none of the updates that are supposed to be in it that I've checked are actually coming through.
E.g. the SCUP.log file is only showing Wireshark 3.0.6, WinSCP 5.15.7, and so on.

Hi.  The 7/20/18 catalog included Wireshark 2.6.2, and Foxit Reader  At least for us, they're showing up under PatchMyPC vendor, instead of under Wireshark Foundation and Foxit Corporation, as they have in the past.
I'm not finding any notes in regards to these having been recategorized.  Did I miss something?  Do we have a problem with our SCUP 2011 and/or catalog?

Ahhh, never knew that.  Thanks for the clarification!

Since QuickTime for Windows is essentially a dead product at this point, any chance of getting it dropped from the Apple vendor and iCloud in there? Or can it not exist under both vendors, meaning taking it out of the PatchMyPC vendor and breaking everyone's existing ADRs?

In trying to set up updates for iCloud, I wasn't able to find it at first in SCUP.  It's not under Apple, it's actually under PatchMyPC/SCUP Updates along with a ton of other products that we're not actually pushing updates for, currently.
I can publish the iCloud stuff successfully, but to get Config Manager to see it, we had to enable the PatchMyPC/SCUP Updates category for syncing, and the synced updates show an "Affected products" value of "SCUP Updates," and a vendor of PatchMyPC.

Short of messing with the cab file before every time we import it, is there any way to get this to show up:
  • In the Apple folder in SCUP
  • With the correct vendor
  • As its own product

...or am I missing something?

Pages: [1]