Install User-context App via Intune in V4

Hello everyone!

I am installing “HIT Phone” via Intune.

my code installation is "Start-ADTProcess -FilePath 'HIT.Phone-1.0.43.Setup.exe' -ArgumentList '/S'"
when running locally, it installs properly, but then when installing via Intune it don’t install
In intune I am installing as “System context” i’ve tried as “User context” but keeps not installing

even i’ve tried like this command:

$LoggedOnUser = Get-ADTLoggedOnUser

Start-ADTProcessAsUser -SessionId $LoggedOnUser.SessionId -FilePath 'HIT.Phone-1.0.43.Setup.exe' -ArgumentList '/S'

And nothing. Any clue how to install this application in user context?

Thank you so much

If the HIT.Phone-1.0.43.Setup.exe must run AS THE USER and it’s the only installation step, then installing as the user is the way to go.

If you are telling Intune to user in the “User context”
You MUST also do the same for PSADT by modifying the Config\Config.psd1 file.
RequireAdmin = $False

Making the HIT.Phone-1.0.43.Setup.exe create a log file could also be useful.

I will try RequireAdmin = $False
But it’s weird because locally i run the PSADT as powershell admin and everything works fine.

but yes, i will try that approach

I have another question if you can help,
I already followed your suggestion and it worked, but now when i install it via intune before the installation a window CMD is prompted, i guess it’s because of using Service.UI

my install command via intune is .\ServiceUI.exe -Process:explorer.exe Invoke-AppDeployToolkit.exe
When i use this command via System-context that CMD window does not appear but in “User-context” that windows display.

Do you know why?
Thank you so much

Never mind, I just removed ".\ServiceUI.exe -Process:explorer.exe " from the command.
Thank you so much That-Annoying-Guy

yah. ServiceUI.exe is a pain.

Only works elevated AND with a user logged-in.
No User? Blows up and you get no install or even a log file.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

Agreed - user context apps should always be deployed in user context, rather than trying to execute a process as user from the system account. And when you deploy in user context, the process is visible, so ServiceUI is no longer required.