Eight checks for managing an office server
Eight checks for a physical office server: where it sits, cooling, capacity, updates, cabling, admin access, restore tests and power.

An office server needs attention even when staff rarely see it. Its location, power supply and maintenance arrangements can matter as much as the software it runs.
Use these eight checks to review a physical server with the person responsible for it. For each one, note what you found, anything that needs fixing and who’ll fix it.
1. Check the installation
Use an enclosure and mounting method suitable for the equipment. Keep access routes clear and protect the server from spills, accidental unplugging and tampering.
Follow the manufacturer’s installation requirements. A rack-mounted unit and a tower server don’t necessarily need the same enclosure or orientation.
2. Confirm cooling throughout the working week
Check the permitted temperature range, ventilation and airflow direction for your model. Make sure an enclosed cupboard or acoustic cabinet won’t trap heat.
Find out whether building cooling stops overnight or at weekends. Agree on alerts and safe shutdown arrangements if the temperature rises. If the room needs its own cooling, get an HVAC contractor to look at it, and expect a new unit to need an electrician too.
3. Investigate capacity before buying upgrades
Review processor load, memory pressure, storage space and storage performance during the tasks that cause delays. Compare the results with normal operation.
A high reading doesn’t identify the cause by itself. Check application behaviour, storage faults and recent changes before adding hardware. Size any upgrade for the growth you expect over the rest of the server’s life.
4. Maintain supported software and firmware
Keep an inventory of the operating system, applications, firmware and support dates. Assign responsibility for evaluating updates and scheduling installation.
The Cyber Centre’s update guidance explains why patching needs ongoing attention. Before each update, know how you’d roll it back, and check the main applications still work afterwards.
Don’t remove unfamiliar software without confirming its dependencies and owner.
5. Label cabling and document connections
Record what each important cable connects and keep labels consistent at both ends. Maintain a simple diagram that another technician can understand.
Support cables without obstructing ventilation or putting strain on connectors. Plan a change window before moving connections, especially when the same equipment supports phones or other office services.
6. Review administrative access and alerts
Identify who can administer the server and how they connect. Limit privileges to the work required, protect remote access and remove obsolete accounts.
Check which logs and alerts are reviewed, by whom and during which hours. Choose security tools that support the server’s operating system and applications.
7. Test restoration of the service
Check that backups cover the required data, application configuration and recovery dependencies. Protect copies from the same access that could damage production.
The Cyber Centre’s backup guidance is a useful reference. Test restoration in a safe location, then verify that the application can use the restored information.
A backup job can report success and still leave you unable to bring the server and its applications back.
8. Review power and maintenance ownership
Check the uninterruptible power supply’s load, battery condition and shutdown integration. A UPS buys time to handle a power interruption. It won’t keep the server running indefinitely, and it doesn’t replace a backup.
Record service contacts, warranty details, replacement options and the next maintenance review. Include what happens when the usual technician is unavailable.


