techrecovery | Functional blackmail, it's for Christmas now!

At the moment the $BigAcademicNWHospitals helpdesk is very very quiet. Santa's gift came a bit early in that way.

Unfortunately the coal in the stocking, that is we the lost of one of the power feeds to our primary location, and this is going to annoy us a lot over the holiday. On a thin crew of one per shift we are not putting too much trust in the rather shabby infrastructure at the primary location and going to operate from our backup at $BigAcademicNWHospitals' proper for the next day.

Downside is that from this location we cannot access a specific tool used to clear oft fouled hospital label printer queues. Why? Because they are phasing out this tool without giving us a replacement. Nearly all of our computers at the primary site can access the tool, as they were grandfathered over. However our backup site has only been up for a few months, so we don't get that here.

I am doing a bit of blackmail as a result. I _have_ to assign these issues to the group that handles the label printer queues, you see. So I'm making every one, which are typically used in the ER at this hour a Critical issue (which I am supposed to do, you see--Policy and all--ER==Critical).

I've just had a nice email exchange with the oncall of this other group who is having to bug her Unix guys this festive eve.

My last email said "Well, you know, we're going to be here tomorrow too. I'd be as shame to have to pepper you with these OMG-Critical tickets throughout the day. Could you maybe just add these two computers so they have permissions to access the particular server?"

We'll see how this tack works.