Open System Tools
In the EPAdmin administrator workspace, open System Tools or search the exact tool label. Destructive service/process changes require current identity, exact plan and verified read-back. Read the detailed operational guide before making changes. The table lists every requested leaf in this group. A connected destination remains subject to current local permissions, resource ownership, installed capability, licence and fresh verification. It is not a production acceptance claim.
Complete tool reference
| Tool | Destination and behavior | Permission or limitation |
|---|---|---|
| Restart Services | Server → Builder; server services section | Any listed local Admin grant: server:read, server:manage |
| Reboot Server | Server → Builder; server maintenance section | Any listed local Admin grant: server:read, server:manage |
| Server Information | Server → Builder | Any listed local Admin grant: server:read, server:manage |
| System Diagnostics | ServerLogs → Diagnostics | Any listed local Admin grant: server:read, server:manage |
| Process Manager | Server → Builder; server processes section | Any listed local Admin grant: server:read, server:manage |
| File Permissions Repair | Unavailable in this checkpoint | General file-permission repair is not implemented; only existing typed ownership-safe file controls may be used. |
| Configuration Backup | Installation | Any listed local Admin grant: installation:manage |
Make and verify a change
Select the intended owned resource and load its current detail. Read impact, current revision, applicable preview and confirmation before an explicit submission. If the server requires fresh authentication, complete its password/MFA flow and submit the reviewed request again; no write is automatically replayed. Keep the durable operation ID and inspect the final resource/service state.
When a tool is missing or denied
Check the current role/grants, installed version and actual capability. A menu label marked unavailable has no supported action to force. Source updates can be newer than your installed kit; they do not automatically add hosting acceptance. Preserve the safe operation/correlation reference and inspect original state before retrying an interrupted change. Do not disable confinement, modify private journals or substitute another account to bypass denial.