News: 1713166153

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Tired techie 'fixed' a server, blamed Microsoft, and got away with it

(2024/04/15)


who, me? Welcome once again, gentle reader folk, to the comfy corner of The Register safe space we call Who, Me? wherein readers share their stories of times when they were not perhaps at the very peak of their technical brilliance.

Last week we put a call out for stories of lessons learned the hard way, and boy did you deliver. For this instalment meet someone we'll Regomize as "Laurence" who assures us that he has had an otherwise "glittering" career in IT – other than during the incident we report today.

Laurence was working as lead developer for a large company at which IT in general – and in particular the notion of "IT investment" – was treated with utter disdain. All the tech in the place was well beyond its glory days, and much of it was limping along on its very last legs.

[1]

Laurence and his infrastructure manager had resurrected many dead and dying machines by using a utility we've chosen not to name that could clean up a Windows PC's registry and clear out a bunch of junk from caches and the like. Fairly basic stuff, but effective.

[2]

[3]

Now, as it happens, not only the PCs but also the main production server was prone to erratic behavior. It was old, running out of space, and not in good shape. Laurence was asked to fix it.

In his defense, Laurence told Whom, Me? "I was also on my last legs after months (and months) of working stupid hours to replace dying systems, working with un-co-operative users, surly managers and doing the work of about five people." So it's not really all that surprising that "in a moment of madness" he installed the same utility he'd been using to revive PCs on the server.

[4]

And then he ran it.

[5]Windows 95 support chap skipped a step and sent user into Micro-hell

[6]You break it, you ... run away and hope somebody else fixes it

[7]DBA made ten years of data disappear with one misplaced parameter

[8]Yes, I did just crash that critical app. And you should thank me for having done so

Shortly after, the calls began. Websites weren't working. Fileshares weren't working. Laurence logged into the server to find "file associations all gone, file types all gone, even UI elements disappearing before our very eyes." Clearly, a utility designed for fixing an offline PC should not have been deployed on a live server.

A managed service provider was called in to investigate, and said they'd never seen anything like it – the entire registry was gone. They asked if anyone had done anything that might have caused this.

Drawing deep within himself to summon his inner thespian, Laurence replied: "No."

Thus exonerated, he went home – leaving the service provider to spend all night rebuilding the server and cursing the very name of Microsoft.

[9]

In the end, management blamed IT, and IT blamed finance for not providing enough money to invest in decent hardware (or, thankfully, system logs), and everyone blamed Microsoft.

Laurence told us he learned three important lessons:

Don't try to fix things when you're exhausted;

Always use Microsoft server software so you have a credible scapegoat;

Acting skills can get you out of a crisis.

There's something in that for all of us, don't you think? If you've ever had a fast education at the cruel hand of reality on the job, let us know about it in [10]an email to Who, Me? and we'll share your knowledge with other readers. ®

Get our [11]Tech Resources



[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Zhz6vR@phGuNz-et-5aESwAAAMs&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Zhz6vR@phGuNz-et-5aESwAAAMs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Zhz6vR@phGuNz-et-5aESwAAAMs&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Zhz6vR@phGuNz-et-5aESwAAAMs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://www.theregister.com/2024/04/08/who_me/

[6] https://www.theregister.com/2024/04/01/who_me/

[7] https://www.theregister.com/2024/03/25/who_me/

[8] https://www.theregister.com/2024/03/18/who_me/

[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Zhz6vR@phGuNz-et-5aESwAAAMs&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[10] mailto:whome@theregister.com

[11] https://whitepapers.theregister.com/



Interesting

Will Godfrey

So, Microsoft can actually provide 'value' {of a sort}!

Re: Interesting

Korev

That's the HKEY to their success...

Re: Interesting

PBuon

DWORD, innit.

Trying ti channel my inner Ali G.

Korev

Speaking of the registry, why isn't the editor of this fine organ known as the "Regedit"?

CountCadaver

Giving me disturbing visions of newspeak and ingsoc

Tubz

Hey Microsoft, why does a server registry not have a change backup or locked out from being changed by unapproved 3rd party tools?

Tom Chiverton 1

It does have a backup.

Defined "approved tools". Who'd decide that ? How could that be abused, given M$ history ?

SVD_NL

The moment you run it with sufficient privileges it's an "approved tool". In some cases it's actually approved *by* a tool, but that's not M$s problem!

Anonymous Coward

I never understood why all the useful system configuration options are buried in this largely undocumented hellhole of keys and strings and dwords. And only accessible with a crappy editor. (does anybody know the difference between regedit and regedt32?)

Why isn't there a nice graphical config page with radio buttons and check boxes for every option and a paragraph of text explaining what each one does?

Even the old windows ini files were a better way of doing things.

42656e4d203239

>>difference between regedit and regedt32

regedit works? Dunno about these days but the 32 variant couldn't search in registry values, only in keys which was/is a bit of a limitation.

Oh sorry - these days they are the same... back in the day there were significant differences in functionality. It seems the timeline went regedit (windows 95ish) -> Regedt32 (NT4 ish) -> regedit/32 (x64)

Config options buried in largely undocumented hellhole of keys, strings and dwords

Anonymous Coward

[1]Anon : “ I never understood why all the useful system configuration options are buried in this largely undocumented hellhole of keys and strings and dwords. ”

To prevent Novell Neware running efficiently on Windows.

[2]Microsoft's Opening Statement in Novell v. MS

Nov 1993: “ We have to take the hard line. We can't give OpenDoc even an inch as easy runtime interface to OLE 2.0. We don't want to lose control of the API that ISV's are writing to. MFC is a special case since it belongs to Microsoft. If we say that OpenDoc is an OK runtime, then they will use that position to get ISV's to write to that interface plus they now get cross- platform benefits, etc. ”

Aug 1995: “ Below is the text of 2 messages sent previously regarding header files and libraries for implementing a Windows 95 Password Provider. To date, we have had no response, but we need this information. Can someone please respond with the information we need? ”

[1] https://forums.theregister.com/forum/containing/4844376

[2] http://www.groklaw.net/articlebasic.php?story=20111021140854502

Re: Config options buried in largely undocumented hellhole of keys, strings and dwords

MJI

Why I still hate MS

Registry bomb

trevorde

Worked on a project where we stored various system level settings in the Windows registry. When a dev pulled the latest code, they ran a .reg file to get the updated settings. I put a bug in the .reg file which nuked the whole registry, resulting in a bricked machine. After bricking my machine & another dev's box, we realised the error. We had one remote dev who was just about to fly in to the office. I managed to phone him at the airport, just as he was about to board. He'd pulled my registry bomb and was just about to write some code on the flight over!

terry 1

I think I know the software used. I recall trying it on my home computer despite many years of experience telling me don't. Sure enough it trashed the registry to the point it was unrecoverable. It also munched it's way though shadow copies so recovery options were thin on the ground. And at the time I was too cocky to do full images, just file backups via robocopy as they were deemed to be sufficient.

I had an backup attitude realignment that day!!

43300

Well, Microsoft breaking things isn't exactly stretching credibility very far, is it? Or stretching it at all, in fact...

a utility we've chosen not to name that could clean up a Windows PC's registry

Howard Sway

To be fair, it did what it said on the tin. It was just that their idea of what "clean up" meant may not have been the same as your idea.

Your computer's union contract is set to expire at midnight.