Hi rhITsec Version 21 is a pretty old version and may be one that requires some "persuasion" or "scripting intervention" to cleanly update. You may want to script an uninstall as a post script to see if it cleans off everything before the update or even have a post script to clean up afterwards.
Please log this issue using our support email https://patchmypc.com/technical-support so we can troubleshoot further. Also please include the following logs From the server: %PatchMyPCInstallDirectory%\PatchMyPC.log %PatchMyPCInstallDirectory%\Settings.xml From a client device: %WinDir%\CCM\Logs\ScanAgent*.log %WinDir%\CCM\Logs\UpdatesDeployment*.log %WinDir%\CCM\Logs\UpdatesStore*.log %WinDir%\CCM\Logs\WUAHandler*.log %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist) %WinDir%\WindowsUpdate.log
Hi Relindwto6 Yes, you can add the disable self updater on your application as well. It will revise that application once you sync. You will need to be sure and update your content to reflect the changes.
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.