Messages

Yes, here is a way to clean Up Third-Party Updates from the WSUS UpdateServicesPackages Folder - https://patchmypc.com/clean-up-third-party-updates-from-the-wsus-updateservicespackages-folder

The updates that you want to publish with Full Content, you will republish those by following this guide.  https://patchmypc.com/faq-scup-catalog#republishing-updates

Email us at [email protected] if you continue to have issues and we can set up a session to see why those aren't publishing Full content.

Hey Louis
  If you are taking over from someone else, check and see if the CM console third-party software update catalogs have Patch My PC catalog active.  If that is set up previously it will pull in Metadata.  If not shoot us an email to [email protected] and we can setup a support session to resolve.

Fabian
Does the account you are using have the proper permissions within your CM console to trigger a SUP sync? The account you use (default is the computer account) when configuring the SMS provider connection in the sync schedule tab would also need full permissions for software updates in SCCM.  If you imported that custom security role from the link:
https://patchmypc.com/permissions-required-in-sccm-for-base-installation-packages-from-patch-my-pc
, make sure to add software updates to that roleÔÇÖs permissions as well.  It will need that to trigger a SUP sync.

Ulicor
Can you submit this to [email protected] for review?

Would you submit your issue to [email protected]?

You can certainly segment the updates out to separate deployment, but they will only install on machines where the update is required.

Please take a look at this to see some of the advanced options of our service. https://patchmypc.com/advanced-configurations-available-using-the-registry-for-patch-my-pcs-publishing-service

Did you see the detection method from the Publishing service:  <lar:And>
  <bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X86" RegType32="true" Value="Bld" Type="REG_DWORD" />
  <bar:RegDword Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X86" Comparison="LessThan" Value="Bld" Data="28127" RegType32="true" />
</lar:And>

Great To Hear!

Hi Rcgalyen
We found an issue in the detection method script that may cause it to not detect correctly. Could you please delete this one application:

How to Delete Applications Created by Patch My PC in SCCM - https://patchmypc.com/how-to-delete-applications-created-by-patch-my-pc-in-sccm

Close and reopen the Patch My PC Tool and run a sync to have it re-create and let me know if that helps?

Hello FGN, you are seeing that error because there is a higher version patch for the product.  The updated version is 9.2 M3 release on Nov 5 2019. https://www.displaylink.com/downloads/windows

Hi Jim, did you select to republish the update and also choose to supersede the update then sync the publisher.

kawhite,
Are you able to ping timestamp.digicert.com?  You are getting errors: An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2148081670.  Can you verify that you have your cetificate imported?

Hi @bryash
The current version for PDFSAM is 4.0.5.0 as of nov4 definition file.  1603 is a fatal error during your upgrade installation or uninstall/install have you been able to search your msi logs to see what may have caused the failure?

Hello @bryash Are you speaking of the PatchMyPC Home Updater?  Is the account that you log in with in the Administrative user group?