Sweet black fucking sabbath.
Me: Here is where you check to make sure you're running this test on only 1 endpoint.
Them: Okay great, deploy to 835 endpoints, are you sure, you have to type 835 into this box to proceed, yes.. typing 835 into box to proceed.
Straight up, I cried a lot today.
@misterfive @GlytchMeister the wipe didn't go though despite being pushed out to 800+ endpoints. I have since deleted the software package and told management we will not be running this process from my side ever again. This is now a one off.. direct hands on engineer operation from now on.
@GlytchMeister @misterfive yeah.. it didn't happen though a miracle of incompetence
Might wanna consider setting up a automated offsite backup system, juuuuust in case C drives get formatted or some shit, got dayum
@GlytchMeister @misterfive we have backups of servers, not workstations. Servers were never under threat by this though.
Sounds like the system my old job had. Customer facing servers were backed up regularly, but employees were supposed to back up their own day to day work. Which they mostly never did, as there wasn't really any way provided to do it.
Seein as hundreds of millions of dollars could be lost by losing hundreds of workstations, sounds to me like each workstation stands a chance of bein worth a million bucks.
I’d say that’s worth backin up. 🤷♂️
@GlytchMeister @misterfive its not the data loss.. is the down time to production and time and capital spent to get 800 workstations operational. User data is mostly on the servers.. moooooostly (insay loooooosely)
But if that many things were wiped... I dont even wanna think about it anymore *drinks more whiskey*
Ohhhh I see. Well at least it’s taken care of. I do NOT blame you for the whisky, I’d be tempted too.
@Idrake @misterfive
Oh thank FUCK, so 800+ workstations didn’t ACTUALLY get wiped?
HOOOOO boy, that’s a butt puckerer, right there