ChipPC - Xcalibur W Wiki

For Server 2.14.x & Agent 2.14.x

User Tools

Site Tools


manage_devices:tasks_and_creating_tasks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

manage_devices:tasks_and_creating_tasks [2017/12/21 14:06]
127.0.0.1 external edit
manage_devices:tasks_and_creating_tasks [2018/02/03 18:25] (current)
wpwiki
Line 2: Line 2:
 ---- ----
 One of the mainstream capabilities all management software needs to possess is the ability to send a single command or a series of commands to devices instructing them to perform certain tasks - be they simple or complex in nature. One of the mainstream capabilities all management software needs to possess is the ability to send a single command or a series of commands to devices instructing them to perform certain tasks - be they simple or complex in nature.
-**proVconnect** is fully equipped to issue these commands and to track their status. The functions, commands and command queues that can be constructed within **proVconnect** can be saved as tasks that can be used in isolation or as recurring tasks intended to deliver actions on a repetitive basis.+**Xcalibur W** is fully equipped to issue these commands and to track their status. The functions, commands and command queues that can be constructed within **Xcalibur W** can be saved as tasks that can be used in isolation or as recurring tasks intended to deliver actions on a repetitive basis.
  
 Tasks can be simple affairs, such as asking a series of devices to change their display wallpaper, or they can be slightly more involved, such as joining a domain. Tasks can also be highly detailed, such as running scripts to install applications. Tasks can be simple affairs, such as asking a series of devices to change their display wallpaper, or they can be slightly more involved, such as joining a domain. Tasks can also be highly detailed, such as running scripts to install applications.
Line 33: Line 33:
 After building the Command Queue, command order can be changed by drag-and-drop. Delete commands by clicking the {{command_queue:​cross.png}} symbol. After building the Command Queue, command order can be changed by drag-and-drop. Delete commands by clicking the {{command_queue:​cross.png}} symbol.
  
-By default, all commands will be run concurrently when sent to the device. However, there are circumstances in which commands should run sequentially - one command finishes before the next one starts. This can be done using the Link capability within **proVconnect**’s Command Queue. Notice the Link icon {{command_queue:​chained.png}} in the image at left. The Notification command will not run until the Generate inventory command has completed.+By default, all commands will be run concurrently when sent to the device. However, there are circumstances in which commands should run sequentially - one command finishes before the next one starts. This can be done using the Link capability within **Xcalibur W**’s Command Queue. Notice the Link icon {{command_queue:​chained.png}} in the image at left. The Notification command will not run until the Generate inventory command has completed.
  
 The Command Queue can be saved as a Task Template by clicking the Save icon, located on the top blue bar ({{command_queue:​save.png}}). Name the Task Template, and then click Save Template. The Command Queue will be saved in the Library’s Tasks section. The Command Queue can be saved as a Task Template by clicking the Save icon, located on the top blue bar ({{command_queue:​save.png}}). Name the Task Template, and then click Save Template. The Command Queue will be saved in the Library’s Tasks section.
manage_devices/tasks_and_creating_tasks.txt · Last modified: 2018/02/03 18:25 by wpwiki