Messages

Hey Blanzeros,

Thanks for reaching out to the forum! When you enabled the option to "Disable Built-In Updater" did you run a publishing service sync to apply that setting to the application?

You can do this under the Sync Schedule tab in the Publisher by clicking on Run Publishing Sync Service.

If that doesn't work, please send me the following log files - [email protected]:

%PatchMyPCInstallDirectory%\PatchMyPC.log
%PatchMyPCInstallDirectory%\PatchMyPC*.lo_
%PatchMyPCInstallDirectory%\Settings.xml
%PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
%PatchMyPCInstallDirectory%\PatchMyPC-PublishingHistory.csv
%SCCMInstallFolder%\Logs\SMSProv*.log

You're welcome, and glad I could help! Don't hesitate to back out if you ever need anything else! 😊

Hey Kotond,

Thanks for reaching out on our forum!

If you're only looking to update Webex and not make it available or required as an app, then you can just publish the update for Webex.

If you want the update to target all devices, then you can add that group to the Manage Assignments option!

All of our Intune Updates had requirement and detection scripts. So they will only install if the products are installed on the client, and if it's an older version of that product.

More information on the differences between Intune apps and updates can be found here:

https://patchmypc.com/intune-apps-vs-intune-updates

Hello,

Thank you for reaching out to support!

We publish the Enterprise Stable version of Edge and perform the following registry key validations when installing the application packages:

'SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}' = 'ap'} = @{Value = '*stable*';WOW6432Node = $True; Operator = '-like'};@{'SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}' = 'ap'} = @{Value = '*x64*';WOW6432Node = $True; Operator = '-like'};}

The full detection scripts for applications published by PMPC can be found in the PMPC Installation Directory inside the detection method scripts folder.

I recommend pulling that script and moving it to a client that's failing to apply the application to verify detection.

On that same client, can you also pull the following log files and send them to [email protected] with a description of the issue:

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

Lastly, can you please run this script on that same client? This will export a csv file containing all install products on that machine. This will also help us determine issues with detection:

https://github.com/PatchMyPCTeam/CustomerTroubleshooting/blob/Release/PowerShell/Export-PMPCInstalledSoftware.ps1

Hello and sorry for the delay!

Can you please collect the following log files from one of the failing clients and email them to [email protected]? Once we have the logs, we can investigate why the 5.0 update is failing.

When troubleshooting update installation errors on a client, we will need the following client logs:

%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\DeltaDownload*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
%WinDir%\CCM\Logs\ScanAgent*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\WUAHandler*.log
%WinDir%\WindowsUpdate.log
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

Hey there!

Just got word from our AI devs and this is what they stated:

 At this time there is currently no source of data at the server or way of harvesting from client logs where content came from during OS Deployment. A remote possibility is that the Status Message data may contain location data for downloaded packages/apps/drivers/images. This is something we'll have to look into and see if that data can be accessed.

In the meantime, I urge you to submit a uservoice item so our devs can track this request and keep you and other customers updated on the status! 😊

You can submit the request here:
https://ideas.patchmypc.com/

Hello, and thanks for reaching out to support! I have forwarded this inquiry to our Advanced Insights team for review. Once they've had a chance to review your request, they will respond with further instructions!

Thanks for your patients!

Got it, thank you for clarifying that! Can you please send me the following log files from that client machine. You can email them to [email protected] if that's easier!

%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


I'll also test this in my lab and see if I can repro this issue.

Are you deploying the update or application package for docker? It sounds like the client is pulling the content from another machine using Delivery Optimization or Branch Caching.

Can you confirm that the WSUS signing cert is not expired and is present in the clients Trusted Root and Publisher machine cert stores?

Hey TJ,

Thanks for reaching out to support! For OBS you'll need to enable Manage Conflicting Processes since the installation is failing due to a conflicting process on that client.

More information on how to configure that setting can be found here: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

If you're making that change an already published update, then you'll need to republish that package for that change to be applied:

https://patchmypc.com/when-and-how-to-republish-third-party-updates

If you have further questions or concerns, please don't hesitate to reach back out! 😊

My pleasure, Gary! Hope it gets resolved soon! 😊

Hey Gary,

Just tested this in my lab by updating AnyConnect 4.8.0 to 4.10.0 (Latest) using our ConfgMgr Application package which was successful.

I'd be interested to look into the logs and see why this may be failing for you!

If you could please send us the following log files from one of those failed clients. You can email them to [email protected] or [email protected]

ConfigMgr:

Updates: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#publishing-service-logs
Applications: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#publishing-service-app-logs

Intune:

https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs-intune

Hey Gary,

Thanks for reaching out here on the forum!

What I can suggest here is adding this uninstall script as a Pre-Script to remove any older versions of AnyConnect before installing version 4.10.

https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Uninstall/Pre-Uninstall/Uninstall-Software

I'll have to test the updates myself to see if there is a better solution, but that should at least help you out when trying to upgrade! 😊

If you have further questions or would like to open a support ticket, please email [email protected] and we can assist further!

My pleasure! 😊

Hey Dan,

Thanks for reaching out on the forum!

The way we handle our updates via Intune is by adding a Requirement script that will run first before the update is installed.

That script will first check if the application is installed on the client, and then will look at the version. If the version is less than that of the update then the update will install.

If not, then it will continue on to the next update. Updates that are not applicable on clients will show as such in the Endpoint Console (Intune).

Here is a KB article that will explain how our Intune Packages work in more detail:

https://patchmypc.com/intune-apps-vs-intune-updates

As for the deployments, updates can only be deployed as required deployments. So if you wanted to cover your bases, what you can do is deploy all updates to All Users or All Devices and they will only install on clients when needed.

Hopefully that helps you here! However, if you have further questions or need more clarification please don't hesitate to reach back out! 😊