{{ computer.notes }}
Starts a scheduled task that is already registered on this computer. Each task runs in the security context its own definition specifies.
These actions take effect immediately on the live computer and cannot be undone from here. A Dell update run can reboot the machine and may interrupt the person using it.
{{ tool.warning }}
Computer not found
Hold
ShopDB normally keeps this computer matching its policy. If policy says a service should be running and someone stops it, ShopDB starts it again automatically.
A hold pauses that automatic correction for the actions you tick, so you can work on the machine without ShopDB undoing your changes. It does not change anyone's permissions, and on its own it does not stop you or anyone else running those actions by hand. Each one can be released separately afterwards.
Give it a time and automatic correction resumes on its own when that runs out - you do not have to remember to turn it back on. Set the time to 0 and it never resumes by itself: the hold stands until someone releases it here, and nothing will prompt anyone to do that.
Lock
Locking is separate, and it is about PEOPLE rather than policy. A hold stops ShopDB correcting the machine; a lock stops other users touching it. While a lock stands, nobody but an admin can run any action against this computer - they are refused and shown your reason instead.
A lock never expires, so use it when the machine must be left alone for reasons ShopDB cannot see - mid-repair, a validated part running, an audit in progress. It stays until an admin unlocks it from this page. Agent check-in and monitoring keep working throughout; you do not go blind on the machine.
Nothing on this computer is under automatic policy enforcement right now, so there is nothing for a hold to pause. You can still lock it below.
0 means indefinite. Policy enforcement for the actions above stays switched off until someone releases it by hand. Nothing will remind you: the computer will keep reporting healthy while it drifts out of policy.