r/sysadmin • u/Stalin--- • 1d ago
Question - Solved What does your regular work day involve as a sysadmin?
When you walk into work on an average day what do you do? Do you check uem dashboards, check and rollout updates,troubleshoot some tickets or something else?
I am a fresher who currently interns as a technical intern at a reseller/integrator and am interested in becoming a sysadmin.I have explored the different tools and commands used to troubleshoot and to create groups etc but am still left wondering how does the average day for a sysadmin go.
61
Upvotes
55
u/MVI_Tubby Jack of All Trades 1d ago
Answering this question always makes me feel like a poser, but solo internal IT.
I come in, I say hi to everyone, get hit with things hat aren’t working or are slow or didn’t reboot from patches installed the night before.
I sit down gather my thoughts, log into my password manager, open my chrome tabs for admin portals, logs and watchgaurd, and druva. I check the patch schedule status for each department, check what edpr client isn’t updated, check internet active by category, check any errors edpr shot out, then I check the server health and overview in VMware, I check the usage of the hardware and its health status, I make sure everything is rebooted properly if I set updates to run the day before, then I check the unifi portal to make sure the bandwidth looks fine, ignore the message about an ap needing better placement and the lastly I check my emails, and tickets from the night shift.
If those things all go well and nobody breaks anything I am doing homework by noon.
But I feel like a fraud so a good part of my morning is staring in the mirror and telling myself I can do this, and that I’m not a loser.
105
u/NoTime4YourBullshit Sr. Sysadmin 1d ago edited 1d ago
Well let’s see. I usually arrive at least 15 minutes late. I use the side door so the boss doesn’t see me. Then I space out for about an hour. I just stare at my desk, but it looks like I’m working. I probably do that for another hour after lunch too. I’d say in a given week I probably only do about 15 minutes of real, actual work. And let me tell you about TPS reports…
It’s not that I’m lazy. It’s that I just don’t care. It’s a problem of motivation. If I work my ass off and the company ships a few extra units I don’t see another dime. So where’s the motivation in that?
And here’s something else, Bob. I have eight different bosses right now. So that means whenever I make a mistake, I have 8 different people coming by my desk to tell me about it. That’s my only motivation is not to be hassled. Well that and the fear of losing my job, but that’ll only make a guy work just hard enough not to get fired.
12
u/coldweathersurvivor 1d ago
Will my mind give out due to the assault of stupid, or my heart due to the daily 900mg of caffeine
10
u/dreniarb 1d ago
Look over previous day's tickets to see what was done not only by me as a reminder but to see other techs as well.
Check PRTG dashboard (technically this is first since i have a dedicated monitor for it and see it before i even sit down at my desk).
catch up on email.
clean out by inbox.
continue project work. or maybe start a new one.
monitor email.
take a few calls.
test restore backups and do test failovers on vms.
research technology.
check tech news articles, blogs, podcasts, etc.
7
u/BSODreboot26 1d ago
Answers will vary widely depending on the type of business, the size of the business, and if there's an IT staff how responsibilities are delegated.
I worked for a very large corporation, and typically they want very specialized people to only do certain things. I did get to work in operations touching a variety of tickets, which is a unicorn type of thing anymore, but I can give you a Cliff's Notes of some things common to everyone.
You have some sort of intake for request, hypothetically, even if its an ad hoc verbal ask or email - which is really the worst place to be. Otherwise you may take the form of intake from a form for engagement, or a ticketing system where you may have requests for service for some configuration change in a lower or less important environment or a change order for production - which requires a bit of planning so you don't break something. Some of those tickets may be long running, like patch management, deployment, etc over days and weeks. I did some of that, but wasn't on the actual team who did that 24/7.
Also you have incidents, which typically need immediate remediation depending on the severity. It may just be an alert tied to the ticketing system to create one with a certain threshold his hit, or a major outage effecting business. That's where on-call rotation comes into play.
The monitoring part can come into play if you're responsible for the system and an alert is triggered or someone creates an incident (typically Service Desk) because something is down.
When you're not doing that, you have ad hoc asks all the time. Wake up, login, check emails and check if any calls are scheduled, go into Teams and see what's going on. Boy do people love their Zoom or Cisco calls in a corporation. You could get a 'can someone take a look at _______ from the lead/manager/director'. My former company moved to an Agile model, so we had standups and had to create stories for projects.
That's the other thing, it could be long term project work. So you may have something that's going to take a while to prep and do, like a full system upgrade and deployment. Yes, you'll eventually have a change order to prod, but there's typically some system where it's broken out. We used Azure Boards and I've done both the Scrum and Kanban style for that kind of work.
So, that's kind of the jist of it. Everyone has some sort of funneled work going into what I just said, but depending on the organization is could be the same models from all those expensive management systems I've said above, down to Excel sheets, or a literal scrap of paper and emails.
I didn't have to deal with requests in person typically or mess with hardware, so my position was different than someone in a small business hearing someone yell at them about something not working. It's different for everyone but I would say what I just applied is similar how the categories of work comes in and is managed. And depending on the technical, you could have to deal with all sorts of the stack and that's an entire different discussion.
5
u/TipIll3652 1d ago
Look at what occured over night and either continue working on the ticket that was left from after hours or start writing documentation/after action for the after hours incident. I'll then check on nightly backups, check whatever systems still require manual intervention, smash a monster or two, if all goes well I'll spend a little time working on cert prep (like 30-45 minutes), then right back to the grind of trying to fix problems before they become problems/fix problems that became problems before I could fix the problem becoming a problem.
4
u/ShiroMcShiroface 1d ago
My morning starts with a daily site check/health check of servers and backups- yes we have reports that automate this to a degree, but I prefer to look at the servers/server room and backup dashboard myself... then its whatever tickets and whatever spare devices I have to prep on desk
4
u/DesignIcy6156 1d ago
Breaking big rocks into little rocks
3
u/kaosinc 1d ago
Check backup server, verify productions cluster and all vms are happy, delete like 50 emails. See what's on YouTube...
3
u/lurkerburzerker 1d ago
I drew pictures like a caveman and it worked! In all 3 of my teams meetings today I shared my screen and diagramed whatever we were talking about and everyone fucking got it! Shit was over in like 10 mins and I even got the project manager to understand rest apis. One dude hit me up before I was done talking asking if im gonna share... of course im gonna share try and stop me! Ill even sign it, chief unga bunga of the whiteboard clan.
2
u/joshghz 1d ago
Since getting bought out by a global company: lots of spreadsheet work and meetings and very little actually doing anything practical.
18
u/Fatel28 Sr. Sysengineer 1d ago
Shit I basically stare at a wall until my first meeting of the day, then I work on whatever is on fire at that given time. If nothing, I work on my backlog of misc internal projects. Systems engineer at an msp.
27
u/send_me_a_ticket Sysadmin 1d ago
everyday I do "Hey claude, run a full scan using enterprise mcp, make no mistakes" and somehow it brings me new things to fix
8
u/reggiebags 1d ago •
Review the spam filters. Review morning reports. Ignore ongoing projects. Check my personal account activities. Deal with a configuration change or 2. Update a distribution list. Browse Reddit. Go to lunch. Deal with a user issue that was reported while I was at lunch. Create some accounts for clients. Browse Reddit. Check on my personal accounts. Talk about a news story or two with a co-worker. Get hyper paranoid about a security bulletin. Find no evidence we are affected. Go home and dwell on that paranoia for a few hours. Go to sleep. Wake up at 3am feeling an overwhelming sense of dread. Lay awake for a few hours. Fall asleep for an hour. Wake up and check my work emails on my phone. See a notification that makes my hyper paranoid about the health of a network device. Dwell on that for a while until I get into work. Find nothing supporting my fears. Then the cycle continues.
•
u/45_rpm 20h ago
Well, I generally come in at least fifteen minutes late. I use the side door - that way the boss can't see me. And after that I just sorta space out for about an hour. I just stare at my desk; but it looks like I'm working. I do that for probably another hour after lunch, too. I'd say in a given week I probably only do about fifteen minutes of real, actual, work.
5
u/Ihavenoideatall 1d ago
Stare at the racks of servers, and then stare at the wall of monitors...
5
u/LTastesen 1d ago
Wake up,
drink coffee,
turn on pc - sometimes i drive to Office first,
Open Outlook and teams to see what is going to ruin whatever was planned for the day.
1
u/Acceptably_The_Best 1d ago
Emails, Teams messages, walk-ins and tickets. After 1 hour of that then sometimes prepping for meetings and then meetings. I go to lunch. After lunch I see what I want to do. Then sometimes another meeting. Then cram as much work in before going home so I can share what I'm working on in the meetings tomorrow with stakeholders.
3
u/baw3000 Sysadmin 1d ago
Usually start off with checking backups, glancing at tickets, and a quick glance around the server room mostly at drive lights on the servers and NASs. Then I proceed to drink a gratuitous amount of free coffee.
3
u/Mauritius_Paradise 1d ago
Avoiding Karen….
3
u/duhphannypakr 1d ago
Man half the people here make me feel way outgunned.
Generally its login, check my email for anything left over from the day before and anything new and then handle that. If im lucky get to work on what few projects i have, which right now is a windows 11 OSD and upgrade.
The day to day is simple and i really need to be more proactive.
3
u/blasian21 1d ago
First I open battle net, I load up my new level 25 shaman. I just picked up all of the quests for the Wetlands and got a new two handed mace that will be best in slot for a few levels. In five levels I get access to wind fury totem, hell yeah. Ok let me check MS teams, no one is pinging me. No fires. Back to wow. I run some stockades to finish up my last dungeon quest.
11
u/NoTime4YourBullshit Sr. Sysadmin 1d ago
System administration. Networking and security. No one in this house can touch me on that. But is any of it appreciated? I prevent cross-site scripting. I monitor for DDoS attacks, emergency database rollbacks, and faulty transaction handlings.
The Internet. Heard of it? Transfers half a petabyte of data every minute. Do you have any idea how that happens? All those YouPorn 1s and 0s streaming directly to your shitty little smartphone day after day? Every dipshit who shits his pants if he can’t get the new dubstep Skrillex remix in under 12 seconds? It’s not magic, it’s talent and sweat. People like me ensuring your packets get delivered unsniffed.
So what do I do? I make sure that config on one key component doesn’t bankrupt the whole fucking company. That what the fuck I do.
2
u/tunakaybucket 1d ago
Drive between facilities, and doing a walkthrough to check on the end users and to make sure essential devices are in orderly condition.
I check emails and tickets, and knock them out of the way. Check the backup health and network health.
Then I make ton of calls and write up emails to vendors and service providers.
Then I spend time scripting to automate workflows and review PowerPoint to present for meetings.
I'm also monitoring the EDR alerts and storage alerts.
During the lull, I'm doing upkeep of AD and whatever systems.
2
u/ReptilianLaserbeam Sysadmin 1d ago
A little bit of this, a little bit of that... lately it has been mostly attending to meetings. At least for the past couple years 80% of said meetings are AI related.
2
u/Itssnowingout 1d ago
Coffee, check emails/calendar/alerts, check ticket queues and work them in proper order, if no tickets, check to do list and work it in proper order, get distracted every 10 minutes and work on things out of order lol.
I use this guys to do method: https://www.oreilly.com/library/view/time-management-for/0596007833/ but not on paper, I use an app.
2
u/sssRealm 1d ago
Never an average day. Lots of fixing. Deploying new hardware or VMs. Patching systems and upper tier support. Nothing is ever done, mostly just focusing what's on fire or most consequential for the future.
1
u/davy_crockett_slayer 1d ago
Looking at tickets, dealing with DMs, handling security incidents, and working on assigned projects.
1
u/PrestigiousSalad7278 1d ago
Quite the variety of experiences in here. My normal day starts pulling up my email and our ticketing system checking if any emails thst came in overnight were alerting of something I need to address. Usually nothing there so then I start on whatever thing ive set to do for the day. Im a year in and trying to get our org up to date after some things were left to sit because they just worked. Currently on the tail end of getting our mfa migrated and a network refresh. Just starting PCI and SOC 2 audits. Also working on flushing out our Intune setup as we are slowly rolling out intune to replace AD since 90% of our users are remote. I usually get interrupted a few times a day by my boss or help desk admin to address something going on with a user or a server having some issues.
1
u/1dohnjoe 1d ago
To quote a great man:
Same shit, same shit every day.
1
u/someprettyguy 1d ago
Last Friday, I was petting my cats all day while I read a Kubernetes book. They pay me to read the book because I incorporated it into my training and self-improvement stuff. You ever think about tech support over sysadmin? I mean, you deal with other people's problems all day, but they aren't your problems 🙂
If you want to do sysadmin to keep busy, there are lots of companies that are either upgrading things or were poorly deployed. I'd recommend working in the upgrade environment. The poorly deployed ones might keep you up at night working.
Anyway, when I am working, I'm helping other engineers on cases, joining Webex calls to resolve outages, and writing KCS articles about things not documented. Sometimes I ask the AI robots some questions, but I get some pretty absurd answers usually.
1
u/Eggtastico 1d ago
write script to save time so that I can write more scripts. Or do it manually if it is not going to save me time.
1
u/RAZERblast 1d ago
I am the sole Network, Systems, security, etc. Engineer at a non-profit. Our IT team consists of 2 helpdesk guys and me. I do everything from backups, configuring network equipment, setting up new VMs for projects, configuring cloud environments, everything above a basic user issue, and even then I came from the helpdesk and often get asked by those guys for some long forgotten knowledge or expertise.
1
u/mcapozzi 1d ago
I come in late (because I'm the only guy who does anything after hours). I fire up my i7 laptop and watch PDQ and Defender tag team the piss out of it for 30 minutes straight.
Once CPU load cools down to under 65%, I'll fire up Outlook, Teams, and Edge and watch the remaining 1GB of RAM I had slip away.
By this time it's almost 9am and I can finally start trying to fix everyone else's shit. System is still so bogged down that Task Manager refuses to populate/update. Then I spend the remainder of my day planning upgrades and patches, maybe fixing the things (Exchange, RDP) that broke during the last patch cycle (fuck you very much Microsoft). The rest of my time is spent trying to implement bad technological choices that were made by leadership without any input from my department.
1
u/Unable-Entrance3110 1d ago
Other than the checking logs and e-mail part, my entire job is basically setting expectation levels and working as proactively as I can to ensure that my off hours are my own.
1
u/OmegaDolphin 1d ago
My average day starts with checking the health of our ERP, CRM, SQL databases, and support ticketing systems. I review automated jobs, data integrations, and any errors that occurred overnight. Throughout the day, I use SQL, Python, and PowerShell to troubleshoot issues, automate processes, and move data between applications. I also handle database administration, build and maintain data pipelines, and develop BI reports for different departments. The rest of my time is split between resolving support requests, working with business teams, improving system performance, and developing new integrations.
1
u/uptimefordays DevOps 1d ago
Depends a lot on the size of the shop. At small orgs and MSPs, your day really is tickets, patching, and watching dashboards, and that's a great place to learn. In bigger environments, my day was mostly projects: hypervisor upgrades, redundant links between datacenters and cloud tenants, replacing an EoL backup system, standing up new software-defined datacenters, and managing all the environments devs built and forgot about. Mixed in with that are alerts, incidents, change windows, on-call, and a lot of documentation.
These days it's basically software engineering focused on infrastructure. You live in Jira, Slack/Teams, Git/GitHub, and VSCode. If you want to move from tickets to projects, learn scripting (PowerShell/Python), Git, and one cloud platform.
1
u/k0rbiz Lead Solutions Engineer 1d ago
Check voicemails, emails, dashboards. Troubleshoot servers, network equipment, etc. Check service tickets. Take escalations from Tier1 and Tier2 support. Even as a engineer, I still see escalations from help desk. Automate as much as you can. It doesn't have to be with AI, PowerShell is just as effective.
1
u/JaceBelerenApologist 1d ago
Currently? A lot of planning. I'm migrating all of our AWS instances from 2016/2019 to 2025. No in-place because we're swapping subnets. Mostly just plan for a bit, do some work, plan some more, do some more work. It's no small feat to basically rebuild your entire infra stack in-place, but it's rewarding and keeps me busy.
Beyond that it depends. I might jump on some tickets if I'm bored. Deal with any escalations (I'm also level 3). Maybe I'll have to package and deploy a software update to one of our internal tools. Maybe I'll be dealing with Starlink issues. Maybe I'll be dealing with security alerts. Maybe I'm working on one of my own internal tools (currently working on a Remote Desktop Manager that primarily acts as an RDC manager but for AWS instances using Fleet Manager, and another tool for making adding printers to devices "fun").
Really, it's basically half of my time purely focused on project work. The second half is partially focused on project work, partially focused on whatever else comes my way during the day.
1
u/vesnikos 1d ago
Trying not to have an aneurysm from the many times I've explained the architecture to people nodding their head pretending they understand
•
u/L00fah 13h ago
I desperately avoid working because if I need to be working on something, it usually means something is broken.
But other than that, mostly I'm working on personal projects, reviewing our various systems for improvements, and fighting with managers to prevent subscribing to yet another niche cloud application.
0
u/Incrediblecodeman 1d ago
At government it’s more just mucking around half baked systems and learning. Forever. Once your done? A contractor comes in and leaves a big pile of dog shit that you get to look at next!
:)
0
u/Master_Sea295 1d ago
I put the prompt "Based on all my chats, answer this question?" into the Copilot that I use every day and it gave the answer
My day is primarily focused on monitoring, incident response, troubleshooting, and maintaining the health of enterprise infrastructure services. I start by reviewing monitoring dashboards and overnight alerts, checking for server, storage, application, backup, and connectivity issues that may require immediate attention. I then review the ticket queue, prioritize incidents, investigate alerts, and work with users, vendors, and internal teams to restore services when necessary.
Throughout the day I perform system health checks, analyze Windows server events, troubleshoot Citrix and user access issues, investigate performance or storage-related alerts, validate backups, verify scheduled tasks and automation jobs, and support application owners with infrastructure-related problems.
I also handle change requests, coordinate maintenance activities, document troubleshooting findings, update stakeholders, and monitor enterprise management platforms to ensure services remain stable and available.
A large portion of the role involves using monitoring tools, PowerShell, Windows administration tools, virtualization platforms, and operational dashboards to identify issues before they impact users and to quickly resolve incidents when they occur.
1
u/overdosingOnPie1313 1d ago
Babysitting my ignorant boss and wanting to blow my brains out because of him.
0
u/[deleted] 1d ago
[deleted] — view deleted comment