• 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 - Liviu (Patch My PC)

#1
We are monitoring the situation, when this happened in the past, they had another release quite soon. As soon as a new is released, we'll update our catalog.
#2
Hey Rafal,

Based on Microsoft Release Notes build 123.x is the latest.

However, they pulled it without any official information.

If you go to the download page, you'll find that version 122.0.2365.106 is downloaded.

Because of this change, we rolled the changes back as well and re-published 122.0.2365.106 with an updated ID.
#4
Great news, thank you for the update!
#5
Hey Muja13,

This issue usually appears when the vendor releases a new version that isn't in our catalogue yet.
That isn't the case this time, as the latest version they released is the one we have in our catalogue too.

This can mean that you either get an installer with a different due to their CDN or it can mean a caching issue and the wrong installer is being downloaded.

Please open a support case to further troubleshoot this.
In the support case, please include:
1. The Patch My PC logs: They can be exported from the General tab within the PMPC Publisher console by pressing the Collect Logs button.
2. A screenshot of the hash of the Snagit installer. Manually download the Snagit Installer, and then run the Get-FileHash command to get the hash of the file that gets downloaded on the server hosting the PMPC Publisher.
#6
Hey Vik,

Thank you for the feedback, it was very nice being there! :)

To investigate this issue further, please open a support case and include the following information:

1. Hit the "Collect Logs" button from the "General" tab within the Patch My PC Publisher --> it will generate a zip archive, please attach it to the support case.
2. Run this PowerShell script and include the "C:\PMPC_Repository\LocalContentHashes.csv" to the support case as well.
#7
Hello Vik,

Was the correct installer downloaded to the local repository?
This guide will tell you which installer needs to be downloaded.
#8
One way of doing this would be to use the PowerShell Deployment Toolkit as a "Post Script" and have it display a notification for the logged-on user.

There is an idea for us to support this option natively, using the "Manage Conflicting Processes" right-click option.
Please upvote this idea. The more upvotes it receives, the better.
#9
Hey Ben,

When we've seen this issue before, the cause was the icon.
Can you please try another icon and see if that does the trick?

We are working to improve the error message and make it clearer.
#10
Hey CFreeman,

Unfortunately, there is no such option. You would have to create your own custom script that does that and specify it in the "Add custom pre/post scripts" right-click option.

Please note that when ConfigMgr/Intune does the install of the app/update you deployed, it will do so as the SYSTEM account.
You will have to configure the script to display the prompt for the logged-on user while the install execution is done as SYSTEM. This is not easy to achieve, and it can be a security risk, depending on how it's achieved.
#11
Hello theresaellis,

This is something PMPC cannot provide support on.
However, to provide some information on this thread - you mentioned that you started hybrid-joining your devices in Intune.
You mentioned that "Co-management" isn't on.
What do you mean exactly? That Cloud Attach is not configured or that the workloads are set to "ConfigMgr"?

If you want to manage the "Compliance policies" from Intune, you need co-management in place and the co-management workload for "Client policies" moved to Intune.
#12
And thank you for letting us know we missed this one.

Automation can break at times and cause us to miss an update, we are always grateful of our customers when they let us know!
#13
The latest version is now part of our catalogue.
#14
Hello muja1913,

Thank you for letting us know we missed this release.
Our automation broke for this software and failed to let us know a newer version is available.

It will be added to our catalog with today's release.
#15
Hi Kevin,

Would it be possible to provide more details on what you are looking for?
We only support version 8.0 and the latest, which is 8.3.
We don't support version 8.1.

The applicability rule for version 8.3 (MSI-x64) is configured so it will not upgrade devices that have version 8.0 (x86) installed.