I've noticed in a powershell remote session a couple of installers that I want to install silently aren't performing their installation. I would like to understand if there's a logical explanation to what is happening.
I have a handfull of (windows-) machines that I need to adminstrate remotely. One of a common element is installating software packages. Some of the packages are based on install shield (exe + cab files). I have recorded an instruction file, and playing back the instruction file is working when run directly on the workstation.
When I run the commands through powershell remoting session the (install shield) log file states there were no errors. However the software does not actually get installed. When I run the same commands in psexec terminal the software installs without problems.
I have encountered one element in powershell remoting that I suspect could be relevant, from an powershell remoting session it seems I am unable run commands that require being run under different credentionals (impersonation?). For example Start-Process with credentionals always failed, likewise runas /user:... failed. I believe what could be happening is that install shield requires running some elements as a different (system-)user and runs into same problem internally.
That being said, I would like to know what is happening and if there's a solution to this problem. It seems to me that powershell remoting is very unreliable if it prevents installing thirdparty software packages.
Just to clarify: Software based on msi packages that I can execute directly through msiexec install without problems. It's specific to InstallShield based 'setup.exe', unfortunately I haven't had any luck unpacking the software to another format but I'd prefer solution for the underlying problem so when I perform ad-hoc commands I can rely on their output.
