We have pretty much completed our migration from using SCCM to InTune (IT).

However, we are encountering a few apps which hang at certain points during the installation. These have worked 100% falwlessly through SCCM and indeed, if we revive the SCCM deployment, we can install via that route.

I strongly suspect that IT is handling output (STDOUT?) differently than SCCM does, wherein the installer is trying to display a screen but cannot and so just hangs indefinitely.

Aside from the above return-to-using-SCCM work-around, we have occasionally resorted to repackaging the offending installer but this obviously introduces a delay in getting apps deployed to our user-base.

Is there some flag we can set when adding apps to IT that we’re somehow not seeing, or some other configuration we set – maybe at the client-level – to bypass this behaviour?

If you feel like experimenting, grab the Innorix Agent installer which is one that’s causing us grief presently.

​We have pretty much completed our migration from using SCCM to InTune (IT).However, we are encountering a few apps which hang at certain points during the installation. These have worked 100% falwlessly through SCCM and indeed, if we revive the SCCM deployment, we can install via that route.I strongly suspect that IT is handling output (STDOUT?) differently than SCCM does, wherein the installer is trying to display a screen but cannot and so just hangs indefinitely.Aside from the above return-to-using-SCCM work-around, we have occasionally resorted to repackaging the offending installer but this obviously introduces a delay in getting apps deployed to our user-base.Is there some flag we can set when adding apps to IT that we’re somehow not seeing, or some other configuration we set – maybe at the client-level – to bypass this behaviour?If you feel like experimenting, grab the Innorix Agent installer which is one that’s causing us grief presently.  Read More

​