Tech Community Live: Microsoft Intune
Mar 20 2024, 07:30 AM - 11:30 AM (PDT)
Microsoft Tech Community
SOLVED

Unable to deploy app to device, rather than user context

Steel Contributor

Unsuccessful in my attempts to deploy an MSI via Intune. I want to target the device context for deployment, but the drop-down to select this option is disabled in the Intune assignment GUI. There is a caveat about device context installs not being available to Windows 10 prior to 17134.81/May 2018 release, but that doesn't apply here, since the devices I'm attempting to assign are past that build. Any ideas?

 

intunedevicecontext.png

 

Thx,

Bob

3 Replies
best response confirmed by Bob Manjoney (Steel Contributor)
Solution

Hi Bob,

 

your problem is based on the MSI itself. The MSI can have properties to control execution context:

 

2018-07-16_11-30-04-1.png

 

Here an example based on 7-zip, during upload the MSI itself will tell you what is available:

 

2018-07-16_11-30-04-1-2.png

 

And during configuration you can limit this to a certain context then:

 

2018-07-16_11-30-04.png

 

I guess your MSI package has a defined user execution context.

 

Can you check this please?

 

best,

Oliver

I would like clarification, also.  

 

"Note

Deploying MSI over MDM in device context is not supported yet on Windows 10 devices."

 

From this article:

https://docs.microsoft.com/en-us/intune/apps-windows-10-app-deploy

 

 

Hi. Please check MSI property ALLUSERS:

 

ALLUSERS=1 for Device Context

Remove property ALLUSERS for User Context

ALLUSERS=2 enables to choose context from dropdown list

1 best response

Accepted Solutions
best response confirmed by Bob Manjoney (Steel Contributor)
Solution

Hi Bob,

 

your problem is based on the MSI itself. The MSI can have properties to control execution context:

 

2018-07-16_11-30-04-1.png

 

Here an example based on 7-zip, during upload the MSI itself will tell you what is available:

 

2018-07-16_11-30-04-1-2.png

 

And during configuration you can limit this to a certain context then:

 

2018-07-16_11-30-04.png

 

I guess your MSI package has a defined user execution context.

 

Can you check this please?

 

best,

Oliver

View solution in original post