How to get it to work for standard account? (Intune)

[fmiskic]

Hello,

Maybe I am missing the purpose. Is this supposed to work for non-admin accounts? I've tested with an admin account and it seems to deploy fine. As soon as it's a standard user it fails.

I mean I understand why this is the case since the PATH for app installer is default to the standard account of the machine. Once you elevate to an admin account you are running it as the elevated account. The problem with even adding the standard account winget to your path is that it's missing the database.

Any help would be appreciated if I am missing something.

Cheers

[KnifMelti]

Hi!
An installation of a System app via Winget-Install must in Intune be deployed to Users/Clients as Run in System context.
In the Company Portal it can be either Available or Required.
I.e. you must make an application in Intune and assign it...

[Romanitho]

In any case, i would suggest to install for system, except the case the app is not system installable

[fmiskic]

If you add a win32 app in Intune you set if it should install in user or system context. Only apps supporting installing in user context can be run under user context. An app installing in system context can be deployed/assigned to users or clients, but it will be installed for System.

Yes so this is what I mean. For example trying to install Firefox or NordVPN under system context just fails when installing from the company portal. This is on a computer with a standard user. When it was tried with a computer that had an admin account requesting the installation the same script worked.

So is the intention of the script to be able to install from a standard non-admin account? It seems that it's not working.

[KnifMelti]

Very strange...
The intention (how it works) is that of installing apps under System context for all users, otherwise there's no point in it.
I'm installing everything (haven't tried FF/NordVPN yet, though 😉) in our environment...
...could it be the PS x86/x64 @Romanitho

[Romanitho]

I tried to deploy Firefox under system with Winget on a sandbox, and it works. Firefox get installed and detected. So, supported.
Could you share with us the config you have ?

[fmiskic]

I tried to deploy Firefox under system with Winget on a sandbox, and it works. Firefox get installed and detected. So, supported. Could you share with us the config you have ?

Thanks for testing this. Again though is this working with a non-admin account? It worked for me as well when the user had admin.

[KnifMelti]

Intune Deployment with %systemroot%\sysnative\WindowsPowerShell:
Romanitho/Winget-AutoUpdate#88
https://www.anoopcnair.com/intune-win32-app-deploy-system32-vs-syswow64/

[fmiskic]

FF is in a WAU thread too: Romanitho/Winget-AutoUpdate#158

Have you tried the ESR version?

I will give this a try and get back to you.

[KnifMelti]

But @Romanitho used the ordinary FF, I suppose...

[KnifMelti]

Any luck @fmiskic ?

[fmiskic]

@KnifMelti Unfortunately I have not. Once I do I will report back.

[fmiskic]

Any luck @fmiskic ?

It seems the ESR also fails. Same script just Mozilla.Firefox.ESR

[trandall50]

I'm in the same boat. Seems to be the only way to install teams standalone (winget+intune) but looks like it will be all for not if it won't work for a standard user. I was so close with this script but it appears it will be back to the drawing board. I can't believe how difficult it is deploy teams to standard users without installing 365 suite.. I'm blown away.

[trandall50]

Thanks for the link. I was hoping to achieve with winget though

[KnifMelti]

Ok, and that's a problem?
I'm not fond of Intune, using SCCM for application deployment even if we are hybrid joined.
We're using Office, but I'll create a WinGet app for Teams myself and test.
We only have standard users in our environment.

[KnifMelti]

This looks like the one:
winget show Microsoft.Teams.ContinuousDeployment
https://github.com/microsoft/winget-pkgs/tree/master/manifests/m/Microsoft/Teams/ContinuousDeployment/1.5.00.31365

[KnifMelti]

Installed manually via WinGet as a standard user:

[Romanitho]

User context should work yes.

[KnifMelti]

On a Swedish system...

[Romanitho]

You can use hidden powershell (small PS window flashes).
I don't get why the id is not the same on direction?

[KnifMelti]

Tried -NoNewWindow, but that stopped it from working

[KnifMelti]

Ah, -WindowStyle hidden

[Romanitho]

Yep.
You won't be able to use -NoNewWindow as process switches between 32 and 64.

Last shot, use the invisible.vbs from WAU. Same command as user context scheduled task

[KnifMelti]

I don't get why the id is not the same on direction?

Microsoft 😍