Messages

Hi
  Yes, since you have both you will need to add addition switch or create a MST for the reader program.  If the reader isnt needed on those and they want to user the reader in phantom you could uninstall the app from their device. This is very similar to having Acrobat and the Adobe reader installed on the same device.
https://kb.foxitsoftware.com/hc/en-us/articles/4403064938516-How-to-set-Foxit-PDF-Editor-as-the-Default-PDF-Viewer-Without-UAC-Prompt-

Hi Strauch
  Please submit in a support case to https://patchmypc.com/technical-support
please include the following logs/files:
Serverside
%PatchMyPCInstallDirectory%\PatchMyPC.log
%PatchMyPCInstallDirectory%\PatchMyPC*.lo_
%PatchMyPCInstallDirectory%\Settings.xml
Client side
%WinDir%\CCM\Logs\AppDiscovery*.log
%WinDir%\CCM\Logs\AppEnforce*.log
%WinDir%\CCM\Logs\AppIntentEval*.log
%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\CIAgent.*log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
%WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
This may be found in the %temp% of the user who clicked ÔÇÿInstallÔÇÖ in Software Center if it was an ÔÇÿAvailableÔÇÖ deployment.
%WinDir%\CCM\Logs\StateMessage.log

Hi Rory, Can you submit your case to https://patchmypc.com/technical-support and include the following logs from your server for review
%PatchMyPCInstallDirectory%\PatchMyPC.log
%PatchMyPCInstallDirectory%\PatchMyPC*.lo_
%PatchMyPCInstallDirectory%\Settings.xml

Hi Ccowart83
That error is normal when there is a newer version of a specific software that isn't in our current catalog and cant be validated, once the Patch My PC catalog has been updated with the newer software version you will not receive that error anymore. That software was updated in today's catalog, here is the explanation of the error: https://patchmypc.com/digest-verification-failed-on-content-for-software-update

Google Chrome 92.0.4515.159 (x64/x86)
Release Notes for Google Chrome 92.0.4515.159
Release Type: Ô¼ñ
CVE-IDs:
CVE-2021-30598; CVE-2021-30599; CVE-2021-30600; CVE-2021-30601;
CVE-2021-30602; CVE-2021-30603; CVE-2021-30604

Hi Todd, I will send you an email to help resolve.

Hi Todd
I will email you direct to discuss this issue.

Hi jmcnair101, Currently there is no way to Integrate, export data or any plans to Integrate with Service Now in the future.

Hi Daniel
  Please submit in your PatchMyPC.log and Settings.xml for review to https://patchmypc.com/technical-support

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.

Thomas
You can download the publishing tool from the following link: https://patchmypc.com/publishing-service-setup-documentation
Email us at [email protected] and we can have a remote session to assist you with setting up everything.  You currently have an enterprise subscription are licensed to use our publishing tool to manage third party updates.

We have some reports  that you can install from our publishing service that would be good to use.  One of the reports that is good to use would be the Sub- SUG Compliance - Software Update Information.

Hi Morten
Webex updated to 3.0.15410.0 yesterday(5/14/2020), trigger a Publishing service sync to pull in the new catalog to resolve your issue.

Hi Louis
  You will either need to select an already created deployment package or Create a new deployment package for this update group within your ADR.