SysAdmin can't do his job right.
Posted by FatMetalJesus@reddit | sysadmin | View on Reddit | 99 comments
So, I have a question. Not SysAdmin exactly but I work for a place that has a small IT team, I have to wear all hats, from HelpDesk, CyberSec, Field, and occasionally NetAdmin, SysAdmin when needed.
Our current "SysAdmin" is absolutely horrendous. He keeps ALL of the passwords, server names, IPs in a Google Sheet. The passwords...omg. EVEN WORSE. I downloaded RockYou to show my Director just how many of our passwords are in that document. None of our servers are secure. He shows up 3 hours late DAILY. I asked for an account on Aruba and got it 2 months later and the password...omg. It was Aruba1234. He acts like CyberSec is TOTALLY pointless and says nobody cares about that role. Said it shouldn't even exist.
What makes all of this worse...we work for a school...When our last NetAdmin left, is when I had to pick up that hat and SysAdmin because he REFUSED to do anything. Kept saying he will just have the new NetAdmin do it when they come in...it took a couple of months for us to find one.
What are ways that we can still do what we need to do, even though the current SysAdmin sucks. We can't do our job if he doesn't do his so we are stuck doing his job and covering for him so we can do ours. But with that said, the higher ups don't see that he's doing anything wrong because his work is being done even if not by him.
Any advice would be LOVELY.
cdoublejj@reddit
wut?
DariusWolfe@reddit
Expand your IT Team.
Then reduce your IT Team.
Then expand it again, because one admin for a school is asking for trouble exactly like this.
r0ndr4s@reddit
Seeing that no one there gives AF , its almost like they want to be hacked. I wouldn't care too much, do what your paid to do and try looking somewhere else in the meantime. Don't cover for him and if anything happens that leads to you not being able to perform your job, just escalate to your superior:
"i can't do this task because sysadmin isn't collaborating with me" and explain in detail how you proceeded, don't let him have a grey area to work against you
Puzzleheaded-Dog-728@reddit
You work for a school
The fix is stop working for a school
Stay out of public services, they are all like this
HotTakes4HotCakes@reddit
Yeah fuck public Services they don't deserve good IT people. Never mind that they're funding is consistently slashed across the board.
Puzzleheaded-Dog-728@reddit
Tax payers get what they vote for. If they wanted a well run system they can fund it better and or vote in smarter people who can effect the change they want to see.
That's democracy, no?
FedUpWithPeople26@reddit
I can attest to that having been a K-12 IT Director and fighting the same battles.
Old-Flight8617@reddit
OP never said it was a public school system.
Way to jump to conclusions.
And also schools, the public ones, have state standards to meet, unlike private schools which often times don't have to.
Merdrak@reddit
I hate to be this guy:
Get clear lines of responsibilities from your supervisor. Do nothing outside those.
Document it all. Requests. Response times. Compromised passwords. Impacts to the ability to do your job.
Back it up with legal documents. FERPA, etc.
Create the paper trail, create the documentation, and don't step outside your role once it's defined. You cannot control what others do. You can control what you track and what is done, and if you have a complaint about a coworker, you have to have documentation to back it up. If the supervisor won't do anything about it after raising the flag, document that as well - dates, times, etc., - so that if anything happens you can say you rang the alarm bells & it was all outside your authority.
This isn't sabotaging someone's career, this is covering your ass. And if you don't cover your ass, you'll be stuck in the shit with everyone else.
gakule@reddit
Ask for clear lines of responsibility and stop doing things outside of your responsibility. Everyone wearing many hats only works if everyone is taking them off the hook equally.
HotTakes4HotCakes@reddit
I don't know, if I were working at a school, that's one environment where I would feel a responsibility to at least try and plug as many holes as I could. It's not about what my job is or isn't, its about the nature of the data and access that needs to be protected.
At least in my experience, this "just take notes as the whole thing burns, and you'll be fine" strategy doesn't work out as well as many people claim it does around here. You can keep all the records you like, but if shit hits the fan, management can also read that as "you knew and did nothing" even if it's not true.
Geminii27@reddit
Which is why you let management know, via a recorded medium such as email. When they try to throw you under the bus, you have the records/printouts.
Itchy_Meaning753@reddit
Spoken as someone that never worked there, imagine 20 years of your budget being cut, insane politics, zero recognition if you work hard, guaranteed union-increases, those environments breed lazy shits by their nature
oddball667@reddit
are you plugging holes? or are you covering them up?
some holes don't get fixed until someone has wet feet
AmiDeplorabilis@reddit
I second this response... WHOLEHEARTEDLY.
marsmat239@reddit
This. Even if it saves you the immediate aftermath the cleanup may likely be given to someone else/outside help as well. The entire team is looked at as ineffective regardless of whether it’s their fault or not.
gakule@reddit
That really wasn't intended to be my recommendation, but I get why you'd read it that way. Get clear lines of responsibility and be able to use that as a document to back up pushing responsibilities where they go, and highlighting ineffectiveness.
It's not 'letting things burn' if you are pushing people to do their jobs.
It's also very possible that what OP is doing is in line with expectations and responsibilities.
Either way, not doing someone else's job for them isn't your problem - it'll be your managers problem to figure out and that very well may be blaming you, but I will whole-heartedly push back on "why didn't you do their job for them?" as if it's your responsibility to manage the team.
Regardless of that, your kid being somewhere that someone works does not require them getting taken advantage of and burnt out to "protect the sensitive nature" of their data, whatever that may be.
gakule@reddit
That really wasn't my recommendation. Get clear lines of responsibility and be able to use that as a document to back up pushing responsibilities where they go, and highlighting ineffectiveness.
It's not 'letting things burn' if you are pushing people to do their jobs.
It's also very possible that what OP is doing is in line with expectations and responsibilities.
Either way, not doing someone else's job for them isn't your problem - it'll be your managers problem to figure out and that's where the leverage point is.
Regardless of that, your kid being somewhere that someone works doesn't necessitate them getting taken advantage of and burnt out to "protect the sensitive nature" of their data.
Hebrewhammer8d8@reddit
I don't know how people can do IT support for schools. It suck big time IMO. The staff are in a school environment of education expecting their students to learn new concepts yet the staff can't learn new processes dropping "I'm bad with technology" the irony.
Natirs@reddit
OP needs to do that. It's unrealistic to wear all hats if that wasn't what you were hired or paid to do. The "I work for a small IT team" is the facade people use to justify having to do a bunch of work outside of the scope of what they were hired to do. I understand the worry about passwords in plain text, no password manager, people not doing their job, but that is the responsibility of your boss. If you come across something that's concerning, you bring it up to your boss and leave it be. When people learn to stop worrying about something that is someone else's job, their mental health becomes way better. If a breach happens or something worse, no amount of running around screaming at the top of your lungs would have prevented it. It was inevitable. I've been there when those things happen and there isn't anything you can do but clean up. It's the job of my boss to make sure their subordinates are doing their job.
gakule@reddit
Careful, someone is going to have to tell you that you need to "manage up" 😑
End0rphinJunkie@reddit
Spot on. As long as you keep quietly picking up his slack management will never see how broken things actually are. Just make sure to get those boundries in writing so you don't take the fall when a breach inevitably happens.
wey0402@reddit
You are still payed even without responsibilities, so sort it out with who ever is needed so both areas can live with it. Sometimes the line can not be drawn the same way in each company.
ShajoSeb@reddit
Honestly, hire an external IT firm to audit the school and oversee the changes. It’s the classic 'prophet in his own land' problem as an insider, you can shout into the void forever and nothing moves. Sometimes you need an outside 'expert' to say the exact same things you’ve been saying before leadership will actually sign off on the work.
Turbojelly@reddit
Document that shit. Don't cover for him during exam season. When he's gone, check the serves and make sure both power supplies are not plugged into the same UPS.
Curious201@reddit
i would be careful about trying to “work around” him too much, because then the school gets the benefit of your work while the risk stays invisible. document the issues in plain language, not as drama: shared password sheet, no MFA where it matters, daily account lockouts, unsecured servers, recurring manual fixes, impact on staff time, and what you recommended instead. then ask for written responsibility boundaries, because if you are touching systems without authority and something breaks, it can still land on you. if they ignore it, keep doing only the work you are actually responsible for and keep a dated record of what you reported. the uncomfortable part is that this may be less of a technical problem and more of a management problem that they have chosen to tolerate.
FarToe1@reddit
Also, if other people are routinely doing his work, the can become "accepted practice" and they'll end up with the blame when the shit inevitably hits the fan. OP should stay in his lane, and complain upwards when stuff backs up.
schkmenebene@reddit
If you have anything you value on your schools system, back it up your self.
I mean, in a proper system, you'd never be able to do that. But I bet he has never considered locking usb ports or blocking exporting of data. So before someone downloads crypto and infects everything on your system, make backups of what you can. Maybe, you can probably take backups of everything and save the day when everything comes crashing down.
A simple backup via usb is better than nothing, I guarantee it.
Don't do his job for him, guy has an outdated mindset around security that simply doesn't work in current times. Maybe it worked in the 90s, when the worst hack was made by a disgruntled ex-microsoft empolyee. But hacking today is literally a billion dollar business and needs to be treated as such.
sadsealions@reddit
Not your problem
Schaas_Im_Void@reddit
I work at a university and it sounds like that sysadmin at your place is the same that was here before me.
It took me a few years to get everything back to order and every single closet, drawer or box I opened had skeletons popping out of.
Ok-Actuator9118@reddit
Sounds about right for a school
junon@reddit
I can't be the only one that immediately clicks these looking to make sure they're not the sysadmin in question, right? Right???
vogelke@reddit
That's your first mistake, because...
Stop covering for him. Do you have any type of cyber-insurance? If so, keep detailed notes about all this and forward them to your insurer, or the state AG. Let him hit the pavement.
disclosure5@reddit
I'll just add that for the reason you described, OP really doesn't get to decide the sysadmin can't do his job, if the person who pays their salary actually decided that they are satisfied with the job.
wey0402@reddit
Just file some changes for relevant work and make it transparent. Assign it to him and follow up regularly, letting the company fail hard is probably not the best option.
sistermarypolyesther@reddit
Agreed. Let him fail.
Ok-Hunt3000@reddit
Welcome to IT! Sucks man I went through it too. Outshine him if you can, idk what rights you have but look for ways to improve the environment despite him, make sure it’s brought up in meetings and eventually your manager if he’s decent will start to see the gap and what you are doing. Do not antagonize him, you just want things done well and securely and are oh so happy to help. Dog his ass out to your manager though, privately, make sure it’s known he’s dropping the ball. My manager was well aware but it starts a dialogue. This kinda relies on having a good manager you’re both under, though. Closed mouths don’t get fed and the squeaky wheel gets the grease, be the grease wherever you can. IT is an afterthought to a lot of the higher ups but if your manager sees what you’re doing and it’s improving the department it’s hard to really argue with.
FatMetalJesus@reddit (OP)
Well, I have SOME pull with the higher ups. But apparently getting rid of someone at a school is a lot harder apparently. My director knows of the entire thing.
Itchy_Meaning753@reddit
It's nearly impossible, and the director will only act if it affects him, stop doing that guys job, let him fail, that will make the dir fail
CharcoalGreyWolf@reddit
It shouldn’t be harder if the employee isn’t union.
SevaraB@reddit
If that's in the US, point out to the boss that the "sysadmin's" comments about security are completely out of line with FERPA guidance. If your school is paying for cyber insurance, and the insurer finds out about those comments, they could deny an insurance claim or even drop you altogether for being too risky to insure.
Itchy_Meaning753@reddit
Reality doesn't work that way at all, insurance will cover them just fine, majority of Public systems are like that, they have to be, because citizens all too often refuse to pay more in taxes to do things right
FatMetalJesus@reddit (OP)
Apparently our insurance knows nothing about cyber. Brought up the FERPA compliance issue too.
HotTakes4HotCakes@reddit
What in the hell insurance is this?
FatMetalJesus@reddit (OP)
Honestly. No idea. I'm afraid to ask. 🤣
We're mandated to do Cyber training (we do phishing tests bc ya know... People click on anything) and we save money by doing it. All I know.
Hot_Direction7888@reddit
You in Maryland? You guys hiring ?
SevaraB@reddit
Which is why you want to approach it holistically in terms of risk management and not just insurance as a specific policy you may or may not have. The point is to get the boss thinking “when something goes horribly wrong, who’s going to get hung out to dry?” The sysadmin acting like cybersecurity in the edu space is an inconvenience to be ignored or avoided is probably one of the biggest insider threats to the school system at this point. FERPA doesn’t dictate specific security controls, but if he won’t play ball with any of their best practices, he should be out on his ass. Let him be someone else’s future ransomware headline.
TheShootDawg@reddit
could be they don’t have cyber insurance, as usually that’s completely separate from the other types of insurance they have. even to the point of a different provider.
ensum@reddit
FERPA is only for public schools/schools that receive federal funding. If OP works for a private school, FERPA technically isn't required (assuming they don't receive federal funding), although most will still adhere to those standards.
Short-Legs-Long-Neck@reddit
CYA. Document this in terms of risk, practises, process, tech. NOT people. Try and capture it as current state of risk, including anything you do, so its not personal. Include proposed solutions and recommendations. Surface to the boss. When it goes pear shaped, make sure you have a copy of this in your personal files.
Its the IT managers responsibility to solve, it's your job to raise it a mature and business like way.
stufforstuff@reddit
To bad one of the hats you're wearing doesn't say "manager" or "director". Until it does, it's not your concern. Do YOUR job, document any problems, and if you don't like the workflow where you're at, move on. I don't understand why people think it's their worries when a coworker that is not under their control doesn't work to their standards - get over it.
doyouvoodoo@reddit
This is a policy and/or management issue.
If a password protection policy is not set or is poorly defined by the organization (policy issue), and/or policy is not being enforced (management issue).
doyouvoodoo@reddit
Ah yes, the advice part. Stop doing their work, and use the ticketing system and or email to document and demonstrate that their inability or unwillingness to do their work is preventing you from doing yours by consistently asking them to do their job.
When a supervisor or manager gets pushy about a fix taking too long or an outage laying too long as a result of this employee, offer to CC them on your follow-up.
nimbusfool@reddit
K12 systems administrator here. Yall are gonna get popped soon or already have. Sounds like he wouldn't even know if your domain were compromised. Plenty of our sister schools have had similar environments and got burned to the ground with ransomeware.
Sometimes you have to let someone fail and fail hard even if it impacts businesses. I was the type to always pick up slack because the job had to get done and I felt responsible even if it wasn't my job to do. Let things fail and work your contract. Keep a paper trail.
kaptejeee@reddit
Talk with your director if he/she don’t care - start applying for other jobs.
It is impossible to re-teach this kind of persons which don’t care about cybersec.
ukulele87@reddit
Is he the brother of the owner or some shit like that?
Or is one of those cant-be-fired gov jobs?
Did a computer murder his wife?
I honestly never seen anything like that, so im trying to find a reason.
m4tic@reddit
Leave. A perfect storm is a-brewin'
Wolfram_And_Hart@reddit
Is your job net sec? Like will you legitimately get in trouble for anything you are doing besides the (hopefully) documented complaints and warnings.
Then you’ve done your job and you just do whatever.
FatMetalJesus@reddit (OP)
Cyber/HelpDesk I'm super close to just sitting by and just answering phones and emails like I'm supposed to. Instead of trying to help the team grow.
Wolfram_And_Hart@reddit
Unfortunately it’s not your job to help the team grow especially if management is resistant. You just become “the difficult one”. You can ride that till they fire you for whatever reason they decide is good enough.
I’ve been you.
You have to decide if you can truly bite your tongue and just do “enough” every day. I never could. I was fired 3 times for stirring the pot in a very small town at some of our biggest businesses. I’m the compliance auditor and privacy officer now. I decide what is acceptable for about 50 businesses currently.
Eventually your company will get hit with a cybersecurity insurance audit. They will have to change their ways or simply be uninsurable.
Eventually, middle management will retire or have a heart attack and they will just farm it all out to an MSP.
Rybro85@reddit
Watch him get promoted or a raise
FatMetalJesus@reddit (OP)
I'm almost certain, that he's going to be on his way out pretty soon. Tomorrow I'm going to the CFO about the tremendous waste of money he is currently.
gearcontrol@reddit
Careful going around your direct report(s), especially if this brings heat down on them.
FatMetalJesus@reddit (OP)
Oh he's not my direct report. Or a report at all. I report directly to our director. Mainly due to A. He would never be there for me to report to. B. I do Cyber as well as HelpDesk C. The hierarchy is kinda fucked. All roles report to the Director by default. We just kinda collaborate as needed.
loweakkk@reddit
How director reacted to the password thing? Did he requested to improve it? If not either you sit on the issue or you find a new place.
You can't do shit if upper management don't care.
Only them can tell you: ok current state is concerning, you are in charge of cybersec now I want an improvement plan by end of the month to validate and monthly reporting.
If you don't hear that, stop caring about it, it's not your job and nobody ask you to ( I know that sucks but you can't do shit without upper management buy-in)
stoltzld@reddit
Hire a pentester to embarrass the shit out of him by locking him out of everything.
urM0m69p3nis@reddit
Somebody is too comfortable. Share the company name; would love to blow a hole in that "pointless Cybersecurity"
Abrelm@reddit
I already feel sorry for you having to wear all of the hats there, feels like that sort of thing which usually ends up with people asking you to fix the coffee machine since it's got a touch display or something, but in a school there's to hope that the janitor will take care of that.
It sounds like a managerial problem too, how come that all of these behaviours aren't reprimanded in any way? What was the Director's response when you showed those documents, just a shrug? Or the whole thing of him coming in late? Either you'll need to show initiative to the point of going way past your job description that might leave you drained, or push for higher-ups taking this stuff more seriously. Gathering evidence/data on his lateness and everything would be another thing I'd start doing.
The petty part of me would just go ahead and evaluate a password manager and start changing as much as I can from that Google Sheet doc and just say "Yeah we're using this now" to everyone else who's not being a stubborn idiot, but with how that person sounds, I bet he'd find a way to change things back and you'd have a terrible case of mismatching password records.
FatMetalJesus@reddit (OP)
We have BitWarden that I'm in control of. I have admin rights across the board. Just about as much as my director. I'm thinking of going into Google and taking the files from his drive and deleting them after I import all of them into BitWarden. Oh, which I have invited him to a couple times already and he's never accepted the invite. Boss is aware of this as well.
doglar_666@reddit
I would be careful about messing with user files, even if you are both admins. Any "securing" of company credentials and information would need signing off by the appropriate Director, whether it is your line manager or someone else. You don't want to go to war with a belligerent SysAdmin. Ideally, you would secure all credentials and audit all devices for remote ingress routes, before rotating all passwords and keys. But you aren't in an ideal situation, so tread lightly. This is how insider threat situations can start.
Abrelm@reddit
That's good on the password front at least!
You could take that Google Sheet and turn it into a csv to batch import it, there might be a bit of fiddling to get the order right into one of the many available formats but ultimately, not too time consuming at all.
You could look into defining a department-official migration date with your director, put in all the stuff into a collection set to read-only for the moment, and once that date comes, yank the Sheets file, set the read permissions to whoever needs them and if he can't access stuff because he ignored the invitation mail and migration date, tough luck. Unless you cleaned him out of the user database already, he should still be under "Invited" and you can just resend the invitation if he complains. As long as it's got the blessing from your director and everyone else is on board, he should no reason to throw a fit. And additionally, you'll have the old passwords in your password history on BitWarden in case there are any odd "switching stuff back without announcing it" shenanigans.
FatMetalJesus@reddit (OP)
Yea, he's still invited. Just had never accepted and heard he's not going to because it's "bullshit"
Abrelm@reddit
I'll never understand these people who use spreadsheets, even the ones with that dinky Excel encryption for passwords in favour of proper password managers. It's got a proper search function, it's organized, properly encrypted and you can even put in 2FA codes. Absolutely ludicrous.
But yeah, I wish you the best of luck with making at least that change official, if everyone else but him is following the changes and going with the times, it'll be another really well-visible sign of him being the outlier on top of the other aforementioned issues. With that mindset of doing everything your own (terrible) way without making compromises in what's supposed to be a team effort it should really bring up some... questions about him sooner rather than later.
Ok-Double-7982@reddit
Fix the coffee machine and hoping the janitor fixes it? Usually the secretary makes the coffee and would be the one who would best know.
Advanced_Day8657@reddit
It's simple. If there are no rules, and he doesn't need to do what you say - then he won't. Some people just don't give a fuck. Practice finding security weaknesses until you find a better job.
Difficultopin@reddit
Leave the company
traviss8@reddit
You guys work in a school? I guess he hasn't had to deal with some smartass shithead who's trying to become a pen tester lmao some kids are constantly trying to hack into shit
plebbitier@reddit
Sometimes, the Sysadmin does bad things because management requires him to do so. I've been there but as long as the paycheck shows up, you do what you are told.
Ok-Double-7982@reddit
Who is managing both of you?
That person (IT director or manager?) does not ensure redundancy within the team with account access? They allow only one guy with the cyber skills of a gnat to hold the keys?
Raumarik@reddit
I was sysadmin for a school years ago, there's no excuse for poor account hygiene. If you've flagged it to a director and nothing happened there isn't much you can do other than ensure YOU work better.
Put your concerns into writing, but be careful as that could see you on the way out - personally if I was being led by a sysadmin that poor I'd look for another job especially if the director did nothing and nobody even cares when they start each day - there's an institutional issue.
HotTakes4HotCakes@reddit
Maybe covertly alert the board or something. If it's a school, it's not a problem that should be left to fester and potentially cause an issue down the line, just so you can say "I told you so".
Byany2525@reddit
stop doing other peoples jobs.. people like you suck to work with
arslearsle@reddit
Worked in a school 20 years ago - 900 students - we had strict security with enforced with certififaces - even back then. Ohh this was in Europe - not US.
gumbrilla@reddit
Ok, I'm not going to condone poor practice, with passwords and the like, but also try to figure out what's actually going on.
I've run into people that appeared like they weren't any good, but that's also because I wasn't their focus and actually they were highly valued in the business.. so why are they kept on..?
Now I don't know school environments, but reasons can be nepotism, management inertia, or they do X brilliantly, and for any of those reasons, and maybe others, they are still there.
Hell, I've been called out before for wondering in at lunch time, absolutely hilarious if they do it in public. "Yes Bob, I was up half the night fixing the billing system, but thanks for that"
FatMetalJesus@reddit (OP)
From what I was told, he "didn't know any better" when I asked about why plaintext passwords were being stored in a Google sheet.
Velo_Dinosir@reddit
Some practical professional advice, nothing technical here;
When you have a situation where a peer or senior is dog shit, but they seem to be getting away with stuff still, you realistically only have 3 options.
If you like the job and want to keep it, you chose options 1 or 3.
Option 1- you do his job and yours. Shit sucks. Do not recommend, but you may find yourself in that situation. Confrontation, accountability, and training are lost causes. If he’s been there long enough, chances are someone has been in exactly your shoes and chose option 2 because they aren’t there to do option 1 anymore.
Option 3- stop caring about his fuckups. If you want to stick around, and you want to keep your sanity, it’s time to get shitty. Stay in your lane, put on those horse blinders, and focus on what you want/need to do.
Option 2- prepare to leave; the company is a walking timebomb at best. This is not a place you make a permanent career unless they put you in charge and give you the authority to make changes, including him.
My personal recommendation is start using your time to brush up on skills that specialize you and look for gainful employment elsewhere. This person is likely a symptom of a dysfunctional organization and you’re not going to make a steady career in this place. Milk it for what it’s worth and move on man.
Iceman_B@reddit
Congratulations, your sysadmin is Michael Scott. Escalate up to management and/or HE and let them deal with this.
Also, polish up your CV.
showerhandles@reddit
You work at a school. Its not that serious to others it seems. No chance at getting a bonus for great work etc. so you shouldnt be too tightly wound either. Itll only make you miserable. Do the work slowly and if someone complains just cite the sysadmin as being slow
galland101@reddit
This is what happens when nobody but you gives a shit. Leave and don’t look back. This guy is probably some insecure weasel who takes all the credit and always puts the blame on everyone else. You’ll probably the one he blames when you get hacked.
No_Yesterday_3260@reddit
I've had luck explaining to the higher-ups the very specific risks and how easy things can go wrong.
Just as a CLASSIC example - When companies don't want to do MFA on their logins, coupled with bad password practices, 30 minutes, everything is encrypted.
Maybe there's some professionals that can give the higher-ups an awareness course, with you providing the higher-ups with the information about the sysadmin practices, so they can see the contrasts :)
Coder3346@reddit
Give me the domain name. I will just teach cybersecurity lesson.
Fitzand@reddit
Look for a new job. Move on.
shrimp_blowdryer@reddit
What is rock you
bushman4@reddit
A password list:
https://weakpass.com/wordlists/rockyou.txt
Benson92@reddit
https://weakpass.com/wordlists/rockyou.txt
bossman1337@reddit
We will, we will...
Helpjuice@reddit
Escalate and work on getting out of working for the school. Quality of people are low, pay is bad, and this is just the type of people that this work attracts due to the super low bar for entry which you would think would be much higher and handled by the county level so it had proper funding from tax money to get some decent people in there.
UpperAd5715@reddit
Run it through legal and put your shit on mail, then try and relax and let loose. If you have any kind of cybersecurity insurance just tell school leadership "this bullshit means that we pay that insurance for nothing as they arent going to pay a dime if we get hacked and data gets stolen". Probably means they'll lose out on some programs or whatever and that hurts their bottom line.
Admin isnt going to care about you if he doesnt even come in, basically made himself irreplacable by making sure nobody has access to anything and in a school nobody wants to go through the pain of having someone figure everything out without information. Document, share your concerns and try and not grab for the bottle as your default "i need to de-stress from this" action!
Electrical_Bad2253@reddit
Have every request to him in writing and tell everyone you’re waiting for him so you can do your piece. Somebody will eventually have enough of it.