Please see the table below to cross compare GUI and CMDlet operational behaviour.
Operation | GUI behaviour | Cmdlet behaviour |
Move computer from one collection to another | If computer is being moved from the RUM controller that created task, the task will be cancelled for the computer. If computer is being moved from another RUM controller, the task will not be cancelled for the computer. | Remove-RumComputer -> Add-RumComputer The sequence doesn’t stop tasks assigned to the computer. Adding Stop-RumTask in between will not result in GUI behavior since Stop-RumTask cancels the task (when run from the same RUM controller) for all agents. See below. |
Add computer to collection | - | Add-RumComputer works the same way as GUI does |
Remove computer from collection | Removes computer from collection, and stops tasks assigned to it. | Remove-RumComputer Removes computer from collection, and doesn’t stop tasks assigned to it. |
Get computers | - | Get-RumComputer works the same way as GUI does |
Get collections | - | Get-RumCollection works the same way as GUI does with “show only collections created from this computer” option unchecked. |
Cancel task for particular agent when performed from Computers tab in GUI | Task created at the same RUM controller will be cancelled. Task created at another RUM controller will continue running. | Not possible with cmdlets |
Cancel task when performed from Tasks tab in GUI | Task created at the same RUM controller will be cancelled. Task created at another RUM controller will not be cancelled - corresponding menu item is disabled in GUI. | Stop-RumTask Task created at the same RUM controller will be cancelled. Task created at another RUM controller will not be cancelled |
Create Processing, Move and Scripting tasks | - | New-RumProcessingTask New-RumMoveTask New-RumScriptingTask Work the same way as GUI does |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center