Computer Details
{{ computer.assetnumber }}
{{ computer.computer.hostname }}Identity
Hardware
Location & Organization
Notes
{{ computer.notes }}
Installed Applications
Corporate Tools
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 }}
Run Scripts
Sends a script from the ShopDB script library to this computer. The agent fetches the body by digest and runs it in the context the script itself specifies.
A script here runs as SYSTEM unless it is configured to run as the logged-on user. It takes effect immediately on the live computer and cannot be undone from here.
{{ selectedscript.scriptdescription }}
- Runs as
- {{ selectedscript.runcontext === 'user' ? 'The logged-on user' : 'SYSTEM' }}
- Runs in
- {{ selectedscript.workingdirectory || 'Agent staging folder' }}
This script requires that folder to exist on the computer. If it does not, the run fails and reports the missing folder rather than running somewhere else.
Recent Script Runs
-
{{ scriptRunStatusLabel(run) }} {{ run.scriptname || run.target }} {{ scriptRunTimeLabel(run) }}
- Exit code
- {{ run.resultdetail.exitcode }}
- Ran as
- {{ run.resultdetail.runcontext === 'user' ? 'The logged-on user' : 'SYSTEM' }}
- Ran in
- {{ run.resultdetail.workingdirectory }}
{{ run.resultdetail.output }}The agent reported success but sent no detail. This agent may predate run reporting.
A zero exit code means the script ran and PowerShell exited cleanly. It does not confirm the script achieved what it was written to do. Output is shown for failures, and for successes only when the script is set to return it.
Collect a Log File
Reads a plaintext log from this computer and stores a copy in ShopDB so it can be read here or downloaded. The agent only ever reads the file - it is never modified, moved or deleted.
{{ logpatherror }}
Local path including the drive letter. Plaintext files only (.log, .txt, .xml, .json, .csv and similar). Large files are trimmed to the last 2 MB, which keeps the most recent entries.
{{ activelog.sourcepath }}
- Collected
- {{ formatDateTime(activelog.collectedat) }}
- Collected by
- {{ activelog.collectedbyusername }}
- File last written
- {{ formatDateTime(activelog.filemodifiedat) }}
- Lines
- {{ activelog.linecount }}
- Size on disk
- {{ formatBytes(activelog.filesizebytes) }}
This file was larger than the collection limit, so only the end of it was kept. The oldest entries are not shown.
{{ activelog.content }}
Collected Logs
-
{{ entry.sourcepath }} {{ formatDateTime(entry.collectedat) }}
The 20 most recent collections are kept for this computer. Older ones are removed automatically as new logs are collected.
Computer not found
What this does
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.
The credential for {{ computer?.assetnumber || computer?.name || 'this PC' }} stops working immediately. {{ revokeCredentialOutcome }}