Messages

When trying to publish an Adobe Acrobat Reader DC update I receive the following error in the "SMS_ISVUPDATES_SYNCAGENT"

----------------------
Failed to publish content for update "49f95540-6b94-443a-966e-0c386ce2c209" because the content signing certificate "CN="Adobe Systems, Incorporated", OU=Acrobat DC, O="Adobe Systems, Incorporated", L=San Jose, S=California, C=US, PostalCode=95110, STREET=345 Park Ave, SERIALNUMBER=2748129, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5" has not been approved.

Solution: Review and approve the content signing certificate from the Certificate node and try again.
----------------------
Previous Adobe update had same issue.

Other updates are published without an issue. This seems to be Adobe issue.
We use native SCCM 3rd party patching without the Publishing Service

don't think so
damn

The path can be found here for x86 version
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Notepad++

Our software is installed on a different drive (D:\Program Files (x86)\Notepad++)

thanks in advance

https://www.asg.com/en/Solutions/Applications-Management/ASG-Remote-Desktop.aspx

I understand the free version is not having a silent switch, but since SCCM is an enterprise solution and enterprises don't (or should not) use freeware. I think the paid version can be included. this version can be installed silently.

thx, but I do not use the publishing service, I use native Third Party Software Update Catalog in latest SCCM build.

It would be nice to have supersedence, this is what updates are, they superseed the previous version.

Notepad++ 7.6.0 (x86) is not detected to update in native SCCM Third Party patching when not installed in default location.

x64 version on a different machine and installed in defaul location is detected OK

So I am not sure if it is related to the not default location or if it is related to x86 version

I notice an issue with the patch catalog (since the order is still pending in our administration, I use the Trial Catalog to get used with the system, so excuse me if the issue is only related to the Trial catalog).

Let me explain: we deploy patches once a month, and only once a month except some urgent emergency reason (day after MS Patch Tuesday) all the approved patches follow a couple of stages (available on test machines for 5 days, accept machines the 7 days after test phase and another week later, all our production machines)

Now with 3rd party patching using the PatchMyPC catalog we experience that the patches in the catalog not contain superseed info. For example the moment a new Google Chrome update becomes available and SCCM did the sync of the catalog, the previous update immediately expires. This means that our production machines never receive the Chrome update since the available time of the approved update is past the expire date.

I know that you should always deploy the latest version, but since we use Chrome in a production environment, a new version need to pass the test/accept stage.The same for Java updates and so.

Can the catalog be expanded with the superseding info the same way MS is providing their patches? Chrome version 70 superseeds verion 69.
In SCCM you can define the time before a superseeded update gets expired to get rid of old versions.

thanks in advance

1 thing to keep in mind I think: the update will not install when an active citrix connection exist (wfica32.exe)

Since Citrix Receiver and Citrix Wokplace are available in the catalog, the extra client component HDX RealTime Media Engine can't be absent.

https://www.citrix.com/downloads/workspace-app/additional-client-software/hdx-realtime-media-engine.html