We're using PMPC Cloud/Portal, connected to Intune.
I've added a Clean up-tool for Foxit (https://kb.foxit.com/s/articles/14238322642196-Clean-Uninstallation-of-Foxit-PDF-EditorReader-for-Windows) as a dependency to the PMP provided deployment for Foxit PDF Editor. The Clean up-tool is a Custom app without assignments.
This works perfect for the base installer, but the dependency is also applied to the updates. This causes the Clean up-tool to run, and remove Foxit. The update then naturally fails, as Foxit is no longer installed.
Is there a way to exclude the dependency from the Updates only-assignment?
Hi Aleksander, I'm not familiar with that clean-up tool, but you might want to look into our Uninstall-Software script:
https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Uninstall/Pre-Uninstall/Uninstall-Software
This can be added to any application as a pre-install script. The
-VersionLessThan parameter allows specifying the version number you'd like to keep. By doing it this way, only versions that are older than the one specified will be uninstalled. Versions that are equal to, or newer than the version specified will be left alone. If multiple versions might be installed on the same device, be sure to include the
-UninstallAll parameter. This way, you can remove any older version that might be installed, while still retaining automatic update functionality from that point forward. See also:
- https://docs.patchmypc.com/installation-guides/patch-my-pc-cloud/deployments/deploy-an-app/configurations/scripts
- https://patchmypc.com/patch-my-pc-uninstall-software-using-configmgr-or-intune
Quote from: Aleksandergh on February 21, 2025, 03:42:36 AMWe're using PMPC Cloud/Portal, connected to Intune.
I've added a Clean up-tool for Foxit (https://kb.foxit.com/s/articles/14238322642196-Clean-Uninstallation-of-Foxit-PDF-EditorReader-for-Windows) as a dependency to the PMP provided deployment for Foxit PDF Editor. The Clean up-tool is a Custom app without assignments.
This works perfect for the base installer, but the dependency is also applied to the updates. This causes the Clean up-tool to run, and remove Foxit. The update then naturally fails, as Foxit is no longer installed.
Is there a way to exclude the dependency from the Updates only-assignment?
Currently there is not a way to exclude the Dependency from the 'Update-Only' assignments. The dependency will be created for all assignments created for the deployment.
You will need to create 2 deployments, 1 for the 'Install' and another for the 'Update Only'. Then only include the dependency for the 'Install' deployment.
Quote from: Aleksandergh on February 21, 2025, 03:42:36 AMWe're using PMPC Cloud/Portal, connected to Intune.
I've added a Clean up-tool for Foxit (https://kb.foxit.com/s/articles/14238322642196-Clean-Uninstallation-of-Foxit-PDF-EditorReader-for-Windows io games (https://iogames.games)) as a dependency to the PMP provided deployment for Foxit PDF Editor. The Clean up-tool is a Custom app without assignments.
This works perfect for the base installer, but the dependency is also applied to the updates. This causes the Clean up-tool to run, and remove Foxit. The update then naturally fails, as Foxit is no longer installed.
Is there a way to exclude the dependency from the Updates only-assignment?
Instead of applying the Clean up-tool as a dependency for the update deployment, create a separate deployment for the updates that does not include the Clean up-tool. If your deployment system allows it, set conditions for the Clean up-tool to only run during the base installation. This might involve using detection methods or scripting to check if the installation is an update or a fresh install.
I'm in a similar situation with deploying Foxit via PMPC and Intune. From what I've found, there isn't a built-in feature to exclude dependencies specifically for updates in Intune. However, you can try a workaround by creating a dynamic deployment.
You could set up the Clean up-tool as a separate app and assign it only to the initial installation. For updates, you could exclude the Clean up-tool from those assignments by setting up different deployment rings or using a custom detection script to ensure it only runs for the initial deployment, not for updates.
That way, it shouldn't trigger the Clean up-tool during the update process, allowing Foxit to stay intact and updates to complete successfully.