Messages

[wsl --set-default-version 2]

Quick suggestion here?
Install or update WSL as-is from Patch My PC on a test device, then run the wsl --set-default-version 2 command from within PsExec launched in the SYSTEM context. See if it does configure WSL to version 2.

I don't have a lot of experience with WSL, but I'm wondering if WSL's version is configured per-device or per-user? If the latter, and the wsl --set-default-version... command does nothing under PsExec, that may explain why adding it as a post-install/post-update script has no effect.

We'll be watching the catalog updates then!
Thanks Andrew!

Hello!

Looking at the Supported Products List (https://patchmypc.com/supported-products), there's a note for "Oracle Java 8" that it requires a manual download.

But it appears that the same product is available through Winget. Looking at the manifest from the Winget community repository (https://github.com/microsoft/winget-pkgs/blob/master/manifests/o/Oracle/JavaRuntimeEnvironment/8.0.4210.9/Oracle.JavaRuntimeEnvironment.installer.yaml), the URL listed in it is reachable, and it does not seems like it requires any kind of authentication.

Would it be possible to verify if Oracle Java 8 could download and update without having us to provide a local content?

Thanks!

Gezz, two times in one day that my Google-Fu failed me on the Ideas site!

Thanks Pete, we'll test it on on side, and add this capability to our deployment strategies.

[Update existing application's metadata, deployment type, detection method, and content files]

Hello!

I've been reviewing https://patchmypc.com/base-install-update-options-explained, and also tumbled upon https://patchmypc.com/forum/index.php?topic=7830.0. Just wanted to make sure and confirm:

When application updates are set to the default option Update existing application's metadata, deployment type, detection method, and content files, are manually-created relations of supersedence, dependencies and global conditions retained after the app is updated to a newer version?

We have previously packaged a software with an EXE installer, and that software is available in PMP's catalog as an MSI installer. We were wondering if we could supersede the old app with the new PMP-packaged app, and that supersedence would be retained when a new version gets released.

We might also explore at limiting the ability of certain apps to install on various environment using global conditions, and were wondering if they too would stick after an app update.

Thanks!

[Create a new application without modifying any previous applications]

Wanted to add to Adam's reply what has been posted on https://patchmypc.com/base-install-update-options-explained

Instead of activating Create a new application without modifying any previous applications, one could select the default option Update existing application's metadata, deployment type, detection method, and content files, and configure an adequate retention policy (Retain up to X previously created applications) to keep a number of older apps versions, in case they are needed.

The deployed application would always be the latest, and if mandatory deployments are set, they would also trigger an update.
BUT (and it's a big but), just as described in the blog post, mandatory deployments would be reevaluated and applied immediately, as their deadlines would be reached. So no concept of rings/waves -- all targeted devices would be updated simultaneously.

Really, the cleanest way to update existing assets with SCCM is to leverage ADRs.

Thanks to you both!
I did not find the idea with the search terms I used; I'll definitely go vote for it!

And yeah, that's what I was expecting for the post-(un)installation script: let it start and pass the return code as a parameter, and react accordingly (i.e. proceed with additional tasks if RC is success, or quit and do nothing if the RC is an unexpected one). We'll work on that direction for now until (hopefully) another solution comes up.

Glad we have more time! We're working on updating our documentation, and Publisher code to account for this change.

Well... yes and no. @Steve Burggraaf only quoted a portion of the addendum by Microsoft. What's missing from the blog post is that "starting August 15th, 2024 all new [webhook] creations should be created using the Workflows app in Microsoft Teams".

Blessed are those that created their webhook before August 15th, as it should work until December 2025.
Else, new customers or ones experimenting with reporting after Aug. 15th won't be able to join the party.

Hello!

We observe that there is no option to prevent the execution of a post-installation (or a post-uninstallation) script if the main software installation/update exits with a failure code.

For example, say a post-uninstallation script that do some additional cleanup after the uninstallation of the main program had finished. If the uninstallation fails with a RC = 1603, then the post-uninstallation script would still be executed.

What would be your recommendations to handle such a situation?
Could an option be added in the Publisher to prevent a post-(un)installation script to run with RC different than a success code? (And if so, could it consume the return code as set in the "Modify return code" property of an update/configmgr app?)

Thanks!

Thanks for the quick reply, really appreciated! (And totally understand why the icon would only show based on your tests.)

Hello!

I took notice of the addition of icons in the product treeview now indicate if the product requires local content, or is configured to skip the install if running by default -- which is great!

Quick question: does this new change only add icons when these ability are determined as required by Patch My PC, or should they also appear when we enable "Manage Conflicting Process"? (Behind the scene, I suspect the Publisher only display the MCP icon for apps/updates having a McpDefaultEnabled element in supportedproducts.xml, and would not use a BlockingProcessManagementPolicy element from Settings.xml as another source for displaying the icon.)

Reading the McpDefaultEnabled element in supportedproducts.xml, I find there is useful information about why PMP recommends/enabled MCP by default for a specific app/update -- for example, for Jaspersoft Studio (EXE-x64): <McpDefaultEnabled>Returns Exit Code 1, update will fail if application is open during update process.</McpDefaultEnabled>. Is that information displayed textually somewhere in the Publisher Console?

Thanks!

[do not]

Hello!

Jumping in 'cause I have a question which is the opposite: if I do not tick "Do not include the version number in the application name", does the Publishing Service reuse the application object in SCCM -- just like it does then "Do not include..." is enabled?

I always thought that I had to leave "Do not include..." unticked in order for PMP to reuse the same application object when a new version is released and retention is enabled, but now I'm curious if my reasoning is correct.

Hi!

Looking at the FAQ Are Driver Updates for Dell, Fujitsu, HP, and Lenovo Supported?, the answer is pretty clear that drivers from HP, Fujitsu, Dell and Lenovo would not be considered for addition to Patch My PC's update catalog -- since these manufacturers maintain their own third-party catalog that can easily be added to SCCM, it would hardly make sense to duplicate the feature in PMP.

I'm wondering if Patch My PC is closed to all drivers submissions, or only to those from the above manufacturers or others that provide a TP catalog for SCCM?

Thanks!

Makes sense! Thanks for your input!

Hey Ben!

Not really -- I'm searching for that option on "Updates" (software update packages), not for "ConfigMgr Apps" which, as you've shown, the option already exists.

Thanks!