Messages

Hello Iraklis,

Regarding question 1:
CustomerCreated assignments are the ones you or a colleague manually created in Intune for a PMPC Publisher app. When a new version was packaged, these manual assignments were automatically copied to the new version, along with the ones set by the PMPC Publisher.
If you don't want the manually set assignments to be copied over, please uncheck the setting documented in this KB article.

Regarding question 2:
What files are updated by the installer of a newer version fully depends on the vendor.
It's likely that Microsoft only updates some files to ship bug fixes or improvements. The Teams.exe might remain the same.

If a firewall rule is needed to allow the program to function, then yes.

Hello TJ,

We don't support custom scripting.
If you write your own script to create any configuration you need, such as a firewall rule, you can specify it as a post-installation script within the PMPC Publisher Console.
We cannot do this by default, as some customers might not want the firewall rule to be created.
Please use this right-click option to do that.

With that configuration, your custom post-install script will run after the installation of IntelliJ is complete.

[On VM1]

Hi Steadybird,

I have given this some more thought.

You could use two PMPC Publisher consoles. I ran a test in my lab to make sure this works fine.

On VM1:

• Select some Intune Updates.
• Use dynamic assignments to deploy any updates that have a CVE and run the sync daily.
• Any updates that don't have a CVE will still be published.

On VM2:

• Select the same Intune Updates as on VM1. If you customize the software using right-click options, customize them exactly the same to avoid conflicts.
• Configure the sync to run monthly.
• Configure the 'Manage assignments' right-click template.
• When the sync runs, if the Intune Updates are already published in Intune, they will just be assigned according to the 'Manage assignments' template.

I have tested this just now, it works fine.
The only note I have is to configure the 'Intune Updates' with the same right-click options on both VMs.

Hey Steadybird,

That's quite a pickle. 

This is the best option I can think of:

Configure Dynamic Assignments only.
Run the sync daily.
If the criteria for dynamic assignments are met (the update has CVE), it's assigned.
If it's not met, publish the update to Intune without any assignments (keep the 'Manage assignments') option empty.
Then, once a month, manually deploy the PMPC updates that don't have any assignments.
You would have to go to Intune Apps --> Options --> and uncheck these 2 options:

• Copy the assignments from previously created applications when an updated application is created
• Delete the assignments from previously created applications when an updated application is created

It's important to do that, as when new updates without CVEs are published, you don't want the assignments to be automatically copied by the PMPC Publisher.
https://patchmypc.com/intune-application-creation-options

I would also make sure I retain a few older versions in this setting:

• Delete any previously created updates when a new update is published

I would retain 4 or 5 at least.
When you manually deploy the software at the beginning of the month, and you are doing a daily sync, if you configure the setting to NOT retain older versions, your manually assigned one will be deleted.

This is not pretty by any means, but it will do the job.

This second instance set to automatically sync daily.

Is this possible? How would the two instances interplay with each other? Would they recognise Intune apps published by each other?

Is it even possible to have dual instances even on separate machines?

It is possible to have two instance of the PMPC Publisher, but that will not resolve the issue, as the updates will still be published to the same Intune tenant.
The resolution I mentioned above should be the best option I can think of, given your requirements.

The more applications you add to your ESP, the longer it will take for them to install during the enrollment of the device.
That can make the process slower.

There is no need to add 'Intune Updates' to the ESP as a blocking app. 'Intune Updates' will only be installed if an older version is found.
As the device will be completely new, no older version will be installed at that time anyway.
Adding 'Intune Updates' to the ESP will unnecessarily slow the enrollment down.

If the option was unchecked after the software was packaged in Intune, you will have to delete it from Intune and package it again from the PMPC Publisher.

For any devices that are stuck in that state, deleting the registry documented in the article below should resolve the issue:
https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications#UpdateInProgress

[Prevent the end-user from opening an application while the application is updating]

Ah, ok.

This issue is caused due to the "Prevent the end-user from opening an application while the application is updating" being enabled in Manage Conflicting Processes



To give you more details.
To prevent the end user from opening the software during the upgrade, we use the Image File Execution Feature.
Before the install, a registry key is set to block the end user from starting the software.
That registry key will be deleted after the installation is successfully completed.
If something goes wrong in between, the process will not get to the end, and the registry key will not be removed.

You will have to remove a registry key from that device to resolve the issue.
You can find more info here

I would recommend unchecking that setting in your "Manage conflicting processes" setting.
Please note that this will only take effect when a future version of the software is packaged.
If you decide to update your configuration and would like the change to apply with the already published version(s), please delete the win32 apps from Intune and package them again using our product.

Hello Sean,

I have not seen any issues in support related to Edge.

What is the issue you are seeing?
Does the install fail on devices? Or does it break functionality on some devices?
If the installation fails, I would recommend opening a support case, as we will need logs to investigate the issue

hi mguenth83,

I'm sorry, I don't understand the question. Can you please provide more details?

hey Muja,

You can right-click on "Windows Subsystem for Linux (MSI-x64) and choose the "Modify Command Line" right-click option.


Depending in which platform our tool is packaging the software, a republish might be necessary.
Please see this KB article for more details:
https://patchmypc.com/when-and-how-to-republish-third-party-updates

hey markburkett,

The current version of the Home Updater does not integrate with SCCM. It's meant for personal use only, with a UI you have to directly interact.

Our Enterprise solution is meant for such integration.
We have a personal lab subscription you could use in a lab with up to 25 devices.

With release 2.1.27 of the PMPC Publisher, Workflows are now supported for Teams notifications.

Apologies for misunderstanding your initial ask.

You are correct, the argument you found in the meantime is the right one.
Linking the MS doc, in case it's needed by anyone else too.
https://learn.microsoft.com/en-us/windows/wsl/basic-commands#set-default-wsl-version

Hello muja1913,

The version of WSL we currently support is 2.2.4.0.
You can see that by right-clicking on the software in Patch My PC --> Show Package Info.