Messages

Were these the original configurations or did they get changed? Would you be able to send a copy of your patchmypc.log to [email protected]

Currently that version of R For Windows isn't signed by the developer. Once it is signed we will add that version to the catalog.

Keep us posted! Sometimes the issue can just appear at odd times, the reason behind it is the ConfigMgr Client sometimes isn't fast enough to deploy out the certificate when it gets installed.

We do have a KB article about this found here: https://patchmypc.com/applications-fail-to-install-during-osd-in-sccm-with-error-authorizationmanager-check-failed-0x87d00327

If you reach out to us via email [email protected] we can request some logs and dig into what might be happening.

We are actively looking at fixing this in the next release! We apologize for the inconvenience.

If you'd like by all means, we can dig in and see if we can reproduce.

This document should help! https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

Our docs for setup can be found here: https://docs.patchmypc.com/

There isn't specifically one that covers going from the Basic tier to the publisher variant but it should be as simple as removing the Catalog and instead using the Publisher listed on the docs page. We'd be happy to help with a setup call as well. https://patchmypc.com/schedule-setup-call

Sorry for the delay here, if you refresh your view it should be updated.

What Server OS are you currently running?

We'll want the following sent over to [email protected]

%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
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
%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
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

Is this for an update or base app install?

You would need to query the SMS_DeploymentType Object and grab the Model name which should give you what you need. How you query that is up to you.

It's an ID generated by ConfigMgr
Update ID if it's an update and deployment type ID for applications

It's used to track things in the registry like deferrals or max run time and a slew of other things

It is technically the ModelName from the SMS_DeploymentType object

At the end of the day ConfigMgr controls it.

This seems incredibly frustrating to say the least:

Can you send the following logs to [email protected] ?

%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
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log