• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 
Menu

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.

Show posts Menu

Messages - Spencer (Patch My PC)

#1
Hey James,

Thanks for reaching out to support!

That is expected behavior as all content deployed from SCCM is downloaded to the local cache (CCMCache). Updates are then copied over to the SoftwareDistribution folders since that's what the WUA uses to process the updates. Products that do not have any right-click options enabled on them from the PMPC Publisher, will not output logging info in the scriptrunner.log

It's possible, content was cleared out in the CCMCache for those updates but left over in the SoftwareDistribution folder.

We can also look at the following ConfigMgr logs (like CAS.log which will show you if ConfigMgr downloaded the file and WIndowsUpdate.log (which will show you if the WUA downloaded the file).

https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs:~:text=Third%2DParty%20Software%20Updates%20Failing%20to%20Install%20on%20Client%20Devices

I also came across this post from Jason Sandies indicating the same behavior:
https://techcommunity.microsoft.com/t5/windows-servicing/location-of-windows-updates-download-with-configmgr/m-p/2144311


#2
Hey jdugger,

Thanks for reaching out on the forum!

The hash error is typically caused when the vendor releases a new version of their product that we have yet to validate add release to our catalog.

The current version in our catalog now: Microsoft Power BI Desktop 2.137.751 (x64)

The latest version available from Microsoft is: 2.137.952.0 (Which was released today 10/22)
https://www.microsoft.com/en-us/download/details.aspx?id=58494

I would expect this to be added to the catalog no later than today (5pm est)!

You can stay on top of catalog releases by subscribing to our newsletter here:
https://patchmypc.com/scup-catalog-newsletter-signup

If you have further questions, please don't hesitate to reach back out! 😊
#3
Hello There,

Thanks for reaching out!

The main issue we see with Zoom and updates not being applicable is due to the installed variant of Zoom being the User-based installer. We do support the user-based version of Zoom in our catalog which you can deploy as an update to patch those versions.

You can also deploy the update (install/required) and application (uninstall) for Zoom (User) to remove that version and replace it!

If you would like us to further troubleshoot this issue, then we'll need to take a look at the following log files:

When troubleshooting Intune application installation errors on a client, we will need multiple client logs. Please include the following logs:

%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%\Microsoft\IntuneManagementExtension\Logs\AppWorkload*.log
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml


If there are any rolled over logs, please include those, too.

Note: Some Patch My PC log files listed above may be found in %WinDir%\CCM folder if that folder exists.

We'll also need the registry export from this script to determine what variant of Zoom is installed on those clients:

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

You can upload the logs to our sharepoint here: www.patchmypc.com/share

Or you can email [email protected] with those logs as well!

Thanks,

Spencer Cruz
#4
Hello There!

Thank you for reaching out on the forum!

This issue occurs because Mozilla keeps two versions of the Extended Support Release (ESR) version of Firefox live for three-point releases whenever they issue a major ESR release:
An older stable version.
A newer version that is potentially unstable but can be rapidly stabilized by Mozilla as issues are resolved.

Please see the following link for why Firefox ESR has not been updated to that "Latest" ESR build:

https://patchmypc.com/firefox-esr-not-in-app-catalog

Let me know if you have further questions! 😊
#5
Hey There,

Thanks for reaching out on the forum! For the Microsoft Update section to work you'll need to have configured your clients to pull Windows Updates from WUfB (Windows Update for Business) instead of WSUS.

The inventory extension will then poll that data from your clients and will be able to populate that dashboard!

More information on this can be found in our docs below:
https://docs.patchmypc.com/installation-guides/advanced-insights-and-patch-insights/microsoft-updates-inventory
#6
Hello there!

I just wanted to let you know that the changes for this have been made in the catalog and the default option for this product in MCP is to "Skip" the install. We thank you for bringing this to our attention!

Let me know if you run into any issues or have further questions!
#7
They shouldn't notice the switch when deploying our package! The new version will install over top and will not affect user sessions. 😊
#8
Hello!

Thank you for reaching out here!

The vanilla version Edge (Included with windows) is missing registry values that Patch My PC uses to determine the architecture and branch of the Edge install. The best workaround here would be deploying the Edge application to devices. Once the MSI is installed once, then updates should become applicable.

This is also mentioned on our Known Issues page for reference:
https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc#:~:text=true%20is%20included.-,Microsoft%20Edge,-Microsoft%20Edge%20updates
#9
This has been resolved! Kofax DL files needed for PMPC can be found under the 'Power PDF Advanced Volume – All Versions' link on the first page once you've logged into the Download site. You'll then need to accept an EULA to get to the main download page. On that second page, scroll down to the very bottom under the 'Patch' section. There is where you can find the .zip files containing the proper MSI package.

Email has been sent to you with screenshots and instructions! 😊
#10
Hey Phil,

Thanks for reaching out to support! Can you please confirm what version of Kofax you're trying to publish?

If you're unable to source the correct package, then I would suggest reaching out to the vendor to confirm if you have access to that specific version of the product.

KofaxPowerPDFAdvanced-5.0.0.21.msi

Can you also confirm that this is where you're trying to access the files:
https://delivery.kofax.com/Downloads

You can send screenshots to my email via [email protected]
#11
Hello,

Thanks for reaching out on the forum!

At this time Adobe hasn't released a newer version of Adobe Acrobat Reader DC (x86) 24.002.20895. The 64-bit version is the only version being maintained at this time.

We've tried to find confirmation of this from the vendor, but only found this article that mentions EOL for the x86 version back on June 12, 2023. However, they've just stopped updating that version within the past two version of the base app.

https://helpx.adobe.com/acrobat/kb/end-of-support-acrobat-reader-32-bit-os.html

We still monitor for new version releases and if made available will provide it in our catalog.

Thanks,

Spencer Cruz
#12
Hey Jay,

Thanks for reaching out on the Forum! Unfortunately, we don't allow older catalogs/products to be published natively through the Publisher. However, if you need to side-load an older version of Global Protect or any product, you can do so with our new Custom Apps portal!

https://docs.patchmypc.com/patch-my-pc-cloud/custom-apps

Through the portal, you can upload the older binary and define the configuration. Once done, it will sync down to the Publisher and will be available under the "All Custom Products" section at the top of ConfigMgr Apps/Intune Apps/ Intune Updates.

From there you can configure any right-click options and publish it to your respective management system! 😊

If you have any questions on how to configure the Custom App portal, please don't hesitate to schedule a setup/review call using the links below:

https://calendly.com/spencer-pmpc/patch-my-pc-setup-and-review-session

For more times - https://calendly.com/patch-my-pc-live-demos/patch-my-pc-setup-call
#13
Hey Kfason,

Thanks for reaching out on the Forum!

We have received multiple requests to split zoom into two products entries. However, both versions of the product rely on the same registry entries and files, so detection would be the same for both versions.

We do have this UserVoice Item requesting this if you would like to up-vote it for tracking:
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-745

We're always looking for ways to improve detection and delivery of our products. So, if something changes on our end, we'll update that UserVoice item to inform everyone that it's now been split.



#14
Hey MS,

That's wonderful new and thanks for the update. We'll go ahead and mark this as resolved. However, if you need anything else don't hesitate to reach back out!
#15
Hello,

Thanks for reaching out to support!

Intune updates don't support uninstalls command due to the requirement script associated with them.

You can use the Intune Application package to deploy an uninstall of the application which will remove the full version of the app, including updates.

More information of the differences between Apps and Updates can be found here:
https://patchmypc.com/intune-apps-vs-intune-updates