InTune App Deployment - Python - User Install Behaviour

[Bankesy]

Good morning,

 

Hoping somebody can point out to me where I'm going wrong here regarding the deployment of Python 3.10.5 via InTune.

 

After reading another forum post elsewhere I've got as far as setting up the deployment as a Win32 app in InTune using the 'User' context, at first AppLocker was preventing the install from taking place but I've got over this hurdle only to find that when users log in and InTune does it's thing they are presented with a UAC prompt for admin credentials to finish the install. I'm assuming there is a setting I'm missing somewhere in InTune to prevent this?

 

I've tried deploying in the 'System' context but InTune doesn't appear to like that for Python and just complains that it cannot find the path specified even though all the other settings remain the same as the 'successful' user context deployment.

 

Any help greatly appreciated.

 

Thank you

[DalekSec]

In the install command we have:

 

python-3.10.5-amd64.exe /quiet InstallAllUsers=1 PrependPath=1 Include_test=0

[Bankesy]

Good afternoon,

 

That's the install command you use for Python 3.10.5 in InTune as a Win32 app for a 'User' context deployment?

 

I'm sure I tried that but will look again, I obviously recognise that command from their documentation and from when I've deployed in the past using MDT.

 

Thanks

[DalekSec]

win32 system context, i found user context to be very flaky in intune unless its a store app.

[Bankesy]

@DalekSec

 

Interesting, when I deploy it as Win32 system context I get the "Cannot find the path specified" error in InTune.

 

I wonder if I've got something wrong in the rest of the setup like the uninstall command or the detection rule, would you be happy to share how you configured these parts?

 

Thank you

[Bankesy]

I fixed it, turns out in the system context I had an incorrect path for the detection rule.

 

Not realising that "python-3.10.5-amd64.exe /quiet" puts the files in a different place to the whole install command above.

 

I think I also misunderstood what the file detection rule is there for, in my mind it was saying "file exists so don't deploy again" when actually I gather it looks at the file detection path post deployment to report a successful install.

 

That would explain why using ""python-3.10.5-amd64.exe /quiet" was installing the app but throwing a failure error because the command does actually work but puts the files somewhere different to where the detection rule is looking.

 

Thanks for your help.