• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

Dear Users… (A thread for Sysadmin, Technical Support, and Help Desk people) Part 10

Status
Not open for further replies.
I've actually done some sleuthing and worked it out. A DoN is a Deed of Novation, which is used to legally transfer the rights and responsibilities of a contract from one entity to another. In this case the DoN was executed to transfer them from a person named Rodney to an organisation named Transcend.

i.e not HR but Legal.

It was cced to a bunch of other people. I closed the ticket with the comment "No action required by Service Desk".
See, I was THAT close! :D
 
I've actually done some sleuthing and worked it out. A DoN is a Deed of Novation, which is used to legally transfer the rights and responsibilities of a contract from one entity to another. In this case the DoN was executed to transfer them from a person named Rodney to an organisation named Transcend.

i.e not HR but Legal.

It was cced to a bunch of other people. I closed the ticket with the comment "No action required by Service Desk".

Fool! This was your one chance to stop Rodney! With Don's murder that made the 12,685 human sacrifices necessary for Rodney to transcend this plane of existence and become a demimortal demon god! If you had responded to the ticket properly by stabbing Rodney with the Six Daggers of Xabaoth you could have averted the apocalypse! It's now too late!! Rodney is even now flying through the demon dimension gathering power, and has been in talks with lawyers as well!!!!
 
Look up ISO 8601, which establishes


Arth could use this as justification for a change in the date format in his situation.


https://www.iso.org/iso-8601-date-and-time-format.html
I'm quite familiar with 8601. When it actually becomes a generally used standard I will embrace it happily. This hasn't happened in the last thirty years and I'm somewhat doubtful, barring generalised user re-education via CPT, that it will happen soon.
Meanwhile in the Real World it's more important to deal with the problems caused by DDMMYYYY and MMDDYYYY.
 
And is less likely to be read wrong. A project I worked on we had to get extracts from a hospital's database which was based around the US company Cerner's system and a homegrown datawarehouse. The former used variants of US formats with day and month in the opposite order from the DW which used largely UK data formats. Often we had to guess which format a column used. The few that were free format were a nightmare. And being hospital records you don't want to risk errors.
I've had international project meetings be missed because of the problem. I've lost count of the hassle in conversion, especially the time lost.
 
In this case the DoN was executed to transfer them from a person named Rodney to an organisation named Transcend.


My first thought was a joke I heard as a kid about a man checking a book out of the library called "How to Hug" only to discover that it was a volume of an encyclopedia.
In retrospect, it must have been a really inclusive encyclopedia to have a volume with such a small entry range or a really thin book.
 
Here's the newest demand, which I'm assuming one of my users got from a book of logic puzzles right next to the one about getting the wolf, goat, and bag of grain across the river.

There's a PC at the front desk.
User 1 has to be able to search job sites.
User 2 cannot be able to search job sites.
Users 1 and 2 have to share a login, the "workflow" (oh how I have come to despise that word) cannot support the time it would take for one of them to log out and the other log in, so a group login has to be used.
Put two PCs at the front desk.
 
I'm quite familiar with 8601. When it actually becomes a generally used standard I will embrace it happily. This hasn't happened in the last thirty years and I'm somewhat doubtful, barring generalised user re-education via CPT, that it will happen soon.

Meanwhile in the Real World it's more important to deal with the problems caused by DDMMYYYY and MMDDYYYY.

I blame the founding fathers.
 
Here's the newest demand, which I'm assuming one of my users got from a book of logic puzzles right next to the one about getting the wolf, goat, and bag of grain across the river.

There's a PC at the front desk.
User 1 has to be able to search job sites.
User 2 cannot be able to search job sites.
Users 1 and 2 have to share a login, the "workflow" (oh how I have come to despise that word) cannot support the time it would take for one of them to log out and the other log in, so a group login has to be used.

Price out a biometric system for identifying the user by facial recognition, and the development costs of adapting the job site software to assign permissions according to the results without changing the login.

Then ask if they're sure they don't just want two logins.
 
Price out a biometric system for identifying the user by facial recognition, and the development costs of adapting the job site software to assign permissions according to the results without changing the login.

Then ask if they're sure they don't just want two logins.

Nah, users are notorious for finding a way to bypass security and proper procedure just in order to be lazy. If you install facial recognition as a requirement to login on Monday, by Thursday the users will be swapping faces to get around it. Anything to get out of memorizing their passwords!
 
Nah, users are notorious for finding a way to bypass security and proper procedure just in order to be lazy. If you install facial recognition as a requirement to login on Monday, by Thursday the users will be swapping faces to get around it. Anything to get out of memorizing their passwords!
Last week one of my SOs and I were dropping some supplies off to a friend at her boat when she decided that this was the perfect time, about 9PM, to drop down to her excellent local pub. She was paying, for the three of us, via Revolut. The facial recognition was hilarious, she has to scrunch up her face for the app to accept her.
 
That scandal that has hit our company and has featured in the UK Sunday papers still hasn't been mentioned by management. About six months since the implementation... tumbleweeds.

Explains why we can't get simple changes to THAT system done in anything like a reasonable time, because they're fighting the terrific skip fire
 
Nah, users are notorious for finding a way to bypass security and proper procedure just in order to be lazy. If you install facial recognition as a requirement to login on Monday, by Thursday the users will be swapping faces to get around it. Anything to get out of memorizing their passwords!

Now I'm imagining them carrying in a cardboard cutout of each others' faces on a stick.
 
//Long story short//

Person B, the one who isn't allowed on job searching sites, mans the desk most of the time doing normal front desk stuff, answering the phone, greeting people and directing to places, accepting packages, nothing out of the ordinary.

Person A mans the desk during a specific timeframe when they do like a "speed dating" version of job interviews, a bunch of people rapid fire, weeding out the people who don't deserve a full sit down interview. Person A has job searching sites up during this process to review these applicants.

No it doesn't make any sense to me either.

So how did it get resolved in the end?
 
Status
Not open for further replies.

Back
Top Bottom