4 ms·
Working on a software deployment across the whole company but without a reliable means of distributing software. Using a combination of AD login scripts where
by herghost 10y ago
Working on a software deployment across the whole company but without a reliable means of distributing software. Using a combination of AD login scripts where available, but mostly relying on the antivirus product which was installed to locally run scripts on each endpoint.
Cut to 1:30am after a full day of eking out 1 or 2 endpoints here or there, and I've figured out a new method to try. But first I need to test it and make sure it's not going to break anything else, so I create a separate asset group in the AV software and add only my machine to it. I add a simple "hello, world!" type script just to show that the script is executing and wait.
And wait.
No "hello, world!". It's 2am, I'm back in the office at 7am, my new insights will hold until tomorrow. I'm going to bed.
About 6:45 I'm in the queue at the shop to get coffee and bacon and my boss walks in for the same. We small talk and then he gets an incident call.
There's a virus affecting all of <locality's> machines. Uh-oh. He's getting ready to abandon his coffee and bacon aspirations (he's the Head of Security), when I ask what's actually happened.
"As everyone's logging in in <locality> this morning they're getting a command prompt pop up that just says 'hello, world!'"
Oh. Fuck.
I abandoned my coffee and bacon aspirations and assured him that this wasn't a virus, it was a misconfiguration that I'd made only hours before.
It was sorted within minutes and was broadly taken with good humour. But I was referred to as "World" for a while afterwards when people greeted me.
- oAlbe 10y ago> I was referred to as "World" for a while afterwards when people greeted me. That feels meaner than it sounds...
- passiveincomelg 10y agofrom the canonical list of Reasons Against Overtime I surely contributed to that list, but was too tired to remember any details. :)