Click Publish (in the Command Queue) to display the Publish Task window.
900
Set the task parameters section
...
For example if you set a task to be played every minute with an occurence validity of 30 minutes, once the first execution of the task starts, it will play every minute for 30 mminutes.
Once published, the Task is stored in the Recurring Task section of the Library. proVconnect will then automatically create and publish occurrences of the Task according to the defined settings
In the Instant publication section, you choose
...
The publication stop date is the date and time at which you want the task to stop playing
If left empty, the Task will remain active unit all the agents complete the Task.
If a date is defined, the Task will be stopped after the specified date, ensuring no other devices process the Task after the date. If at least one agent did not complete the Task within the execution period, the Task will be marked as Obsolete.
The validity duration is the confirmation of the time during which your task will be valid based on the publication start date and the publication stop date.
Choose the target devices section
...
Set option section
...
You can choose to Wake up the targeted devices. If this option is selected then a WoL instruction will be sent to the selected devices. Please refet to the Wake-on-Lan information in the Session & Alimentation section of the Interact Menu page.
If the Wake-On-Lan option is enabled and at least one unit in the pool of target devices is powered on, that unit will send a Wake-On-Lan network event to other units in the pool. For further information, please refer to Wake On Lan page within Advanced section.
Scheduling
The Task can be set to be executed immediately or at a later time. To schedule the task to run later, modify the Publish Start field.
An end date can be defined using the Publish End field.
If left empty, the Task will remain active unit all the agents complete the Task.
If a date is defined, the Task will be stopped after the specified date, ensuring no other devices process the Task after the date. If at least one agent did not complete the Task within the execution period, the Task will be marked as Obsolete.
...
When managing units that are not in the same time zone, it can be difficult to determine what time the Task is performed by remote devices. The Expected Execution Date provides the expected completion date based on the device's time zone. Modify the time zone according to the remote device's time zone.Recurring Tasks
To make a Task recurring, tick the Recurring Task check box on the Publish Task window. Once published, the Task is stored in the Recurring Task section of the Library. proVconnect will then automatically create and publish occurrences of the Task according to the defined settings.
Choose Target Devices
proVconnect offers three different ways to select the devices for the task.
Selected devices
These are the devices chosen using the tick boxes available within the Device List.
Current View
These are the devices currently displayed on the first page of the Device List.
Select groups
These are all the devices within the selected groupsYou can also choose to Send an email when the task is finished. If this option is selected then you have to choose the email groups you would like to send the mail to once the task is finished. Note that the confirmation email will only be sent once ALL the target devices have executed the task.
Progress Legend
...
| Scheduled |  | Task is planned but not yet published; the start date is in the future |
| Published |  | Task is published; the start date has passed but no agent has collected the task yet |
| Processing |  | Task is processing; at least one agent has collected the task |
| Stopped |  | Task has been stopped; no more agents will collect the task |
| Completed |  | Task is over; all agents executed the task without errors |
| Unpersisted |  | Task is over; all agents executed the task without errors but the Write Filter was not deactivated |
| Failed |  | Task has failed; at least one error occurred |
| Partial Failed |  | Task has failed; at least one error occurred but the Write Filter was not deactivated |
| Obsolete |  | Task is over; the End date was reached |
...