Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Jake Shackelford (Patch My PC)

Pages: [1] 2
1
You can export your settings from the advanced section however I'm guessing you'd like some more fine tune controls around that? You'll want to submit it as a request on our ideas page found here: https://ideas.patchmypc.com/

2
Would you be able to send the following logs from that client device to [email protected]?

%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log

3
Generally you shouldn't need to keep them, we do recommended using the retain functionality for Applications though with a setting of at least 1.
That way in the event an application doesn't work within your environment you'll have the previous version available to roll back to.

4
You got on the right track with the option to disable the self updater.

Sadly we can't publish older apps as our catalog only has the latest revisions of the applications.

5
As it stands today there is not a way to do the export on a schedule. We do have a similar idea on our ideas page I'd suggest giving it a few votes. https://ideas.patchmypc.com/ideas/PATCHMYPC-I-1388

7
This should be in your catalog during the next regularly scheduled sync.

8
We will look at adding this soon! Thank you!

9
Would you be able to send the following logs to [email protected] ?

%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\CIAgent.*log
%WinDir%\CCM\Logs\ClientLocation*.log
%WinDir%\CCM\Logs\CMBITSManager*.log
%WinDir%\CCM\Logs\ContentTransferManager*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\LocationServices.log*.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)

10
Use the uninstall intent. Both will work but install will show as an error.

11
You could run a basic batch or PowerShell script to set the ACL on the plugin folder: https://theitbros.com/using-icacls-to-list-folder-permissions-and-manage-files/

For info on how to add this you'd want to check out the following KB article https://patchmypc.com/advanced-pre-post-scripts Which actually covers a very similar scenario.

12
We currently only have one download location per app, in cases like this we generally recommend using the local content path option. More info can be found via this https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download

Essentially you can manually download the file and place it in the repository and have the publisher look at the repository before it attempts to download. This obviously isn't ideal long term.

We will reach out to the vendor and see if they have plans on rectifying the certificate error.

13
Do you know what file caused this scan to alert you?

14
If the main install fails yes it will not run!

15
A pre-script will not run if the core installation fails.

In regards to a prescript to kill the processes you can actually use our right click options for manage conflicting processes. This will let you target apps to close, more info can be found here: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications


You can also use this KB to get more info on the pre/post script options: https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#custom-scripts

Pages: [1] 2