Event order in an Installer Session
- Jobs with the setting Installer Run: Start are executed first
- Jobs with the setting Installation: Start of first package are executed as soon as the first package has to be installed.
- Jobs with the setting Opening a repository are executed before the first package from a repository is executed. These jobs are executed only if the calling package resides in the same repository as the called package.
- For each Software Set the jobs with the setting Software Set Execution: Start of a Software Set are executed.
- Jobs with the setting Package Execution: Start are executed at the start of each package.
- When finishing a package, installation jobs are executed depending on the result of each individual package installation. The following jobs get executed:
- Package Execution: Success for successful packages
- Package Execution: Error for failed packages
- Package Execution: Abort for packages terminated with ExitProc(Undone)
- Jobs with the setting Installation: End of last package are executed after the last package of an installation sequence has been installed.
- Jobs with the setting Installer Run: End are executed at the end of an installer run, regardless if a package got executed.
This order can differ in certain events:
- Whenever an error occurs (e.g. when a package is installed or during the installation of packages, for example during package reporting) , the jobs with the setting On error are executed.
- Jobs with the setting On error are executed immediately after the command that caused the error and not when the package installation is finished.
- In some cases, jobs with the setting On error have to be called several times while a package is installed.
- If a package or a Software Set contains a component that has to be executed or if a package has to be called from another package with RunEScript, the jobs with the setting Package Execution: Start are executed for the called package. All other jobs which run for normal packages are also executed for the called package.
Remarks:
- The jobs with the setting Installer Run: Start and Installer Run: End are not executed in the Software Shop. They also do not cause the Installation: Start of first package and Installation: End of last package jobs to run.
- The following job types are treated as regular packages in the sense that they cause other job triggers like Installation: Start of first package and package triggers like Package Execution: Start to run:
- Time: AutoInstaller Interval
- Time: At every login
- Time: Hourly
- Time: Once a Day
Executes once a calendar day if the activation time of the policy has been reached.
- Time: Every 24 Hours
Executes only if at least 24 hours have elapsed since the last execution.
- Time: Once a week
Executes once a week if at least 168 hours (= 1 week) or a multiple thereof have elapsed since the activation time of the policy. - Time: Every 7 days
Executes only if at least 168 hours (= 1 week) have elapsed since the last execution.
- Reinstallation of a Computer: End