Roland/Assetmanager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update

Browse Source
This commit is contained in:
Roland
2026-09-23 21:20:11 +02:00
parent 4567df7ebb
commit c187b0c45e
14 changed files with 743 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SETUP_ANALYZER.md
+8
View File
@@ -36,6 +36,14 @@ Version 0.5.5.77 can also create a persistent AssetManager software package dire
Software-package jobs transfer only the files required for the selected action through MeshCentral, run the generated PowerShell wrapper, and use the normal AssetManager callback/status/retry infrastructure.
## Post-install application start
A package can optionally start an application after a successful install or reinstall. The launch happens only after the package detection rule confirms that the software is installed. Because deployment jobs execute as SYSTEM, AssetManager uses the active interactive Windows session and the logged-on user's session token to create the configured application there.
If no interactive user session is active and **Start only when an interactive user is logged on** is enabled, the application start is skipped without failing the installation job. Application launch is also skipped when the installer reports that a reboot is required.
For known packages, Setup Analyzer can prefill the application path. Greenshot uses `C:\Program Files\Greenshot\Greenshot.exe`.
## Installer process handling
Generated installation scripts no longer use `Start-Process -Wait` for the installer. They start the installer process, wait only for that specific PID with a configurable timeout, and then evaluate its exit code. This prevents a browser or another long-running child process launched by the installer from keeping the PowerShell script open indefinitely.