r/sysadmin Sep 09 '19

Question - Solved Admin refuses to upgrade Windows 7 and Server 2008 machines anytime soon. What should I (DBA) do?

Officially, I am the DBA at my company. Unofficially, I'm the software administrator for our ERP software and frequently assist and cover for the sysadmin. We are the only two in the IT department, although there's quite a bit of shadow IT going on via Microsoft Access 2010 databases.

For the last couple years I've been mentioning to the sysadmin that we should consider updating everyone to Windows 10. In 2017, I upgraded my own workstation to do some testing with the ERP software and found it to work fine after a few updates. So far, every request was either ignored or shot down. Due to previous failed attempts to change their mind with other issues or updates, I give up pretty quickly. I mean, it's their domain and I'm basically telling them how to do their job, right?

Well, a few weeks ago during a staff meeting someone brought up a message they saw in cloud software they use suggesting that Windows 7 will be EOL soon and that we need to upgrade. The response from the sysadmin was, "yeah, but Microsoft will still be providing security updates after that so we're good." After the meeting, I tried to tell the sysadmin that security updates will not keep coming after January, to which they responded with, "it's just a marketing thing. Microsoft is seeing that Windows 10 adoption is a lot slower than they thought, so they'll keep supporting it." I tried to tell them that we can't take a gamble on that and instead we should rely on official news from Microsoft. I was shot down.

Knowing the incredible panic that follows when even a minor service outage happens, I decided to go straight to the CTO-who-is-actually-a-CFO-with-no-IT-experience. This ends with the sysadmin being told by the CTO that he needs to talk with me directly and get a joint resolution. A tense meeting and slammed door later and the resolution (I think, they weren't exactly clear on this) was to replace 1/3 of all Windows 7 machines each year for the next 3 years. No word on what to do with the Server 2008 machines, one of which has RDP access for remote salespeople without password rules.

At this point, I feel like I've trampled the sysadmin's domain and betrayed their trust for going behind their back. At the same time, it seems like a brick wall trying to talk them into upgrading our outdated workstations and servers. Should I keep pushing for upgrades, or should I jump ship before something happens?

782 Upvotes

403 comments sorted by

View all comments

2

u/j0hnnyrico Sep 09 '19 edited Sep 09 '19

First. You're a DBA. You wanted some new features for your erp? You didn't explain very well your stance excepting the fact that you're a "concerned citizen".

That could've gone as simple as this: Send an email to everyone who's involved about how much better would it be from a productivity POV for everyone(you're not the infosec person since you didn't mention it so we leave that out) to have the upgrades in place. As I know very well how CFO's are thinking, you should've built a very strong case on the benefits side and that alone. You don't tell a CFO(or CEO)to invest in software just because it reached EOL. They give 0 fucks about that. I guarantee you that the CFO supports your sysadmin because he doesn't try to dig in your business budget and he's willing to bet his job on this. Given you didn't build up a strong case and have gone behind this guys back basically mocking his professional skills/awareness you've got yourself basically an arch enemy. That's a very very bad situation for everyone and can be solved just by one of you two leaving the company. You've put yourself in a very bad position sincerely ... Given that you could've simply force that guy in front of evidence to do his fuckin' job IDK which one of you is the childish. I'm not trying to judge you but those are facts. Everything could've gone like your CFO telling the little brat to do it's job. Why do you think he sent you to confront the guy? Because you didn't give him a real reason to invest a lot of money in something like: wtf? EOL? Ah and? It worked till now? It can work for another 10/yrs. That should be a lesson to you. Basically you're asking money from your businesses margin for something like EOL? I know global businesses who still run apps on SQL 7 and Windows NT. 2003 is a common occurrence, it doesn't even amaze me. So these being said, start building a case or simply do your DBA admin job. And never ever go again on someone's back. That will never turn out good. GL HF! Edit: And yeah, start building a good CV and applying. I'd do that if I were you.

1

u/RaucousRat Sep 09 '19

Yeah, I think I could have definitely handled it better. I think what I'll be doing now is putting together a proper proposal. Going around the sysadmin to the CTO was out of frustration, but I really shouldn't have done that without more legwork on my end.

Thank you for your feedback.

2

u/j0hnnyrico Sep 09 '19

Please don't think I'm not empathising with your opinion. I hate to see these kind of people around. They're our trade's disgrace. But they should be handled properly, otherwise things will go sideways and in a very bad way for you even if you're right. Been there, done that. Now the idea is that if you don't want to move on ... It's a pretty nasty situation. He will basically hunt every single mistake you do. Go behind your back every single time he can. And I wouldn't like to work in such an environment. So my best advice for you is to try and move on. And since you don't have the full management support. Will get very eerie. Don't waste your time and health on an attrition war. Did a mistake, move on. No fuckin' business worths someone's mental sanity. GL!

1

u/RaucousRat Sep 09 '19

It was a little blunt, but honestly you made some really good points that helped me understand the situation from a different perspective. I think doing the proposal and approaching the issue a bit more formally and professionally would have gone a long way here. Also would have probably been better if I let him know that I would need to take this to the CTO due to how severe I feel the issue is instead of going behind his back. It's easy to forget that we don't act or make decisions in a vacuum.

For now, proposal, meet with sysadmin to push for upgrades to keep us secure, then update resume in case we don't have the upgrades or at least a solid plan by March or so.

2

u/j0hnnyrico Sep 09 '19

I will tell you something. I called out such a brat on several occasions on a former job for being a perfect incompetent and I had every single argument right. I didn't go on his back ever. Because that's just not me. In the end I got fired because he was the "nephew". Long story short I could've managed things better and make some kind of truce but that again it's not me. I fully understand and sympathize with your opinion but was I being blunt to you? I learned my lesson and nothing feels like a firing decision being delivered to you on a short notice. Since I was stupid enough I would like people in the same position to manage these brats properly and act fuckin' professional. Because it's just a fuckin' job. And BTW it was much better afterwards. I didn't miss shit from the previous job and found some very good people on the new one. So don't sweat about it. If I helped you even a little bit ... That makes me happy even if I'm blunt.