Package Manager Components vs Intune/MS Endpoint Manager Apps clash

Question

Does anyone else have this issue, during deployment of PMC Package Manager in Intune Autopilot & MS Endpoint Manager OS Provisioning, it downloads the 2 components, the client and the cloud adapter and then when other Intune/MECM MSI packages are coming in, there is error 1618 (Another installation is already running), this can happen vice versa, depending which tool runs the MSI first, Package Manager or Intune/MECM.

We are currently thinking of getting rid of Package Manager and use these deployment tool to install these 2 components, so such a clash doesn't happen. But if anyone else has better ideas, most welcomed.

Jens Hansen · Answer

I don’t see that as an issue—you are attempting to perform two installations simultaneously, which is causing an error.
You have multiple solutions to resolve this issue:
- Push the Package Manager as the final step of your build process.
- Use a script to check if the Windows Installer is available before starting new installations when installing from Intune.
- Deploy without using the Package Manager.
Additionally, ensure that policies are not enforced for specific versions of the EPM components, as that is likely to create issues. The Package Manager is the only component you do not control. When BT updates your PM Cloud instance, it will also update the package manager.
I really like the Package Manager, but I also recognize that there is always some risk when using software that auto-updates.

Reply

Badge Earners

Reply

Badge Earners

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded