Trundled back to work this morning.
Over the holiday period I’ve observed that one of my network segments (the one which I’m using to set the new file/print/active domain controller/etc up for the company network upgrade, stopped responding.
Assumed the NAS shitted itself as usual, but was not too worried as I have backups, and it is not used yet anyway.
So, when I arrived at work, I found the NAS and server is 100%. My attention then turned to the PC hosting the firewall and network router (all VM’s).
Upon closer inspection, I found that the CPU fan somehow worked itself loose and the CPU burnt itself out, which is weird as the latest Intel CPU’s are supposed to throttle themselves when overheating. (i3 CPU).
Anyways, trundled off to get another motherboard, fit it, also dead. Tried another PSU, still no luck.
At this point I moved this PC to one side, for reprogramming (with a hammer) at a later stage, and commissioned another PC (which I was using to test powershell scripts and RAID arrays on).
Fired it up, works, Add extra RAM, fired it up again, still good.
Moved the HDD from the old PC over to the new one, and let Server2016 start up.
Everything came back up beautifully, except for the onboard NIC which Server2016 had an issue with. Faffed around with this for a few minutes (including locating and installing the original NIC device driver from the manufacturer’s website), then decided that the onboard NIC can go blow hairy and sweaty goat balls.
Fortunately this problem was solved with the addition of an USB NIC. (derp durr). Traffic over the USB NIC will be low, so it should not be an issue for now.
That was the only IT issue that I first faced in 2018. What about you guys?
I blame the Grinch.
edit : started the original motherboard up, now it works. o_O