Earlier quoted context omitted.
That probably means nobody is using the servers you maintain and your department should be eliminated completely.
Or somebody was just joking... Who knows...
maybe I was joking too!
“A Windows 7 deployment image was accidently sent to all Windows machines”
61–70 of 149 posts
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#62Snark and sarcasm aside, I am impressed with the level of detail that the IT department is sharing; it is refreshing to see such a disaster being discussed so openly and honestly, while at the same time treating customers like adults.
It's not a standard across the board, but I've found academic institutions to be more honest about their technological mistakes (outside of large-scale breaches) than the private sector.
I worked at a company for several years that provided software to the IT groups in the higher ed vertical. What I found is there are two types of people in higher-ed IT (and they often congregate at different campuses):
First are the people who believe in the mission. They are really good, and are willing to take a cut in pay for some combination of social good, great working environment, etc. These kinds of people tend to be forthright about problems.
The second group are people who would struggle with the demands of the normal corporate world. They are getting paid less in higher ed and are worth what they are getting paid.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#63I've just been hired to run a project using SCCM to upgrade ~5000 PCs from XP to Win7. This was amazing reading. Reading such a detailed wrap up of an IT team going through my worst possible nightmare was enlightening.
It must be reassuring that your new employer is so proactive in getting that XP upgrade project running.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#64Earlier quoted context omitted.
> As soon as the accident was discovered, the SCCM server was powered off – however, by that time, the SCCM server itself had been repartitioned and reformatted.
I feel bad, but I laughed at this for few seconds...
I wouldn't feel bad. I guffawed at most of this story.
Not in a "haha, what a bunch of morons. Serves those jerks right!" kind of way, but more in a "oh dear, that's the worst thing that can possibly happen! Oh no it gets worse??". I've been through IT catastrophes (and caused a couple myself) and I could easily see this happening to me. Still, it's funny as anything.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#65Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#66Reading that just made me feel sick to my stomach and my heart goes out to the poor gal/guy that pushed "Go" on that one. Shit happens, but a screw up that big can be devastating to ones psyche.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#67stark3, you seem to be hellbanned.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#68https://twitter.com/DEVOPS_BORAT/status/41587168870797312 "To make error is human. To propagate error to all server in automatic way is #devops." Frankly, I'm surprised things like this don't happen more often. Kudos for the incident management. Also a big plus for having working backups, it seems.
Worst mistake is always happen in batch. --Devops Borat
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#69There was a similar catastrophe at Jewel osco stores many years ago. Nightly, items added to the store pos were merged back with the main item file at each store location. The format of the merged data was exactly the same as loading a new file, except the first statement would be /EDIT instead of /LOAD. One of the programmers decided to eliminate some code by combining the two functions, with a switch to control whe…
Failure should never be the only time you get to meet upper management :(
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#70Earlier quoted context omitted.
The BOFH sabotaged his systems before departing? Didn't build a backup plan? And they hired him back?
You know what? Fuck them. Fuck higher education completely. Undervalued and underpaid is the name of the game for any important IT roles in that shit hole of an industry. Disclaimer: dev at a university.
Preach it.
That said, if you get a cushy job, it can stay cushy for a long time.