Extras · 1 of 4

A typical day

Morning: check backups ran, read overnight alerts, review the patch schedule. Then tickets: a new hire needs accounts, a shared drive is full, an application server is slow. Afternoon is project work, like migrating email to the cloud or replacing a storage array, usually tested in a lab first. Big changes wait for the evening maintenance window. The rhythm is quiet weeks broken by the occasional very bad day when something core fails and you are the person who fixes it.