Combining line-of-business (LOB) with Win32 applications.


We currently have a LOB application which is published with the “Required” assignment to a group: “OldApp group”.

Recently, a newer version of this application was released and so I created a new Intune Win32 application package for this application.

My reason to create a Intune Win32 application package instead of a LOB application are the added functionality (such as: Supersedence and Depencies) in the Win32 application packages.

This “NewApp” was published with the “Required” assignement to a new group: “NewApp group”. Now the endpoints are receiving (using “Required” assignment) two applications: 1. OldApp (LOB)
2. NewApp (Win32)
It seems that the LOB application take precedence over the NewApp.

I already tried to add the “NewApp group” in the OldApp “Required” assignments and changed it to “Excluded”. I also tried tried to add the “NewApp group” in the OldApp “Uninstall” assignments as included group.

None of these helped. I still have the old LOB application. Are there any suggestions/guidelines when it comes to: combining LOB and Win32 applications?

Answer ( 1 )

  1. I think the combining LOB app with Intune Win32 s not supported as per Microsoft. Even though I tried it on many occasions and worked fine. But your situation is somewhat complex and this is where Microsoft will say let’s try to avoid this kind of mixing of LOB app and Intune Win 32 app deployments.

    I also see complex scenarios or unexpected behaviors because of combining both Intune Win32 and LOB in Autopilot provisioning scenarios.

    This could create some confusion (in the ESP scenario) when you use dynamic AAD groups (not the Autopilot provision ones because those AAD groups will get pre-provisioned).

    Note from Docs

    If you mix the installation of Win32 apps and line-of-business (LOB) apps during Autopilot enrollment, the app installation might fail. The Intune management extension is installed automatically when a PowerShell script or Win32 app is assigned to the user or device.

    For the scenario when a Win32 app is deployed and assigned based on user targeting if the Win32 app requires device admin privileges or any other permissions that the standard user of the device does not have, the app will fail to install.

Leave an answer

Sorry, you do not have permission to answer to this question .