So, aside from interviews being bizarre I also had a bizarre case yesterday.
For context, we only provide support for a small number of PCs on a hospital network - and ours usually hide behind a NAT/PAT (Linux Zentyal box) that only lets in traffic on a select bunch of ports only.
So this site managed to get a hospital wide virus infection. They usually don't spread to us, but this time they did. My policy, since we do control software for radiation treatment, is to reinstall any servers and any machines involved in real time treatment delivery again to make sure they are clinically safe. Workstations where doctors letters are written or where treatment plans are reviewed I am less strict about.
This attitude, as usual, clashed with customer IT who had disinfected the server PCs and were assuring me they were fine. In the fifteen minutes I was one of those things the error log had ballooned to the size of the New York phone book and I had to reset my teamviewer (yes, I hate it but they wanted to see what I'm doing) connection because of a bsodding driver issue - but sure, everything is fine. What could possibly happen if the server bsods during a treatment. Naturally, IT's driver reinstallation did not make this go away.
I was arguing with IT when I remembered these guys don't know anything about MS SQL. So while team viewer was running I fired up the VPN, opened my trusty old friend SQL server management studio, set the database to emergency mode and then proceeded to show them in the other session.
"Have you seen the database is red? We have data corruption!!!1111!!!oneone1! Oh my god, what do we do?"
"Don't worry. If you set up a new server for me, I can restore from a backup."
"Yes, give us an hour."
Problem solved.