CONFIGURE INNO SETUP INSTALL
Now it behaves exactly the same regardless of how the install is initiated, and no user interactable SYSTEM context components are being created.
CONFIGURE INNO SETUP UPDATE
Just to update this, I've now been able to resolve this by setting my DT to run the installer/uninstaller as a 32bit process on 64bit clients. If I remotely execute the same install via a tool like Client Center (also while a user is currently logged in to the system), then the application installs as desired with no automatic launching of the application via the Inno setup or visibility to the logged in user.īefore creating an SCCM Application I also tested this same installation script via a Scheduled Task running as SYSTEM and this also behaves as I want it exactly the same as executing the install via Client Center.Īm I missing something obvious as to why the exact same DT is behaving differently depending on how the install is initiated? I can't see how with my DT configured to install for the system with no user interaction that when installed directly from Software Center I'm ending up with user interactable components which are running as SYSTEM.
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.
CONFIGURE INNO SETUP MOD
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?
0 kommentar(er)
