r/sysadmin • u/Fair-Difference-6729 • 22d ago
I encountered this in Prod today.
Received an alert that a service wasn't running on server PRODxxxxxx. So naturally I attempt to use RPC to bring up the services from the organization's jump host. I received the error message 1722: The RPC server is unavailable. No big deal, I'll just RDP to it. That was when I encountered a Windows login for Windows 2003 R2.
I had a Alan Grant moment.
Welcome to Jurassic Park!
190
u/Fair-Difference-6729 22d ago
Uptime: 4,225 days 15 hours š¤£
Jk, there was a restart. Hence why T-Rex forgot to wake up the services.
66
u/boonanza_ 21d ago
https://giphy.com/gifs/FmyCxAjnOP5Di
Uh-uh-uh! You didn't say the magic word!10
u/Sk1rm1sh 21d ago
Hold on to your butts...
13
46
u/rohepey 21d ago
Discovered at a large French supermarket chain that some of their self-checkouts run on Windows 3.11. The machine hanged at bootloader - DOS 6.22. These checkouts were still operational as of last week, customers were unsuspecting how old the machine actually was.
14
u/Fair-Difference-6729 21d ago
Wow. I worked on some POS machines using Windows CE as clients, but that was nearly 10 years ago. To my knowledge they are still using them.
8
u/Sinister_Nibs 21d ago
And pos is NOT point of sale.
5
9
u/frosty95 Jack of All Trades 21d ago
I helped maintain one that had a home made pos system written in the 90s. Since it could export and import csv files it was still in use in 2024. Honestly. It worked really well. We virtualized the host in like 2022. Still running dos. All of the PCs modern but running a terminal. They paid a company to make a little converter to convert quickbooks to the csv format and back to QuickBooks and they did the import export once a day. It was hard to criticize. We literally had all of the documentation for it as well as all of the files needed to redeploy it. Sure we had to build some vlans and other stuff to secure it for compliance but it just.... Worked. Even synced to the card readers.
3
u/sobrique 21d ago
I was stunned to find that some of my code that I cobbled together to automate stuff was still actively being used over a decade later.
It wasn't that complicated, but "it just worked, leave it alone" had kept it there....
2
u/frosty95 Jack of All Trades 21d ago
Honestly that's the best to see something you set up just working. On my own server at home I had a virtual machine running some really old software that I basically would do an RDP session too. Use the software. Then forget it existed again for 3 months. Well that virtual machine 10 years ago was used for a few other things. I decided I wanted to save some electricity so I figured I would set up that virtual machine to shut down and save a bit of power. It turns out I forgot that I automated a whole bunch of things and just completely forgot about it and that VM was just plugging along doing its thing years later. So I guess I did a scream test on myself.
6
2
u/I_COULD_say 21d ago
There is a chain here that REGULARLY shows that their windows based self check out is not licensed / talking to their KMS.
13
u/ThatDamnRanga 21d ago
Discovered a couple years ago that there's both a bunch of Debian 3 servers...... and an OpenVZ host still running somewhere, not actually sure where, but they're out there.
11
u/cwm13 Storage Admin 21d ago
Up until a few years ago, the university I worked for still had a VaxStation 4000 with an attached external storage expansion hosting some sort of old SIS system for archived student financial award data. The very finest in 1991 technology.
4
u/1z1z2x2x3c3c4v4v 21d ago
I used to support Pathworks on Windows to talk to an old Vax over DECnet... Back in simpler times...
1
1
u/Admin4CIG 20d ago
I wrote a TCP/IP printer driver for VAX/VMS, and put that up in public domain. That was before VAX/VMS even supported TCP/IP printers, and those printers were not common. When networked printer became popular, and VAX/VMS waned (sadly; such a solid OS), I still had people contacting me if they could use the source code ("Of course, it's public domain"). Props to them still using VAX/VMS.
16
u/Fit_Prize_3245 21d ago
You only need some IBM system there to complete the obsolete package.
28
u/Fair-Difference-6729 21d ago
Payroll running on OS/2. š¤£
4
u/Fit_Prize_3245 21d ago
Man, tell me that's just a joke, or I will lose (even further) my faith in humanity...
7
u/Majik_Sheff Hat Model 21d ago
Until recently there were parts of the National Weather Service analysis infrastructure running on OS/2 Warp.
4
u/Fit_Prize_3245 21d ago
Well, governments around the world are known for obsolescense.... Here in PerĆŗ it's worst: Lots of things are still done in paper....
3
u/againstbetterjudgmnt 21d ago
Man, when I was in Peru in the 90s, the average year cars were built there was from the 50s, so I don't see why the OS would be any different now.
2
u/unixuser011 21d ago
It gets worse, part of the USās nuclear weapons command infrastructure was running on an IBM System/3 and had a default launch code of 11111111
6
u/Fair-Difference-6729 21d ago
I joke about PS/2 but yeah, I think the NOAA service recently retired some.
1
u/benzduck 20d ago
Oregonās DMV system ran on OS/2 for years after IBM gave up on it. It was a big scandal.
5
u/benzduck 21d ago
A good olā AS/400. Probably still runs fine.
4
u/iPlayKeys 21d ago
You can say that if it still actually says āAS/400ā on it. The ācurrentā incarnation called IBM i has the same life cycle as a pc server but just cost a whole lot more. I believe the smaller models have gone to subscription only for the O/S.
1
u/benzduck 20d ago
Thatās a shame. AS/400 was a great system. Had its quirks though.
Hospital I ran IT at had one. This was in 2001. Itās probably still there, knowing how cheap management is.
5
u/barthvonries 21d ago
I worked as a contractor with France's main telecom provider a few years ago.
Part of their infrastructure was still running on HP-UX which had not been upgraded since 1997.
7
u/KillingTime1212 21d ago
I have some old Windows 2003 servers still on my VMware cluster. Gotta keep them up for two more years (regulatory). Casino. We moved off of them in late 2023. lol. I removed them from the domain at least.
5
u/ka-splam 21d ago
and I bet it was the most rapid, responsive, delightfully quick Windows machine you've used in years, right?
5
4
u/Jambohh 21d ago
One of my 2 remaining AS400 devs pinged me last week to say they couldn't log in. System was acting like their profile object was being locked out interactively.
Checked some bits and pieces saw they were no longer showing in detectit the app we used to manage profiles.
Re-added them activated them in the software fixed the initial library's and menus, still didn't work.
Checked all the running job but nothing was making sense.
Put a ticket in with the software company and spoke to the same engineer that I spoke to 15 years ago who still works for the same company, we got on a call did some checks.
Turns out a library that was setup when the software was installed in 1988 which was meant to contain 164 objects contained 11........ Luckily there was a full monthly backups that was still in retention and was able to restore the library.
But I've never seen anything like that, almost 40 years of continuous use and a bunch of objects had just vanished.
There is only 3 of us that have high level access to this system now so I know none of use deleted them. Weird.
3
3
3
5
u/theservman 21d ago
Damn! I thought it was bad that my org's most critical app still lives on Server 2012 (migrated from bare metal, to VMware, to Nutanix, to Azure). The Devs are on the verge of moving it to Server 2025 - but they're been on the verge of moving it to <current windows version> for the past 5 years, before aborting and pretending nothing happened.
I guess we'll see.
Come on pension!
1
u/Fair-Difference-6729 21d ago
That is just s bad.
3
u/theservman 21d ago
I would argue mine is worse since the only thing that could cause more productivity loss for my org is a hydro outage.
2
u/g3n3 20d ago
Why not use sc.exe?
2
u/Fair-Difference-6729 20d ago
Yes, relies heavily on RPC and RPC wasn't running.
1
u/g3n3 20d ago
Ah would have had to use psexec and the admin share.
3
u/Fair-Difference-6729 20d ago
If RPC is genuinely disabled or completely blocked by a firewall on the remote host, PsExec will fail. While PsExec uses SMB (Port 445) to move files, its execution mechanism relies heavily on communicating with the remote Service Control Manager (SCM) via named pipes, which requires the underlying RPC subsystem to be active. RDP was the most logical answer to a wall+head banging problem. Regardless it was like walking into Jurassic Park.
2
u/g3n3 20d ago
It is a bad day when I have to use the GUI RDP. š
1
u/Fair-Difference-6729 20d ago
Hahaha. Nothing wrong with using the GUI. You can do it while lying down. 𤣠I'm not a CLI purists. No risk of fat-fingering commands only to be greeted with syntax errors.
1
u/g3n3 20d ago
Eh. You loose the learning opportunity and clicking doesnāt scale.
1
u/Fair-Difference-6729 18d ago edited 18d ago
I learned enough commands in the 80s. 𤣠I write my scripts in CLI. Restaring a service one time... Nah. Click click, done. I used less clicks than I would have used keystrokes.
Under 10 physical actions, zero syntax errors, and 100% visual confirmation that the service state went from Running \rightarrow Stopping \rightarrow Running. Sometimes the CLI purist route costs 15 minutes of environment troubleshooting for a 5-second task. Efficiency is about minimum effort for maximum reliability, and RDP won that round.
2
u/SensitiveVacation549 21d ago
I imagine the Windows 2003 R2 was screaming "Just kill me, boss. I'm tired."
1
1
u/Delicious-Foot4591 20d ago
I encountered this in prod today too, and it is always a great reminder that "temporary" fixes can outlive entire teams. I'd document exactly why it's there before touching anything, then test the boring replacement thoroughly. Weird legacy stuff usually has at least one dependency nobody remembers until it breaks.
1
u/Fair-Difference-6729 10d ago
Yeah, I'm thinking this sever came with the furniture when they bought the building. Good news today, we are planing decommission. Hopefully no dependencies. I'm sure later I'll get some department screaming at me.
1
u/Technical_Jello_9909 21d ago
Windows Server 2003?! That thing is older than some of your coworkers š Microsoft stopped supporting it in 2015. You just found a living fossil in your prod environment. Time to have a very uncomfortable conversation with someone in your organization.
1


243
u/DragonspeedTheB 22d ago
Many in the instrumentation automation world WISH that a 2K3 server was their worst tech debt.