Site deployment workflow for T360
T360 is a PowerEdge tower server platform. Begin with the room and workload: estimate compute and memory needs, storage capacity, backup path, network ports, power availability and local service access. A tower chassis is often placed outside a rack, so airflow, cable reach and physical security should be part of the layout.
Configuration map
| Selection point | Specification / confirmation |
|---|---|
| Exact model | T360 |
| Platform | Dell PowerEdge T360 tower server |
| Form factor | 4.5U single-socket tower system |
| Storage | Drive bay and interface configuration depend on the selected chassis build |
| Memory | Confirm installed DDR5 ECC UDIMM population and capacity |
| Power | Choose a supported PSU arrangement for the final system configuration |
| Operations | Plan service access, network uplinks, backup, OS and remote management |
Build selection
For T360, choose the processor and memory to fit the application, then size storage and controller options around performance, redundancy and recovery objectives. Confirm the drive bay type and backplane before selecting SAS, SATA or NVMe devices. Power supply selection must be reviewed against the final system build rather than an isolated component list.
Commissioning runbook
- Inspect chassis, rails/feet, bezel and delivered accessories.
- Confirm service tag, CPU, memory, storage and PSU against the approved quote.
- Configure iDRAC, firmware baseline, time source and management network.
- Install the selected OS and validate storage, NICs, backup and monitoring.
Operations handover for T360
Record the service tag, firmware versions, drive map, controller mode, network interfaces and recovery procedure for T360. Confirm who owns patching, alert review and restore testing. The handover should state the approved system configuration so later upgrades can be compared against a known baseline.
Use T360 and the finalized component schedule as the reference for support and future parts requests.
Keep the exact T360 model and service tag together in the commissioning and asset records. Verify that T360 appears correctly in the installed-system inventory after setup.
