Installer WakeUp
With DSM, you can install software at a specified time. Depending on the situation, the DSM administrator has a choice of different options to plan and execute installations. DSM provides various mechanisms to ensure that the actions can be executed as requested.
The following WakeUp options are available:
- Wake up the computer and start the Installer at a specific time in the future (by policy)
- Wake up the computer and start the Installer immediately (by job, when creating a policy)
- Wake up the computer and start the Installer only once at a specific time or immediately (by computer)
Scheduled WakeUp by Policy
When you assign a package to an installation target, you can plan a specific time in the future when you want to wake up the computer and start the Installer; this option is available in the extended settings of the Policy Wizard dialogs.
Be aware that the exact time for starting the Installer is calculated by the DSM Client itself and that the DSM Client controls this process. Apart from the policy settings, the DSM Client also considers other settings, such as the maintenance timeframe. Since the DSM Client gets all the information it needs during client synchronization, a planned start of the Installer must be scheduled after the next client synchronization. If you want to wake up the computer as well, the DSM Client sends the calculated time to the server. The server wakes up the respective computer at the scheduled time.
The following settings are available for the software policy, patch policy and job policy:
- WakeUp Mode
Use this mode to determine how the system wakes up the Installer so that it can execute actions at a specific time. With the Computer and Installer value, the system can run a WoL job when needed so that the Installer can actually start as scheduled. With the Installer value, the Installer only starts when the computer is already running.
The next time the Installer runs on the respective computer, the calculated WakeUp time is determined (see below).
Concerning the WakeUp of the computer, the calculated WakeUp time determines the time when the server actually sends the respective job
You can change the mode any time. The system updates the calculated WakeUp time during the next client synchronization. - Execution time span for Installer-WakeUp (min)
Use the time span for example if you want to stretch the time for starting 1000 computers and Installers over a period of 4 hours. This helps you avoid load peaks. Default value: 240 minutes.
The Position within time span setting (see below) determines the position of an individual computer within a specific time span.
When the DSM Client calculates the actual start time, it also considers other properties than just the activation time and the time span.
The following settings that are closely connected to the WakeUp by policy are available for the computer object:
- Position within time span
This setting defines the position of the computer object during a certain time span (position '1' = the time span starts; position '1.000.000' = the time span ends).
When you update to DSM 2016.1 (or higher), the position is automatically calculated for all available computer objects with the help of a random generator. You can change the value later, if required. If the value is above 1.000.000, the system runs the action after the specified time span. If several computes have the same position, the system runs the action at the same time if the conditions are the same, too. - Calculated WakeUp time (from policy)
This setting defines the time when the Installer must be started on the computer and when the computer must be woken up (if required). The DSM Client calculates this time and notifies the server if the WakeUp mode of a policy is set to Computer and Installer. The calculated time is based on the associated properties such as activation start time, postponement time, maintenance timeframe, time span etc.
The starting of the Installer at the calculated WakeUp time is independent of the regular starting of the Installer (e.g. by polling).
If the DSM Client cannot calculate a matching time from the values used, the property remains empty and there is no planned start.
The administrator may change or remove the calculated WakeUp time in the DSMC. The system overwrites the calculated value during the next client synchronization. Removing or changing the calculated WakeUp time only has a short-termed effect and can be used for actions such as preventing the scheduled waking up of a computer.
The following example shows how the DSM Client calculates the actual WakeUp time:
- Activation time: 10/31/2016
- Maintenance timeframe on that day: 4:00 - 7:00 a.m.
- Time span: 240 minutes (default)
- Position within time span: 581635
- The calculated WakeUp time is 4:00 + (0,581635 * 240) min. = 6:19:35 (local time)
Immediate WakeUp by Policy
Apart from the scheduled WakeUp, you can also specify by policy an immediate WakeUp of the computer (WoL) and/or an immediate installation of pending changes (FastInstall). After storing the policy, the system creates the respective jobs. To prevent too many computers from starting at the same time, you can specify a time span to split up the start times.
These are the same actions you would use for interactive installations on a computer:
Scheduled WakeUp by Computer
The administrator has the option of planning a scheduled WakeUp for an individual computer. The properties of the computer object include specific settings for this purpose.
The following settings are available:
- WakeUp Mode
Use this mode to determine how the system wakes up the Installer on a client so that it can execute actions at the specific WakeUp time. The Computer and Installer value runs a WoL job, if required, and then a FastInstall job to start the Installer. With the Installer value, the Installer only starts when the computer is already running. The system only sends the respective job when reaching the specified time. - WakeUp time
This setting determines the time when the system runs the specified action via WakeUp mode.
The respective jobs are sent no earlier than at the scheduled time. A simple reset will remove a scheduled WakeUp.