Messages

[.0]

Thank you for uploading the file, Liam.

We checked the file's hash and determined that it has the same hash as the one we use in our catalog.
The only difference is the one you noticed as well:
ps-pulse-win-22.7r2-b29103-64bit-installer.msi
ps-pulse-win-22.7r2.0-b29103-64bit-installer.msi

For now, we'll keep the file as it is, as we are unsure why you got a file with a different name.
Please rename the file to match the name of our file for now.

We'll continue to monitor this and make the necessary changes, if needed.

Hey Liam,

we already have an update.
Can you please share the new installer with us?
Please upload it to patchmypc.com/share

Hey LiamPMPCForum,

Thank you for reaching out. Give us some time to look into this.

We'll update this thread as soon as we have news.

hey jjurgens,

The latest version is now part of our catalog.

Thank you for bringing this to our attention.

[updates]

Hey PDowell,

If the updates you deploy from ConfigMgr just sit as available in the Software Center, please look at the ADR deployment configuration.
On the Deployment Schedule tab, you should see the configuration.
The update is likely deployed as available with a deadline X days in the future.

If you're still having issues with this, please open a support case with us, and we'll take it from there.

Thanks for sharing that article with us, Joe. It's really useful.
Unfortunately, that is something outside of our control. We cannot manage that.

@Joe, offtopic. your username was configured to be your email address and was publicly available.
I have renamed your user account to "JoeM".
I hope that's fine.

Hey Phil,

Is the software deployed as an ConfigMgr App or as an Update?
Does the software show up as failed in the Software Center, despite the software being up to date on the device?

Hey Robert,

We don't have any control over how the installer behaves.
The installer for the Teams Classic version we support will patch the "Teams Machine-Wide Installer" app. This app installs the actual Teams app for each user profile.

The user-based Teams app that is installed by the "Teams Machine-Wide Installer" self-updates.

The behavior you are noticing might be something Microsoft configured with their automatic updates for the user-profile version of Teams.

[General]

Please open a support case.
While the error message from your initial post is benign, if you no longer have any successful syncs, there is something else at play.

Please collect the PMPC Logs (General tab then press on Collect logs.
Please attach the logs to the support case.

[Cloud]

Hey mpotase,

The error is benign and can be safely ignored.
This error only means that the connection to portal.patchmypc.com is not yet configured on the Cloud tab. This also means you are not using the new custom apps feature we released a few months ago.

[Advanced]

Any update on this? The link provided contains the installer needed for this to be updated.

Hey storm-warning,

The VMWare products have been switched to require a manual download.
Local Content Repository for Applications that Require Manual Download

Despite the software being publicly available for download, the vendor now provides the installers in a compressed format.
The PMPC Publisher does not yet have the ability to uncompress the files.

To get the software successfully published, you will have to manually download the installer, extract it from the archive and place the installer in the local repository folder declared on the Advanced tab.

This is great news, Matthias! I'm happy this works fine for you now!

[1602 (0x80070642)]

hey mdigrego,

This is a great question.
If you navigate to the Intune Portal --> Apps --> Windows Apps --> select the app you are interested in --> under "Overview" you'll find the Device status. It will show you on how many devices the software was successfully installed, on how many it is still in progress and on how many it failed.

If the user defers the installation, Intune will mark it as an installation failure.
Any installation failure marked with exit code 1602 (0x80070642) means the user deferred the installation.
PatchMyPC-ScriptRunner – Known Exit Codes

that is correct.

In addition to adding the app under "blocked apps", please make sure to deploy the software as required to the same group the Enrollment Status Page profile is deployed to.

Then Intune will only evaluate that single app during Autopilot.

[all]

hey mguenth83,

During Autopilot, Intune will evaluate all win32 apps that are deployed as Required to all your devices.
In your case, I assume all Intune Updates you package through the PMPC Publisher are deployed as required to all your devices.
This will slow Autopilot down, because the more Intune Updates you deployed through PMPC, the longer it will take Intune to evaluate all of them during the enrollment of the device.
The Intune Updates are win32 apps as well, so Intune thinks it needs to evaluate them as well during Autopilot.

Having Intune Updates being evaluated during Autopilot is not necessary, as they won't apply anyway.

The best option to go here is to have one app, maybe Company Portal or anything else, deployed as Required to All Devices and then marked as a "blocking app" in your Enrollment Status Page.
Intune will then evaluate that win32 app only.