Starting with 8.7 SMA is able to quickly install, upgrade or uninstall client plugins without involving policies and tasks.
The information about the plugins that needs to be processed is passed to the agent via install xml file. This is the same install xml that is being used to provide SMA with the connection profile and CEM settings.
Install xml sample containing Deployment Plugin info is below. The important fields include plugin name, version, package GUID, installer's command-line.
There are a few ways install xml can be passed to the agent:
In all the scenarios above the install xml file named AEXNSC.xml is created in the agent installation folder or copied in there and then SMA is restarted. All the scenarios work exactly the same way after that:
Release: 8.7
When quick installer starts at step #11 (see above) it creates the following registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent
The first one is removed at the end of quick install sequence at step #15 and can be used to detect if quick installer is currently running or it was running before and crashed for some reason. The crash dump should be created in the later case.
The second registry entry is meant for plugin installers usage, they use this registry entry to detect if they are running in "quick install" mode and that they should not start or stop SMA service or send basic inventory. The second registry entry is also used by SMA service at step #16 to detect that installation sequence has ended and that it should send the basic inventory.
Quick installer copies both AEXNSC.xml and QuickInstall.xml that were used during installation sequence to "InstallLogs" folder, see sample below. There could be multiple xmls in case quick installation sequence was running multiple times, pay attention to the time stamp in the name. These files are never cleaned up.
Below is the installation sequence sample obtained by using filter "QuickInstaller" in the log viewer. Two plugins gets validated, downloaded and installed.
Loading and plugin validation stages go first - AEXNSC.ml gets loaded, plugins get checked one by one.
Downloading stages go then - two plugins get downloaded one by one, which can take some time, the download timeout for each package is set to 10 minutes, if the plugin download cannot be started in 10 minutes, then that plugin will be skipped.
Then SMA service starts quick installer by passing path to QuickInstall.xml to AEAGENTUTIL.exe using /quickinstall parameter
Quick installer then stops SMA service
Quick installer then validates and installs plugins one by one starting SMA service at the end
Unified policy allows admin to schedule plugin updates via policy, The policy with the specified plugins in the list is processed only once. In order to process the same policy again the admin should change the plugins list.
This policy tracking mechanism is based on a policy run history, which is stored as set of files in "Quick Installer" folder, see below.
Each file name consists of policy GUID and policy content hash. You can force SMA to run policy again by removing the history file.
Each history file contains xml describing the policy rollout result, see below. By matching the time to XML files in "InstallLogs" folder you can find AEXNSC.xml and QuickInstall.xml files that were used during particular policy rollout.
So generally, SMA logs should be gathered from the Agent, and then we can check the mentioned folders if data was generated there.
Also note that only current list of Agents on 8.7 is supporting Quick Install method: