Hi - we experience a very strange behavior that we can’t explain… Maybe someone else has seen this before or knows why this happened…
We need to install a pretty complex software - PI Processbook from OSI Soft. The installation has multiple steps in a batch - install.cmd. That batch starts approx. 10 different setups. Some MSI installs, but also some installations using OSISoft’s setup.exe. When we call the install.cmd from a command line in system context or from a administrative PowerShell commandline - everything works fine and all steps in that batch return 0. When we run the same install.cmd (Execute-Process -Path “$dirFiles\install.cmd”) on the same computer from the deploy_application.ps1, then some of the steps in the CMD return 1 instead of 0 (but still successfully installed). We can reproduce this behavior. It’s always the setup.exe that returns a different return code when called from PSADT. Any ideas what can cause this strange behavior? I couldn’t believe it until I saw it reproduced on my VM?!?