Soldato
It's a point to raise at least. Not signing the policy shouldn't mean you can be excused for wreckless behaviour.
In a spot of bother at work.
- Thread starter Shikkaka
- Start date
Indeed, The policy we had in place stopped user logging in until they signed the agreement, At which point their account was unlocked. Just something to think about
Thankyou thankyou. We also have a policy which pops up when signing it. God damn, why didn't I think of that.
EDIT: It basically says they agree to the one he hasn't yet signed and it is available from the IT Dept.
Last edited:
Soldato
Awesome stuff
Lol, why do you say that?
How do I go about speak to a union rep? Never done this type of thing before.
He has a contract that says he should not save important docs locally.
He did and they was lost. So he has not done his job as he should.
Don't you know who your union rep is?
Awesome! I've gone from dreading this meeting to rather looking forward to it. Should I accept some of the blame though as effectively, I've not done my job properly aswell, a one off mistake though.
I have no idea. How do I find out?
Caporegime
I'd make this point, if its not in a place to be backed up, its his problem, also...if you've migrated? Have you done clean installs or what? Surely the files would be stored locally somewhere if its an upgrade?
Oh and this...this happens where I work, we re-iterate the fact that locally stored files are not backed up, save them to a user area on the server where it IS backed up!
A bit confused as to why this is being laid on the OPs lap, sounds like management on both sides have cocked up. IT for not having backups enforced and his own department for not ensuring backups were being checked/carried out by users who were properly trained.
I'd be particularly annoyed if I was hauled into this on the day I return without having any official warning or time to prepare.
If there was no plan or documentation with little or no supervision by more senior members of IT then it can't possibly be landed on the OP. I'm a senior in our team and the buck stops with me, not the guys who work under me if I haven't trained or given them proper documentation and guidance. Department structure seems messed up where the OP works, the buck doesn't stop at the person who's doing the work if he/she has had little or no support to carry out important duties.
Was there ever a risk assessment done, I hate them but this sort of failure to backup due to long paths etc is something that should have been recognised and checked. Likewise a backup of the old systems could have been made "just in case."
I'd be particularly annoyed if I was hauled into this on the day I return without having any official warning or time to prepare.
If there was no plan or documentation with little or no supervision by more senior members of IT then it can't possibly be landed on the OP. I'm a senior in our team and the buck stops with me, not the guys who work under me if I haven't trained or given them proper documentation and guidance. Department structure seems messed up where the OP works, the buck doesn't stop at the person who's doing the work if he/she has had little or no support to carry out important duties.
Was there ever a risk assessment done, I hate them but this sort of failure to backup due to long paths etc is something that should have been recognised and checked. Likewise a backup of the old systems could have been made "just in case."
Soldato
Looks like you are out of a jam Steameh. The one good thing this thread has done is helped you logically think things through and arm yourself with what you need to go in and fight a battle should you need too.
As I said earlier, the main point here is not who is to blame, but what can be done in future to stop this happening, etc. Go in prepared for that too and you can't go wrong. People make mistakes, the one that "you have made" was unforseen and could happen to anyone.
The fact that the user is crying because he hasn't followed policy isn't really your problem but the event has brought to your attention certain issues that will be dealt with accordingly
As I said earlier, the main point here is not who is to blame, but what can be done in future to stop this happening, etc. Go in prepared for that too and you can't go wrong. People make mistakes, the one that "you have made" was unforseen and could happen to anyone.
The fact that the user is crying because he hasn't followed policy isn't really your problem but the event has brought to your attention certain issues that will be dealt with accordingly
Basically 'document management' is an addon to word, excel and outlook. When you click save it prompts with a different save box to upload this to the DM server. It's a crap system really but has been put in place as we legally have to keep all files for so many years.
We do clean installs over the network so the whole partition is wiped.
Caporegime
Actually, I used to work for a repair company and when you sent away your laptop for example to be 'checked over' it would guaranteed be coming back to you blank.
yes they said back up data before hand, but they'd literally restart a fresh install, even if there wasn't a problem with the damn hard drive
Well if you're given fair warning beforehand, I'd say it's fair game, it's a form of disclaimer that removes any liability from them.
LOL if they tried to blame you because he hadn't signed the document!
So you have to backup users stuff until they sign it! If i were a user i'd never sign it.
You could accept a portion of the blame, but not all of it.
Good luck in there hearing, when is it?
So you have to backup users stuff until they sign it! If i were a user i'd never sign it.
You could accept a portion of the blame, but not all of it.
Good luck in there hearing, when is it?
The planning and communication in this whole roll out has been none existant. You will hear this from the other guys I work with and my own boss.
They've given me till Thursday so not too bad I suppose. Still, wasn't expecting it the moment I return.
We have a tick sheet which we go through to ensure it's a thorough job but even that has grown in size as they realise bits are missing.
No risk assessment at all and they are just now thinking of backing up the old system 'just in case'.
This Thursday! And thankyou.