Applies for EMv6 & EMv7.
Similar to the "SCCM" section, the "EM" section also provides push installation and mass rollout options. As opposed to SCCM, no applications, but rollout plans are selected (additional information on rollout plans can be found under Packages - EM - Rollout plans or here).
The "Push tasks" overview is used to view tasks that have already been created and to edit these tasks.
You can use the "New Task" option to create another task. In a first step, you must define on which computer the task shall be applied and specify the rollout plan to be executed. Then you define the visibility mode for the user.
In Step 2 you must define whether the log files shall be collected or not and whether remote download shall be allowed or not.
Remote Download: This field refers to the installed EM distribution point, which can be a home DP or a remote DP. This setting is automatically assigned during installation and stored in the XML file of the distribution point. If remote download is allowed, the client checks its home DP to determine whether the required package is available. If it is missing, it checks the remote DP for download. By default, this option is disabled.
Log files: You can either allow transfer of the task log to the EM server or not. If, for instance, a system is shut down after a task has been completed and you open the task log of the client, this log is empty, because the client has been shut down. If you allow that the task log is transferred to the server, the log is also available when the client has been shut down.
The third and last step is to define who shall be able to view the push installation in the console.
For a mass rollout, you must define for which collection the rollout shall be applied, which rollout plan shall be used and in which interval the rollout shall be performed. The visibility mode must also be specified.
The second step defines additional parameters, i.e., how log files shall be handled and the maximum number of bookings per hour. The user can set a time for the EM mass rollout. Limiting the number of bookings limits the load on the EM server. Once the maximum number of bookings is reached, the respective time is not available anymore for other users.
The third step is to define which users shall be able to view the rollout in the console.