[identity profile] patgund.livejournal.com posting in [community profile] techrecovery
At various points duirng the medical school year, we have so-called "triple jump" exams. Due to security, IT gets involved because we have to prepare an exam image, (stripped down version of OS X that only has MS Office and printing, no save or web functions, and has preloaded the files needed for the exam.)

It takes us usually 1-2 days to prepare the exam, and each image is taylored for the printer in each room. Each room has six G5's. Radmind is used to insure that only the machines in that room get that image. One hour before the exam, all the machines are imaged with the test image, and printing is checked. Machines that fail are pulled and a new one put in it's place. If everything works out right, it can be done in 15 minutes. If not, we need every second of that hour.

So, bright and early today, exam instructors come into IT. And tell us that the exam has been moved to 8:30am, and and oh, we're using three rooms instead of one, because they didn't realize that 18 students can't use six machines

They tell us that at 8:05am.

Quickly build an image for the other two rooms, and pull a all hands on deck to image the machines. Thank all the Gods at once we didn't have a hardware failure. Get the whole thing done at 8:27am, with an IT staff member (myself) on babysitting duty in case of a failure mid-exam.

Just in time to catch merry hell from the exam coordinator for IT "not being prepared" for this exam.

EXCUSE ME???? You gave us an incorrect number of rooms and students needed, (and they're damn lucky the other two rooms didn't have classes scheduled for them), changed the time with NO notice to IT until 25 minutes before the exam. They know damn well it takes an hour to set up those rooms, and that we're supposed to be notified 24 hours ahread of the exam in case of changes. Where the hell do they get off blaming IT for their screwups???

Oh, that's right, they're doctors and medical school instructors. They're infalible on everything, aren't they???

*Facedesk*

(On Edit - the interm CIO just caught hell about it too, and his response? To chew us out for "not being prepared", and had no interest in hearing any "excuses" from his IT staff. Typical reaction from him, he bends over backwards for faculty and staff, and will not back his own staff up or give us the tools needed to properly do our jobs. Grumble)

Date: 2006-05-03 06:28 am (UTC)
From: [identity profile] artela.livejournal.com
I suggest that once the dust is settled you (as a dept) send out an IT memo reminding people of the deadlines for work to be done in such circumstances.

Oh, and your boss sucks. They should have at least listened to you objectively and then chewed out the people really at fault :-)

Date: 2006-05-03 06:45 am (UTC)
From: [identity profile] bamatone.livejournal.com
Yeah, whatever. Listen. You have the greatest collection of icons I've ever seen.

Date: 2006-05-03 07:00 am (UTC)
From: [identity profile] psychotwinkie.livejournal.com
*comes out of lurking again*
I have to agree. I wanted to yoink about 1/2 of your icons ;D, they are just that good!

Date: 2006-05-03 07:07 am (UTC)
From: [identity profile] psychotwinkie.livejournal.com
Thank you :3

Date: 2006-05-03 08:45 am (UTC)
From: [identity profile] the-s-guy.livejournal.com
Damn. I would have been tempted to tell the exam co-ordinator "You requested six PCs. You got six PCs. If you would like to request more, please fill in the form and we will respond in three to six working days. Or, if you would like to jump ahead in the queue, you can apologise to both me and to the students for your screwup. But make it fast, I have outstanding requests from people who actually realise that equipment doesn't magically pull itself out of my ass."

Date: 2006-05-03 11:27 am (UTC)
From: [identity profile] gilmoure.livejournal.com
The good thing is, it's a medical school. If people there were to suffer...knee injuries, they'd give the students some hands on training.

Date: 2006-05-03 12:51 pm (UTC)
ext_8716: (Default)
From: [identity profile] trixtah.livejournal.com
Glad you're getting out. If your boss won't back you up, when you have a clearly-defined policy and you're totally in the right, time to say buh-bye.

Date: 2006-05-03 01:52 pm (UTC)
From: [identity profile] canray.livejournal.com
I'd have been more than tempted.

When all else fails, make like a Beuracrat.

'Course, I've played Paranoia and GMed Paranoia XP, so I'm *VERY* good at it. *Evil Grin*

Date: 2006-05-03 01:56 pm (UTC)
From: [identity profile] canray.livejournal.com
"Today we shall demonstate the proper useage of a Clue-By-Four to beat the stupid out of this person. Ummmmm, I'm going to need a COUPLE of volunteers to do this, as this is a very stupid person."

Date: 2006-05-03 02:11 pm (UTC)
From: [identity profile] canray.livejournal.com
Find some of the Paranoia Form-Request-Forms on PDF for the people to fill out, too!

Those are great!

Date: 2006-05-03 07:50 pm (UTC)
shirenomad: (Whedon)
From: [personal profile] shirenomad
Agreed, but just for the record, I created the "Swearing in Mandarin" icon... I'd appreciate a mention of that in your icon list, [livejournal.com profile] patgund.

Date: 2006-05-04 12:26 am (UTC)
From: [identity profile] network-nerd.livejournal.com
I got a call the other day from a senior exec, reporting wireless not working in location XXXX -- emergency, event is going on there.

So I throw together my kit and verify that wireless *is* working there just fine....

Then I take a look at the AP logs, and see that there's this one client trying to associate every five seconds ... and it's one of the clients from location YYYY.

XXXX is one of our (current) standard locations; there's a pool of laptops that live there, and that are specified to be the machines that are allowed to use the wireless there.

YYYY is a legacy/rogue location that we don't have management access to; it's only allowed on the network because the user who installed it has tenure.

So I write up the ticket: "Wireless in XXXX is working as specified. No access was ever requested for the client that is trying to access it and failing." And route it up the chain of command for policy guidance, where it still sits a week later.

Date: 2006-05-04 03:00 am (UTC)
shirenomad: (Default)
From: [personal profile] shirenomad
Thanks muchly.

Date: 2006-05-05 02:14 am (UTC)
From: [identity profile] klytus.livejournal.com
Saddly, even this isn't always good enough, as people like this think you just make exceptions to proceedure for them because of "who I am." It also sounds like you cork-suckling boss would buy into it and get on your case for not breaking proceedure. Hmm... maybe you could use that to your advantage? Go to *his* boss and say how his pathetic minion is telling you to ignore proceedure?

::sighs:: Only in a more perfect world...

Profile

techrecovery: (Default)
Elitist Computer Nerd Posse

April 2017

S M T W T F S
      1
2345678
91011121314 15
16171819202122
23242526272829
30      

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 20th, 2026 09:19 am
Powered by Dreamwidth Studios