I’m trying to use execute-processasuser because this terrible msi will not accept the allusers flag. so it defaults to the installing for the user who runs the process instead of all users. Here’s my line for execute-processasuser and the app is not getting installed at all.
$PCUser is a variable that gets built from parsing the pc name.
I know it’s not good practice to do so, but in such situations when an MSI is misbehaving, I have had to resort to recapturing it a time or two.
When you’re trying to install as ALLUSERS=1, are you running as SYSTEM account or just with a user with administrative credentials? Some custom actions made by vendors also don’t like the SYSTEM account profile layout.
Installing an MSI for the user can get messy to manage later, particularly if a machine gets recycled or it’s shared and a second user wants to access that MSI.
I am usually using SCCM to deploy or an elevated user id when testing. Does it work with an elevated user account and not via SCCM? I have seen that before but it has been awhile. We used to have a dedicated admin account that we would use for those apps. Or, like you said, you can recapture it. What is the MSI?