Discussion Locked

When a network administrator puts in his 2-week notice...

0 helpful
166 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

... what do you do?

Immediately remove him from service, disable all his access and pay him til his last day?

Trust he won't do anything bad and keep things status quo til his last day?

Quietly monitor everything he does and pull some of his privileges out?

Assume he's already filled his iPod up with everything already he can use against us later on down the road?

166 replies

by dr dij

to:
be sure you know all the passwords to devices such as routers and root passwords to systems if you don't have other admins for same systems.

be sure you have working backup tapes

be sure you have documentation of his day to day procedures both for normal ops and to fix things that break regularly due to load, etc.
(e.g. we had a router that crashed when too many users and only one net admin knew the 'fix')

Is there someone else who can work with this guy in last two weeks?

In an ideal setup you'd have a log device for system activities somewhere else that only the admin of that device could alter (e.g. another server that admin didn't have pwd to) and you could go back to this if anything 'blew up' suddenly.

I left a company with a paranoid tyrant boss, and got a call a couple weeks later. It was to ask where a file was, which was fairly obvious. I told the guy where the file was and didn't think much of it, tho I wondered why he called.

I found out months later from someone else who worked there that the system had crashed after I left and they were fishing to see if it sounded like I had anything to do with it. It was a hardware crash which I as a developer couldn't mystimagically create but the guy was paranoid.

I suppose the answers to your questions could depend on his record and how he's perceived.

Was he an egotistical dependancy builder who made people dependant on him to fix things because only he knew how and wouldn't show anyone else, or just a normal person?

I'd consult HR; Did this guy not get any promised raises or bonuses like the guy at the brokerage firm who planted the logic bomb? Has he made any statements about dislike of the company in last couple years? Any major arguments with other depts or people he dislikes?

by dmckay2003

I have been in this situation where I was layed off and immediately my email was locked! I wasn't able to send my farewell email even though I had no hard feelings. I was asked for all the passwords for all of the network appliances and gave my boss the admin password to everything. Even if you do have a grudge against a former employer, it seems to me that it would do you more harm than anything to plant a bomb or cause any loss of productivity. You have to remember that even though it's illegal to say something derogative or make a prospective employer feel like this person would be a bad choice it happens all the time in this industry. Why bother to do all the schooling and all the blood sweat and tears that we as systems and network engineers have to endure to get where we are if were going to destroy our career because of a job that didn't work out? Maybe it's just my age and the 20+ years of doing this that has shown me that making stupid moves like sabotage can end up only in a bad way and can never really pay off. Besides, didn't the question state that he gave notice? I would have to beleive that he is just moving on as we all do when we feel stagnant or need a change.

Just my thoughts>>>>>>>>

by jcdshs

I totally agree.
I've been the network admin at my current place of employ for 11 years. I have always done a good job, i am trusted by all the staff here,...You get the picture.
If I decide that financially I can no longer resist the offer of a bigger pay packet (I'm 47, not getting any younger) or a new job with different challenges why would I suddenly overnight turn into the world's biggest security risk? I have always been totally professional in my approach with this company so why should that change all of a sudden?

by dr dij

because its happened to us. One employee of a school district my former boss was consulting with started being 'too stressed' to come into work. She was the only one who had the admin pwd to a unix system. She wouldn't give it to anyone. And they had trouble firing her because school district, not private employer.

Another person (not system admin) wouldn't document any of her job, and erased production templates before she left. We had to scramble and rewrite some of these systems. Kind of our fault too for not backing up her PC and making her write procudures before that.

by tony hopkinson

on how good your procedures are. If he's a critical, with lot's of secrets, you are SOL.

Is it an amicable leave?

If they are good pay the guy, let him go. shift all the passwords, and breathe a little safer.

Assuming he's going to leave you in the lurch and treating him like that, is pretty much a self fulfilling prophecy though.

by mjd420nova

We have in place an exit procedure for just those reasons. It does consist of password and access procedures for all systems and hardware. Company already had serious problems in this manner and started the routine to guard against problems. Also the manager has on record all needed info in the case of major failure or emergency. We had the lead administrator depart regretfully due to a traffic fatality and left things in fine shape but no way to make any changes. Took three weeks to cycle all hardware thru default settings to gain control and reset passwords. I wouldn't wish that kind of hell on anyone but my worst enemy.

by gadgetgirl

get someone working in parallel with him. Make sure that person takes lots of notes for things that may be needed in future. Also keeps an eye on what he's doing.

Next, look at his documentation. Make sure it's up to date, readable, followable, and makes sense. If you have time, check it through in a live situation. (I know someone who left a load of micky mouse paperwork, which wasn't checked until a failure and was found to be absolutely useless)

Don't just check your back ups, check the restores, too. All programs have fads and foibles - you need to know "which way around" the program needs to be done. i.e. should folder creation be done first or last? Seems silly, but some programs crash and die if things are done in the "wrong way".

By all means, get all his passwords. But, please, quietly check them ALL. I know of a situation where passwords were left; the first six worked, the rest didn't .....

Pull any privileges he doesn't need on a day to day basis. Gives him less opportunity to place havoc with your systems.

For goodness sake, take his ipod, and any other devices off him! While he's still in your employ, you have a right (or at least you do here in the UK) to check his personal possessions for data removal. It's probably already gone, but by asking to check them, he'll think twice about using any data he has. If necessary, get him to sign some form of words on paper to legally ensure he can't use/keep IPR/patents on anything related to the company.

Make sure all his user accounts not having admin access are scheduled to expire the minute he leaves the building.

And the minute he leaves the building, change all the admin passwords you have on that checked list!

(Needless to say, double check any that allow VPN/remote access - oh, and look for any programs that allow that too, in case he's left himself a back door.........)

Let us know how you get on.

Best of luck - been there, done that, escorted the guy off the premises. You need all the luck you can get!

PM me if you need more

GG

by mailrick

Disable all his access and pay him til his last day. Just discussed this yesterday in Windows Server 2003, 70-298 class. He shouldn't take it personally - this is just a fact of life/business these days - unfortunately.

by feral

If his departure is amicable and you can only discover that with a thorough debrief then you should not have too much drama I would think.

During his last two weeks make sure all his daily procedures are documented and you obtain passwords to all systems as suggested.

Depending on how you intend to fill his shoes, I would hire a contractor from a reputable firm immediately to shadow and learn the role with a possibility of it going to full time.
Once the contractor is in place then he can assume the role of admin in conjunction with the incumbent and cut over the job. The outgoing admin should be ok with this.

Make sure the contractor is properly qualified so that he can call it out if he sees something amiss, also brief the guy to bring it quietly to your attention if he suspects mischief then go hard.

Do not cut his access off unless you are going to terminate him immediately, that would be suicidal to the business especially if you do not have his accesses sorted out.

If you do for whatever reason need to terminate him immediately be careful, co ordinate this so that as he is walking to the office for his termination have someone capable disable all his access, LAN, WAN and remote and take control and ownership of his profile and data.
Check that there are no suspicious accounts on servers and disable them if there are and so on.
Once his access is removed escort him to the office have him pack and escort him offsite, do not let him log in again for any reason.

by masontony

I was laid off after an eight month period with a company ,I was paid up for my two week notice and told to leave the laptop ,van keys and anything else .I was then escorted off the premises.This was not a nice feeling and was uncalled for .
My son also works in IT and when he was attending a course which was out off his own pocket the company let him go .He was also escorted of the building and treated like a criminal .I understand they have to protect them selves but there is no call for this.

by puchatek2

Regardless of the sysadmin's reason's for leaving, general character, or relationship with management, you send him/her home, paid to their last day, of course, and immediately disable all their accounts, and change the admin passwords on all admin accounts and any other accounts with elevated privileges. Better to be safe than sorry.

by angry_white_male

... it's nothing personal, but once a network person with all of the admin rights indicates he wants to leave, he becomes a liability. IT security has been my focus for a long time and it's all about mitigating risk. Aside from relocations and following hearts, most resignations aren't because they're happy... most people quit because they don't like their job, boss, salary, co-workers, etc. So there's a little bit of animosity.

It's nothing personal. No one is accusing anyone of any wrong-doing, but the potential for one last hurrah because what are we gonna do - fire someone who just quit? (and there's plenty of stories out there about this sorta thing). Laws are still iffy at best when it comes to prosecuting these things.

My goal is to do what's in the best interest of my employer, not someone who's about to walk out the door. His loyalty to me evaporated as soon as the 2-week notice landed on my desk - why should I return the favor? It's business.

by big ole jack

It's never good to come off being an a--hole when terminating an employee. Also, there will be less chances of the former employee trying to enact revenge or spiteful behavior if they are terminated in a professional and appropriate manner.

by markck

i can smell you a mile away you little jerk. your one comment said it all, why should i do him any favors? typical management double speak. again, look in the mirror and realize the small, small pathetic man you really are.

by capnpauly

It's obvious you are concerned, but do you really need to be?
I can understand why you'd want to immediately remove his access to everything, but until you get someone to take over for him (at least in the interim, like a tech ready to 'step-up' or the CIO to focus on the administration side for a while) removing his access to things may cause problems because whenever he needs to do his job function(s), he will need to come to someone in authority to log him in or do a 'Run As'.
Going back to the 'has he given cause for concern' statement, has he? Does you company make people take a behavioral/psychological questionnaire (a`la PRADCO)? Were there any 'red-flags' that would give cause for concern?
I'd agree that I'd try and get someone to shadow/work with him. As long as you can do that, go ahead and limit his access and just make him show the other person where to go, what to do, and how to do it.
Good luck!

by zodder

I was in a similar situation, but I was laid off instead of giving my 2 weeks for another job. While the urge for revenge was there, there was no way I was going to put my reputation on the line or do anything destructive to the system. I consider myself a professional and acted as such until my last day. I gave copious notes to management, created a comprehensive password list, and helped the outsourced IT people as much as I could until my last day. While I was pissed off at the circumstances surrounding the lay off, I wanted my legacy to be that of someone who cared, was competent, and was trustworthy. I hope I'm the norm and not the exception.

by rvfrueh

This is what I have always done when leaving - I make sure the next person to do my job knows how, and I have all of my access limited to basic functionality, and then shadow them and have them do all of the work for 2 weeks.

by angry_white_male

I know he wasn't a happy camper the past couple of months working for me. He would often go around me and to my boss (god forbid I make people earn their paychecks here and follow the rules)... and he even decided he was going to boycott my weekly one-on-one meetings.

If it were up to me I would have walked him out the door once I got his notice - but I'm just a mid-level manager, not my decision.

I've already yanked his remote access, and I'm slowly cutting back his admin privileges that won't impact his duties here.

by big ole jack

Being an owner of my own firm, it's wise to never create enemies with your fellow coworkers or subordinates. There is nothing more sinister than having an employee leave on bad terms and taking all the access password with him/her. Be sure you have everything documented and make sure the usernames and passwords you have do indeed work...don't take anybody's word for it. It is standard practice to escort the person out as soon as notice is given, but if the relationship was good and there was a good level of trust, then you can let this person serve out their final two weeks. In your case, it sounds like this person might resort to malicious behavior, so I'd err on the side of caution and legal liability and boot him out pronto.

by dr dij

no matter what you do, no matter that your paying them a good wage they think they should have more, no matter that you're the boss they make people dependant on them as they won't show anyone else how to run a process to generate data, etc.

There's endless bogus reasons to be disgruntled and some will be whatever you do. You can't make friends with them all. You treat them in standard professional fashion and they're still intolerable.

by taboga

That's what it boils down to, doesn't it? I mean, if anyone would have ever treated me like a criminal suspect after I had done the professional thing by giving an appropriate notice, I would have rescinded it and quit on the spot!

If an employee is the ONLY person who has access to something, or is the only one who knows the "how to" for something -- that was management's first mistake. A lesson should be learned THERE.

But if the guy is a professional and is doing the right thing and I already have someone who can step in (if only temporarily) and do his job -- I let him go right away and pay him for the two weeks. Why? Because he is leaving for a REASON. It may be money, it may be he is not satisified with job, future or whatever -- but he's leaving for a reason. And if I am paying him for a two-week vacation before he starts his new job, whatever his reason for leaving was, he will probably leave on good terms and not have a bone to pick with us in the future. And he won't be going around for the next two weeks telling everyone how much he's looking forward to leaving and how the job and/or the company "sucks". We don't need that. And besides, no one really does any WORK in their last two weeks anyway -- so it's not like you're losing anything by letting him go early.

by beoweolf

Explain to the departing admin that you need to insure things will function in his absence, so he will not need to directly address any more issue. What you want him to do is monitor the system and direct any anomalies to the person he thinks is best suited to resolve the problem. Any problems that person has repairing or configuring the problem - he is to assist by suggesting the correct procedure, directing the operator to the correct documentation. If documentation is non-existent, he should spend whatever time he is not assisting, in preparing those documents.

Also, the day that you are first informed of his resignation, take a full system backup which should be stored indefinitely. When his replacement arrives, another full system backup should be done as part of turnover. The before/after backups are a good way to protect both administrators. The unfortunate truth is - it is also SOP for the arriving administrator to blame any mistakes on "previous" administrators. Taking both backups is good way to keep both of them honest.

As far as passwords, access security, etc. There are more than enough suggested procedures, processes detailing how to handle this subject - matter of fact, each functioning IT department should have this in system documentation along with disaster recovery and other "remedial" procedures.

In the past, when I have left a company, I would have the next inline change all passwords while I was still there. That way he would have them and I would not know them. If something came up that required me to use that level of access, I would have him change to a temporary password, do what I had to do, then he would change it back to the new secret.

In essence, I put myself in the role of a consultant until departure. (Note: True to form, I was still blamed for inadequacies of the new staff, but the preparation I did before leaving was able to successfully defend my reputation. Remember, your reputation; for honesty, integrity, organization will follow you throughout your IT career. It is in your best interest to defend it religiously, even after you move on to the next job.).

by myads1

Once I realized that a previous employer placed no value on what I did, I silently inserted ONE LINE of code that would shut everything the app I designed down after some odd number of days (20-30ish) if I didn't log in to the program. The error message would point any debuggers in the wrong direction, and the strange timeframe would reduce suspiscion of sabatoge. At the same time, any sort of amicable leaving would have made me immediately remove this code (yeah they didn't appreciate me, but at the same time I didn't want to burn all bridges unless they did it first). So even your outline process, while much more secure that most mentioned, isn't fireproof.

by bwilkes8

From a management perspective, you have to way the good and the bad. How bad to you need his services? How much institutional knowledge does he hold? Have you noticed a decline is his performance or work? This is not an easy question because maybe he is a great person, no risk to security, and has been on staff since day one. Now a better opportunity, a career change or even a family tragedy has occurred and he is simply making changes in his life to accommodate them. You need to talk with him if at all possible to get a full picture of his situation, his mindset, his mood and then make a determination on how to or how not to deal with nixing his network privileges.

by turbinepilot

About two years ago a new business opened in the area and they began hiring staff, many of them away from other local businesses.

One of the existing businesses got the bright idea to immediately terminate any employee who gave their two weeks notice to move to the new company... without pay.

Seems the remaining employees at this particular business shifted their strategy to only give notice the day they were planning to leave.

Whatever policy you implement for the first admin's departure will be observed by the remaining ones. If an employee has an axe to grind he'll simply do the mischief before giving notice. The good employee who is leaving will contine to act with professionalism and integrity.

The point is there is no policy that you can implement that will prevent mischief. You should only placed trusted employees in the admin positions. If they are no longer earning your trust you should remove them from any admin position long before you get a two week notice from them.

by angry_white_male

We place a lot of trust in people all the time, but you won't always know if they have an ulterior motive until it's too late.

We will debrief the individual. Our staff attorney will read him the riot act - put him on notice that if we discover anything, that we will prosecute. Standard stuff.

We're yanking all admin access that he doesn't need.

I'm pushing to have him put on the bench til his last day since he's not doing much til then anyway.

by locrian_lyric

you just may teach your other employees to *NOT* give notice... ever.

Plus, your company may earn a bad rep.

by fixit

I have a friend who got the sit down with the lawyer treatment, and lost her admin privileges the day she told her boss she was putting in her notice because she was moving to follow her boyfriend.
The result of this for the company was a disaster. They treated her like a criminal because she gave notice. Her response was to simply use all of her vacation and leave.
So when they called her to ask her a question only she could answer she said I will be right down. She showed up with a new consulting contract they had to sigh to get any answers out of her at all. She wanted $1000.00 dollars an hour minimum one hour.
Within three weeks they had no choice but to sign it. And before you ask, she had given them all her passwords. She was just the only one who could do her job.

by bwilkes8

Why not just read him the riot act, give him two weeks severance pay and be safe instead of sorry. Sometimes foresight is a life saver.

by locrian_lyric

Either the person is trustworthy or that person is NOT trustworthy.

The fact that they gave notice is an indication of the former.

This kind of situation can be handled delicately without making the person and other employees feel criminal.

All you have to do is move to an immediate knowledge transfer, give the employee a "new best friend" who will accompany him to all meetings, sit with him for knowledge transfers, et cetera....

by audreyd

I agree completely with Turbinepilot! If management comes down hard on the employee who is leaving, other employees will notice; it could influence their own attitude towards managament, especially if they think the departing employee is fully professional and trusted. Angry_White_Male's name indicates to me that he may be reacting emotionally rather than rationally. If the employee was always highly trusted, the departure friendly, I wouldn't come down so hard on the guy during the last 2 weeks. It sets a bad example for the rest of the staff.

In my world, we do that type of shutdown on privileges only for people who might have an axe to grind with the employer. After all, we have had to occasionally phone former employees to pick their brains after they leave.

by angry_white_male

He's only been with us for 7 months, and it was pretty apparent he wasn't happy here from the get-go... as if he made a mistake in quitting his last job and coming here thinking this was a big step up (it was a lateral move for him at best - and I made it clear to him that was the case).

Tried telling him to hang on - we're hiring more people soon so he could work on stuff he's got the talent for, but he didn't want to hang around much longer.

He hasn't absorbed that much institutional knowledge, so there's not a lot to transfer from him other than some updates on the projects he was assigned to, and that are mostly done anyway.

by locrian_lyric

When their systems crashed and they were losing 1 MILLION a month, they begged him for help.

He told them to pound sand.

by fixit

The funny thing is they called me and wanted me to fix the app., I program in perl and c# and Basic etc., but I didn't write the app. and she didn't comment the source other than basic variable explanation. So they are losing money hand over fist and trying to get me to trick her into telling me how to fix it.
But I am not a programmer, I am a network administrator and hardware geek. So I tried but in the end they had to pay. That is what you get when you treat good people like crap. The company did fire the manager that caused the whole problem, but it took them a while to do it.

by locrian_lyric

My friend's former manager and his bean-counting buddy BOASTED over how much money they saved by letting him go...

He was making WELL into the six-figure range. This guy is about the most brilliant guy I know, and was worth every penny, btw.

Anyway...

Jerk1 and Jerk2 BEGGED him to bail their backsides out after they were made to explain WHY they let go of the only man who knew what was going on with mission critical systems.

He was already working elsewhere and wouldn't go back to that commpany for any price.

The two jerks were eventually fired, but like with your friend, it took a while

by big ole jack

He/she can countersue and state all sorts of things about your company, whether or not they are true, but your company will get sucker punched with a suit and will waste money on defending itself against a frivolous lawsuit. People will do all sorts of spiteful things when they are angry, so don't push your luck by throwing your attorney and legal mumbo jumbo at terminated employees. They've read the policies prior to hiring, signed on the dotted line, and therefore are bound by the legal language. By saying things like "If we find anything...we will prosecute". Define what you mean by "anything" and how would you prove it was the terminated employee's fault and not somebody else at fault? Labor laws are on the side of the employee, so be careful in how you deal with a termination, as many firms have been sued out of existence by terminated employees for improper termination or other matters deemed to have been violations of labor laws.

by locrian_lyric

You can do anything to a person and their anger will subside, unless you humiliate them.

that is the one injury that no man has ever forgotten and will take years to seek revenge over.

by bwilkes8

But foresight is better and it sounds like there might be a little there, protect your resources, deny his privileges and reassign him a guest account, CYA, cover your butt and your company's. But as many have said, treat him with respect so that others will see that the company doesn't "dump on" an individual leaving.

Tough call to make, but leaders have to make decisions that not everyone will like.

by big ole jack

It's bad enough to get walked out the door like some criminal, but it's even worst when they call you after termination, asking for advice or information. Termination is termination, and if anyone from my former employer wants further information from me, they will have to cough up a good chunk of change for my consulting services. Basically, they reap what they sow when they treat terminated employees like potential hackers or disgruntled employees. You want my help after you boot me out the door? Sure, but it will cost ya big!

by online4

I was in a situation similar to Zodder's, but instead of being laid off I was fired. I worked for a law firm where my boss, the executive administrator, was answerable to the shareholding attorneys, one of which I had apparently pissed off. After nine years as senior half of the IT department, my boss had to let me go because he was told to. It was a total surprise to me, and was quite upsetting to him.

My boss bent over backwards to ease the pain, while taking care of the firm's interests as well. They gave me all the help they could finding a new job, and kept me on at full pay for two months with the understanding that I would receive bonuses if I stayed and helped them through the transition. They even let me keep my firm laptop and PDA. They brought in a more than competent replacement who has only had to call me twice for minor things (for which I didn't charge the firm; both items were answered with a one minute phone call).

I spent six months finding a new job (more pay, less stress, and much closer to home), but I still have friends at the old place and even drop in occasionally. Neither side burned its bridges, and I feel good that we both acted with integrity. I still don't know which attorney was responsible for my demise (though I have my suspicions), so I just don't talk to any of the shareholders anymore.

by big ole jack

They are spoiled beyond belief and believe that the world revolves around them. Good luck trying to support these clowns who simply fail to comprehend that what they want and what is technologically feasible are two different things.

by big ole jack

It's never professional to boast or brag about an employee's termination, whether it be voluntary or involuntary. I'm glad those two jackasses got their butts kicked out of the company because in the narrow minded MBA mentality of trying to "save" the company money, they actually lost money for the company by creating an immediate void in a system that required specialized talent. Also, it's the management's fault for creating this "one man show" situation in which nobody else knows anything about the system, other than the immediate guy who was fired. I can see why he didn't want to share his knowledge in the name of job security, but such an attitude is also wrong on the part of the employee.

by your mom 2.0

Couldn't a disgruntled employee be convicted or sued in a civil case for sabotaging and/or stealing data?

You mentioned that the employee could have loaded his iPod with info to use against your company...are we just talking trade -secrets and proprietary info or something illegal that the employee could use to blackmail you?

I'd like to think that something could be done in a legal sense if someone sabotaged my systems or stole data.

And even if this guy held all of the "keys to the kingdom", I'm sure you could farm out the job of recovering this info to a hired gun.

by bharris09

The iPod may contain records of the company's illegal activities. Admins may very well know "where the bodies are buried"..

by dr dij

i.e. fed employee Gonzales who has 'forgot' about what happened.

In the case where the school IT employee was the only one with the unix system admin password the system had to be reformatted.

What would a case have done? Maybe a year later it would have come to trial, and she could have claimed she 'forgot' the password.

And in the unlikely but possible case she really had 'forgotten', maybe stroke or hit on the head or car accident, what would putting her in jail accomplish? If she had passed away, they'd be in same position but no legal case.

In the meantime they were out of use of the system for a year if they did that. In the end bad managment put themselves in that position by having only one person knowing critical info.

by locrian_lyric

He had a FINE attitude and did not horde knowledge, nor did he do anything for job security.

Anything they wanted, they got from him. When he asked for help, or to cross-train others so he could take the occasional vacation, they poo-pooed him.

His hands are completely clean, which made the situation all the more satisfying for him.

They contacted him six months later begging and pleading, and he let them twist in the wind.

by jmgarvin

Find out why he is leaving and what the conditions are. I'd also try to get his replacement online before he leaves. This means that the replacement is available and trained, but also it makes it much harder for him to walk with a bunch of data.

It also boils down to trust. You trusted him when he was still with you, why should you stop trusting him now?

by apotheon

In fact, an experience with an employer taking the "lock out technical personnel the moment they look like they're leaving", and losing some data that was actually [b]mine[/b] as a result, has led me to believe that in every case I should always ensure I have personal backups of [b]everything[/b]. I'm an ethical guy -- I'm not going to misuse any information I have about the company and its network -- so anything I find I have that I shouldn't after leaving a company, I'll just delete. The risk to the companies out there created by the prevalence of this sort of untrusting attitude is greater than the benefit, though, because it just teaches all technical personnel to prepare for being locked out.

. . . which means some of the company's data is likely to be duplicated off-site.

I know what I'm doing, and am attentive enough, to ensure that I don't put an employer at risk when I prepare to cover my own fourth point of contact. Not everyone is me, though. Do you really want to encourage them to, for instance, keep backups of critical corporate data on poorly-secured home computers?

by your mom 2.0

...that basically says that if you screw with us or steal our data for malicious purposes, we'll sue and/or arrest you.

Seems like it would drive the point home. And when done correctly, it comes across as standard procedure. Maybe right before the exit interview.

by support

There really is no reason to fire him/her immediately.

Admins aren't (usually) stupid. The admin did not make this decision overnight, and has already copied files or done damage to your resources if s/he was inclined to do so. 99% of all admins know that they will be dismissed immediately and take any steps they feel necessary BEFORE they hand in a resignation.

Use this time to get all of the knowledge that you can from the soon-to-be ex-employee. S/He should not be doing daily work, but should be transferring critical job task, password and company process information to one or more persons that are staying.

If your company was smart, you wouldn't have a single admin anyway and this procedure should be pretty painless.

Hire a replacement asap and always be sure to have 2 equally skilled employees assigned to any position that can bring your company to its knees.

Your best line of defense is open communications. Unless you keep your admin in a server closet, s/he will reveal his/her feelings about the job and company in his/her daily conversations. If they are ALWAYS negative, first look into the complaints and see if there is truly a company problem that should and can be addressed. If the complaints can be addressed do it.

Second, if the complaints are unfounded or simply out of the company's ability to change go ahead and find a replacement for the complaining admin before you get that dreaded letter of resignation. If you (DISCRETELY) find a replacement, that's the time to call in your admin, fire the admin and lead him/her out of the building.

by fixit

She was not hording knowledge. She repeatedly tried to get them to let her train some one else to handle vacation time etc. but they were too tight. This kinda stuff happens when people kiss ass to get into management instead of work to get there. The manager that she worked for could not do ANY job in his department, and had no idea how critical his Lead (only) programmer was.

by jmgarvin

It seems like everyone is ready to hang this guy, when it isn't apparent if he's done ANYTHING besides quit.

First and foremost we are professionals. Second, it would have to be a highly unethical person that would steal your data and bring it with them. Third, do you treat all employees as if they were thieves when they leave?

So bizarre.

by apotheon

People are so short-sighted that they think the only way to protect yourself from bad people is to punish everyone, good people included.

by angry_white_male

I should probably add that we're a public sector employer that has to live within the framework of regulatory compliance. We get audited regularly by the state and they look at things like controls, process, policy, etc.

I run things by the book here. If a departing network administrator wants to screw things up - it's my ass on the line, not his. I have a mortgage to pay and mouths to feed and I'm not gonna let someone leaving us screw it up for me. Sorry for not being squishy about hurting someone's feelings on their way out the door. Nothing personal, it's business. It's best practices. It's having good controls in place. It's ensuring that my IT dept isn't front page news because of poor security practices.

by apotheon

"[i]Nothing personal, it's business. It's best practices. It's having good controls in place. It's ensuring that my IT dept isn't front page news because of poor security practices.[/i]"

It's a good way to ensure that your lack of trust encourages people to distrust you, leading to more likelihood of someone [b]wanting[/b] to screw you over.

by fixit

You sir are a pencil pusher! I have never been 'job scared', it literally takes me two days to find a new job if I quit one. If you allow yourself to treat people poorly because you are afraid you could lose your job, you deserve to lose it! Integrity is worth alot more than a paycheck.

Some one, in a comment above, wrote that your reputation will proceed you in your I.T. career, and they were very correct. It will also proceed you in your management career, probably even more so. Loyalty is a two way street sir!

by absolutely

Not your commentary, but the subject of it.

[i]I run things by the book here. If a departing network administrator wants to screw things up - it's my ass on the line, not his.[/i]

I've noticed that what you're saying is true, but what a pile of hooey the situation is.

[i]Sorry for not being squishy about hurting someone's feelings on their way out the door.[/i]

Feelings be damned, it's taxpayer expense that annoys me. It's utter hogwash that the only way for you to have a reasonable certainty that you [u]won't[/u] get wrecked is to waste taxpayer money. In turn, it's our fault as taxpayer/voters that we've condoned, encouraged of demanded this crap. Somebody should do something about it.

:^0

by tonyackerman

Been a lot of discussion on this, most good, some not. My 22 yr's worth of experience, from both sides of the fence and in both good and bad situations below.

First off and I realize that it's a bit late now, plan time into ANY admin's schedule for documenting procedure. Very few places that I have worked seem to realize the importance of planning this into the schedule, and almost none realize how randomized an admin's day becomes in such a short period of time. Give them time to breathe and expect others in the company to abide by it. These people are the ones that are keeping the wheels turning, give them a chance to keep their tools, documentation and house in order.

The documentation doesn't have to be written in detailed tech speak, but it should outline enough detail to allow a relative newcomer to be able to follow the notes and keep your company out of trouble. Any admin worth their salt will be willing to do this and be willing to share their knowledge. Being the priest/priestess of secret knowledge is old school and should get you shown the door. Sharing your knowledge shows that you're a team player and should entrust you with greater responsibilities and greater opportunities.

Second, do NOT alienate this person UNLESS there is a confirmed reason to suspect a potential security breach. If that case exists, get them out the door NOW and live with the consequences. Hire in whatever expertise you need to pick up the pieces, but don't put yourself at further risk by keeping that person around. If this person is has not given you reason to suspect malfeasance, then don't treat them like they're a criminal. Treat them with respect and professionalism.

Third, explain the needs that you have and ask their help and cooperation in minimizing the impact of their leaving. Do not be patronizing, be professional and clearly outline your needs (not expectations, your NEEDS, there is a big difference). Ask their buy-in to meet these needs. Ask them if they would be willing to extend their time with you in the case a catastrophe were to occur (so few places plan for this contingency). Jointly determine what set of conditions need to be met in order to bring your operation back online. If this person is willing to extend their stay under this contingency, come to an agreement on how long that extension would last. If not, you must to put a plan together to cover this contingency.

Fourth, ask them what they can do in the time remaining to help meet those needs and then clear their schedule of anything that would obstruct their ability to meet those agreed upon objectives. Explain that from your position, meeting those needs is now the most important set of objectives that they have to meet, everything else short of a major catastrophe is secondary, and MEAN it. From experience I can tell you there is nothing more frustrating than to have work that was deemed critical path interrupted by some user who was having trouble with a print job. (WTFO, I thought that I was to focus on this procedural documentation and not have to deal with this routine stuff. What is really important here, my knowledge or squeezing me for every last little fixit job?).

Fifth, explain that immediately AFTER they leave, the passwords and access that they have has to be changed, not by them. This isn't a statement of distrust, it's a matter of procedure and for security audit reasons. They should expect this and it should not come as a surprise, but it needs to be clearly stated and articulated for legal reasons. Outline what accounts are going to have passwords changed and what access methods are going to be disabled. Ask if there are other accounts/access methods that THEY know about that have not been mentioned. You're showing them the trust and respect they deserve and you're giving them the chance to show that that trust and respect is well placed. By offering the chance to present any remaining information that you may need to know and to confirm what needs to be addressed, you've covered your butt and theirs. This is CRITICAL.

Last, leave the door open. If this person was viewed as valuable enough to add to your team when they first came on, after they leave you may find that they had become even more valuable and you just didn't realize it. You may find that you want them back and for them the grass may not be greener after all.

If an admin is really good at their job, you won't even notice what it is that they do, that's what they should be striving to achieve. Too often, admin's are not very good at bringing their achievements to the attention of those that they work for, and as a result their work and achievements are overlooked and unappreciated. Guard against that and your retention of these contributors will be much better.

by jcdshs

You have posed an incredibly ill-defined scenario with absolutely no background info, thrown a little bait into the water with your accompanying prompts and then sat back to wait for the sharks to circle - and boy did they.
Was the network admin ill - maybe just been given 2 months to live by his cancer speciallist? Was his partner suddenly diagnosed with a terminal illness? Did he win lotto last week? Did a filthy rich uncle just die?
How long has this person worked for your company? Are they a trusted employee? Have they been called up for active service in the armed forces?
There are SO MANY reasons why this person may have put in 2 weeks notice - remember, they are not being fired! They are asking to leave.
First thing is to get someone to sit down with them and find out exactly why they are giving notice. Then you can start taking any appropriate responses you feel necessary.
Maybe the guy did win lotto and he is going to buy out YOUR company. Who will be the first one out the door then if you jump in and crucify the guy ;-)

by techytype

Yours is the first reply to this thread that caused me to want to reply. Most of this thread is valid, from a BUSINESS perspective. People seem to forget that we should be working to live, not living to work. Yours has hit the point with accuracy and class. Thank you.

by neon samurai

I've been reading the discussion and with each new post, can't help thinking; if the original poster is reading TR, what are the chances that the business network admin is reading TR?

Yeah, most are replying from the Business and IS point fo view. A topic like this get's the security geeks all riled up real good. I don't think it was ever mentioned if this is an amicable departure. Knowing the business relationship and reasons for leaving probably completely changes the responses given.

by dr dij

lots of good answers have covered all the possibility and suggested reasonable answers and when to trust the people.

We got a good discussion out of this. Did you even read all the post?

by tony hopkinson

If they bin you they expect you to get dischuffed

If you leave they figure you are dischuffed, they just missed how they managed it.

Personally I would be very offended at the idea, that I would sabotage something before I left.
There again I did a departmental switch at one place, and they found it convenient to leave me with my access, 'just in case'

A month or so later, something went wrong and they rang me up to see what I'd messed about with! Nothing to do with me of course, but I pressured them into removing my old privileges for their cheek.

So it can work both ways.

by locrian_lyric

I also had occasion to demand my accounts to be deleted.

On another note....

I was laid off from a company in 2001, then went back as a consultant in 2006.

Some of my accounts were still there.....

SKEEERY eh?

by ananeo

I recently gave my two weeks notice, but for some reason nobody expects me to go anywhere, boy are they going to be suprised.
My integrity would not allow me to do something that could ollow me around the industry the rest of my life.
There lost, not mine.

by locrian_lyric

It's human nature.

by the same token, we have a hard time conceiving of the things we are not inclined to do

by sharpj

When I gave my notice after 10 years, my VP had all my privs removed except basic email send/rcv. Someone else packed my office and i was allowed "limited" access to the 20 bldgs around to say my good-byes, then processed thru HR and given 2 weeks pay. Like they say, it's just good business.

by mkameta

The damage if any to the Business would have taken place a long time before the 2 weeks notice would have been submitted. If a business really wanted to protect themselves no matter how large or small they are, then they should implement little things like, change controls, SOX auditing, IT Management processes and procedures then audit these on a scheduled basis. :-).

by angry_white_male

Problem is - we have no controls here... been fighting to get an ISO on board to handle these things full-time. I have my policies - but no means to enforce them, no time to document them. So I use best practices to cover my ass. I've gotten burned for doing so - but in the end, I know what I did was right and if it pissed a few people off who expected to get what they wanted without having to jump through the neccessary hoops to get it - well, if that makes me a prick, then I did my job.

So, I have to take the worst-case scenario approach and do what I can... unfortunately I have a boss who knows little about IT security - he's too busy kissing up to his bosses to give it any real thought.

This place is a mess - I'm looking to move on myself... in the meantime, I'm just doing what's right.

by seanpsullivan

I was given notice and was given the opportunity to stay for a whole month. Now I am blown away by this action however, my ethics and values came out on top. They see I will not do anything to damage or hinder the business.

by alxcsby

You have to understand that if he's planning on damaging your network, he's probably already done it. If he wanted any of your "incriminating" files, he's got them. Most netadmins are generally pretty laid back and friendly. If he's leaving with bad blood--over a dispute, etc.--there might be something worth worrying about.
A. You trusted him enough to hire him.
B. Any damage has already been done.
C. We're not likely to be that spiteful.
D. Removing his privileges is silly, he'll just bypass it.
E. Disabling his access is silly, again, he'll bypass it.
Just let him be and be thankful you got two weeks. After all, the new netadmin is going to need something to keep him busy.

by locrian_lyric

Not much to add to that....

A admim has your company's jewels in a vice at all times.

never give him an excuse to squeeze.

by dr dij

A. Ok that's true
B. possibly, if data theft but deletions and locking out of systems by not supplying passwords and procedures occur when he leaves.
C. professionals aren't spiteful but reading the news and examples I gave in previous posts show there are plenty of 'non-professionals' in position to cause your dept grief. There is little that can be done legally and even if you do the damage is already done. What good is winning a lawsuite against former employee who destroys your system when you're out of biz (the NJ company this happened)
D. removing privileges. if you feel the need then there are indicators the person isn't a professional. This is simply protecting your company. If he 'by accident' deletes or destroys stuff with his valid password I don't think you'd have much recourse legally. If he 'breaks in' by bypassing or using another password then you can show he was guilty of hacking / breaking in.
E. again, if you DO trust the person you don't disable their accounts. Again, if they bypass and hack in then you have an illegal activity. If they really needed it to do their job, then either someone shadowing them does it with their account, the procedure doesn't get done, meaning your company hasn't found replacement or shadow,..
if there is someone competent to disable the password then more likely there is someone to take over the tasks. if not and the password stays active because the person leaving is in charge of passwords, such as small shops is not ideal either. Still the company's fault for not hiring temp consultant, etc or having backup for the person.

by fixit

Ok, I built the companies network from the ground up. There is only one other person who knows even close to enough about it to start to stop me from logging on. How are you going to stop me from bringing your company to a stop if you treat me poorly? Why would you be stupid enough to alienate me in the first place. I am not a bad employee and I would gladly help a new comer fill my shoes if I was planning to leave. You are assuming that you are dealing with unprofessional people just because they have a reason to move on. Ever thought of just saying 'hey thanks for all the great years, come by and see us some time'.

by dr dij

some people DON'T think it will follow them around. What with companies afraid to give bad ref to anyone. And not everyoen is good or will do the right thing.. Some good books on insider theft of data also mention how to handle incidents of system and data destruction.

And I was saying in orig post to evaluate each person. e.g. do they have a history of complaining or disciplinary action, previous threats to quit, layoffs, turned down for promo or bonus, or other reasons to commit destructive acts?

by dr dij

means to someone that you don't trust them and therefore they're conna be ticked off about it and more likely to break thru the door and steal from you? That's what your saying sounds like. That's cyclical reasoning.

People will get ticked off regardless of how you treat them. You still need security procedures in place for destructive acts.

Insider theft (non destructive acts) tho is likely to have occured prior to the notice. So locking won't do much good in that regard as if it was going to happen most likely did already, except for (possibly) the departing sales person, etc who didn't think till last moment to take your customer list with them.

Or IT person who wants source code, etc but didn't think to take it earlier before notice.

by apotheon

Please keep misrepresenting what I said to construct straw men you can attack in lieu of actual counterarguments. I think that tactic is working well for you.

by neon samurai

Then the admin should already be pretty sure of how a good will departure should go. Assuming it ended under good relations, I, as admin, would be expecting my security to be reduced, tasks to be handed off and replacement shadowing me. Heck, if I'm admin and no reasonable security precautions are taken when I tell them I'm leaving then I know there's good reason to wish them luck and head off.

I would also just like to mention again that if this person is a network admin who does read TR, this may have been the wrong medium for discussion.

(Crap, did it again, anyone know where the dictionary I keep accidentally adding words to is kept? I'll go check the firefox folder under my ~ dir to start.)

by dr dij

such as lockdown, are not 'treating people poorly'. And a desire to keep a system running and protect your employer is not 'odd' or 'bad' as you seem to imply.

If you left the locks to your front door of your company unlocked any time or just after someone leaves, then he or someone else comes in and destroys everything, YOU will be the one who suffers, not him.

You may be out of a job. Locking down systems is simply due diligence and ITIL not some Orwellian security guards with truncheons nightmare.

To suggest people shouldn't protect their systems sounds incredibly stupid. Locking someone out of critical systems when they are about to not be employed anymore sounds totally reasonable.

You're going to do it anyway two weeks later.. Do you have no responsibilities? Perhaps you just graduated or something?

What would proceed him in his management career is if he let an infantile person who left or before they left, destroy a company when he could have had procedures to easily prevent this. the problem is you CAN'T trust everyone. No 'love everyone' words or glossing over change this.

Tho reasonable procedures such as evaluating risks of individuals, backing up, etc ameliorate and almost eliminate these risks.

by fixit

We are talking about a GOOD employee who gave you his two weeks notice. Not some one you are about to fire. People who give notice should not be treated as criminals. You never know the guy might just help you make the transition smoother, make him mad and you get no help.

by locrian_lyric

You can't please everyone, but some of the things *I* have seen go beyond the pale and have in every instance destroyed loyalty and morale among the remaining folks...

"Gee, did you see what they did to Dave? They took him to lunch and removed him from the system while he was out" (happened to a former coworker)

"Did you see that, they sent security to his cube, turned off his computer, gave him five minutes to pack up and escorted him out. Not only that, they searched him on the way out" (happened to me)

After incident #1, a number of folks found other work, and didn't give notice.

After incident #2, same thing.

You come down too heavy handed, and you get your remaining employees wondering how THEY will be treated.

by tony hopkinson

of an employee with no documentation on what they did, could do, or have.

Even if it's not hostile, you are still stuffed.

Two months wouldn't be enough time to hand over, never mind two weeks.

by jamie

1. Assume he is a human being.
2. Ask him if he is unhappy with his current job, possibly do this through an exit interview.
3. Ask him to guide you through all of the backup and restore procedures.
4. Ask him if he has any work related material at home, if he has could he please return it.
5. Ask him if he could train someone up as a temporary replacement.

This way he still feels respected and is likely to respect your company.
After he has left the building change the administrator passwords.

Jamie

by tuvals

If this individual gave two weeks notice and is a good employee asking him to document what he does is to much to little to late. If someone is leaving and you now, for the possibly first time have a long talk with him you just blew it. You can respectfully pay him/her for the two weeks and walk him/her out the door or ask them during that two week period to train another individual. Most companies today do not have an overflow of talent and may be hard pressed to put someone as knowledgeable in the job. I speak from experience as a retired project manager with a large corporation who was called back (working for a vendor) to do the same job. I am now working for a company where I had to use my past experience to build up contacts, etc. I may be an exception to the rule but I have a full set of desktop procedures documented in case the time comes when I will leave. Whether they let me hang around for two weeks or pay me and walk me out the door is totally acceptable. It is only a job and if one makes a decision to leave and gives notice it is a done deal.

by femijumo

once he has been loyal and dedicated to you but due to career development or increase in pay , he should not pose any threat to you, be fair to him because a person that look irresponsible today might be a key to the success of the same company tommorow.

by shadow1

I am currently at that point in time. I have interviewed for a new position but would not even consider doing anything inappropriate in my time left. Word does get around.

by andrew

I worked for several years in a place with full admin privileges from day 1 (which I thought was a little strange). They showed me the door three days before the Christmas break after an 'unsuccessful' re-application process that they said was a 'normal' practice. The network admin told me to go quietly but I fought the decision and won my job back via an independent arbitrator. When I was unknown (ie: Day 1) I had full network privileges - yet only 'touched' the things I was supposed to touch. When I returned I was so restricted on the network as to be virtually redundant. I could only help users improve their skills with apps, couldn't restart print spoolers, move and or recover lost files, create accounts, etc. They even changed the BIOS password on 350 machines to keep me out. Nine months after my return the Network Admin was dragged kicking and screaming by his superiors to the server room and made me an admin; although (unbeknown to the superiors) with heavily restricted privileges - do I keep complaining to the superiors? Now, I would not trust the Network Admin to give me the time. (Turns out it was he who shafted me through the re-application process) His ruthless attitude is the reason for the draconian action companies take against previously trustworthy employees. Yet I am a trusting person so do I be savvy or naive next time?
The answer for any company is to have fully documented systems so that every employee is redundant if a bus should hit them. I spent three years documenting the network procedures and knowledge for the organisation - but he saw that as a threat not a service. In my opinion, that document remains their salvation should they one-day lose their #1 Network Admin. However, it is now a year out of date as I wasn't allowed access to it when I returned.

by markck

hey AWM....get a hobby, breed elephants or something. in short, GET A LIFE!!!! can't people move on to other jobs??!!?? why is coporate america so dead set on making working peoples lives so miserable??
ever think he's moving on cuz he's sick and tired of the daily garbage YOU force feed him? or cuz YOU denied him a raise? or YOU didn't approve a much needed budget?? it's time to look in the mirror AWM and see your own faults. by the way, let the guy go in peace!

by cblackford

Being management, an enterprise admin as well as having full network access, the first thing I did was insist all my access be removed including physical access to secure facilities. This was done to make sure I was protected from the company. Professionally, they had no reason or grounds to expect I would not anything. I'm a professional. I just wanted to make sure I could clearly demonstrate any subsequent events could not be blamed on me. It is real easy to point the finger at some one who is no longer there. Any employee who leaves or whose position is eliminated should insist all privileged access be removed immediately. The departing team member can work with other staff team members to walk them through any changes (always make sure there are at least 2 other people involved to prevent creditable denial and don?t touch the keyboard yourself). It is as much as protecting yourself as protecting the company.