Advertisement

How to Deploy MSI App to Intune MDM Using SCCM CB and Intune

MSI application can be deployed to MDM enrolled clients using new SCCM ConfigMgr Current Branch (CB) and Intune Hybrid. Does MDM enrolled client mean full Intune client? No, it’s not full Intune client rather it’s lightweight MDM client. How do we install/configure Intune lightweight MDM Client? The Intune/MDM enrolment of lightweight client is done by Workplace join (Windows 8.1) and Work Access (Windows 10) -“Enroll into device management – Select this option if you want to enroll into device management (MDM)”. In this post, we are going see to how to deploy a MSI application to Intune MDM lightweight client (via SCCM CB). Video tutorial on “How to deploy MSI application on to Windows 10 machines using Intune MDM client” here.

How to deploy MSI applications to Windows 10 machines using Intune (+ SCCM) ?

Lightweight_MDM_Intune_Client

Navigate through SCCM CB console via \Software Library\Overview\Application Management\Applications, right click and select new application. Select “Windows Installer Through MDM(*.MSI)” as application type and provide the UNC path for application source.

SCCM_Intune_MDM_MSI_Deployment_3

This will automatically detect all the properties of MSI and configure your application similar to normal MSI deployment. The properties which are automatically filled are Installation command line, Detection method and uninstall command line etc..

SCCM_Intune_MDM_MSI_Deployment_4

One the application is created, right click on the application and select Deploy. As this is an MDM MSI deployment, we have to make sure that the package is deployed to cloud Intune DP (manage.microsoft.com) as mentioned in the following screen capture. Rest of the deployment process is very similar to normal deployment. You can select either Available or Required.

SCCM_Intune_MDM_MSI_Deployment_5

Make sure that the content distribution is completed successfully on Intune cloud DP and all other deployment options are configured correctly.

SCCM_Intune_MDM_MSI_Deployment_2

You can login to Windows 10 device with lightweight MDM Intune client and launch either the company portal application or open Intune company portal website ” https://portal.manage.microsoft.com/ ” to install the application. If the deployment option you have selected is AVAILABLE then you have to initiate the installation process from Intune company portal 🙂

SCCM_Intune_MDM_MSI_Deployment_1

About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: ConfigMgr (SCCM), ConfigMgr CB, SCCM 2016

19 Comments

  1. Andrew says:

    This doesn’t seem to work, I can deploy Offline Windows store apps but MSIs don’t seem to work. Are there any logs other then the SSPlog for the Company Portal App? Are there any other requirements that I might be missing?

    • Anoop says:

      It worked straight way for me. I tried without any command line parameters. You should give a try with out any command line arguments.

      KR
      Anoop

  2. Gabriel says:

    Hey Anoop, thanks for this blog post. It helped a lot. I’m having the same problem as Andrew. I can send configuration baselines to the laptop fine but the msi just sits at “unknown”. I’ve tried 4 different deployments. some with switches. some without. A 32 bit and a 64 bit. All distribute fine. The ones sent to a windows phone say “not correct operating system”, which is correct and expected and proves the end to end, but the windows 10 laptop just doesn’t do anything with the 7zip deployment and SCCM just sits at “unknown”. The client check passes though. Is there anything I can check or make sure is setup that I might have missed please? thanks

    • Anoop says:

      Complex command lines are not supported in MDM MSI deployments. Only way is to deploy MSIs without command lines or arguments

      • Gabriel McColl says:

        Thanks for reply , I tried without any switches and it still didn’t work though.

      • Anoop says:

        Oh ok, that is really strange. Is that normal MSI or some EXE is stubbed into it? I hope you have selected the correct option for the deployment and deploying to MDM Windows 10 machines (1607?)

      • Gabriel McColl says:

        It’s just the 7zip msi. I seen another blogger deploy it without problem. Same file. Same setup.
        No switches. Almost no settings changed etc. Just nothing happening.
        Not a special exe or anything fancy. 1.5Mb file

      • Anoop says:

        Have you tried any other MSI or Do you have any other environments to test?

      • Gabriel McColl says:

        Yeah, also tried Google chrome msi. Not got another environment to try but this is fresh built test domain. Very open

      • Anoop says:

        Which version of Windows 10 you are in? If it’s latest try following steps to get more details :-
        1) Open Event Viewer.
        2) Navigate to: Applications and Services Logs->Microsoft->Windows->DeviceManagement-Enterprise-Diagnostics-Provider
        3) Filter on Event IDs: 1900-1930
        4) It will help to know the MSI ProductCode of the app as this is what the events will contain.

      • Gabriel McColl says:

        Thank you again for the replies. It’s v appreciated. I have 0 events with those IDs. No errors showing in that log at all either.

      • Anoop says:

        So you don’t any events related to MSI deployment in the event logs?

      • Gabriel McColl says:

        Not that I can see on the win 10 machine no. It’s very strange since the configuration baselines arrives and applied within minutes

      • Anoop says:

        Windows version? Is that 1607?

  3. Gabriel McColl says:

    Yep 1607
    All showing in sccm. And receiving config items

  4. Gabriel McColl says:

    Heya, I tried this with a different laptop and it worked perfectly. It just be something with the laptop I tried. !
    Thank you v much. Really appreciated

  5. Gabriel McColl says:

    Just to give further update. I removed and reenrolled the original laptop and the msis deployed. Not sure what happened !

Leave a Comment and Contact Anoop