If I manually click Install via Software Center then I end up with the application launching itself as SYSTEM which the currently logged in user can directly interact with - incredibly undesirable and it also 'blocks' the installation state because my Start-Process is still waiting for the installer to return. The issue I have is this Inno setup package has a step which will try to run itself after the install is complete even if it is configured to run silently with no interaction (it uses Inno's Exec and ShellExec according to the install log file) the actual issue is that how it behaves is dependent on how I execute the SCCM install.

Within SCCM I've created an Application with my DT set to install for the System with no user interaction or visibility. The reason for using a script is that I want to do some additional post-install configuration for the application. I have an application that is using an Inno setup package, and I am installing this via a simple Powershell script that executes Start-Process -FilePath $setupExe -ArgumentList $arguments -Wait -PassThru -NoNewWindow. As a general rule, if someone has flair, they almost definitely know what they're talking about.

Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.Please send mod mail if you qualify and would like flair set for your account. Flair is reserved for Microsoft employees and MVPs.System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes.

It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?

Inno setup run