Jump to content

Recommended Posts

Posted
Unfortunately @ZeroHour they chose this route. I offered to give passwords and write them down as I was working and changing them but told it was unnecessary. This was in writing as well.

 

At least it was in writing, they obviously have a plan or someone on the team is possibly aware of whats needed to be done. Remember they can still ask you to hand them over during your paid gardening leave, you are still technically an employee.

Posted
Not an employee anymore. Termination date was yesterday and being paid the notice time + accrued holiday.

 

Ahh when you said:

stuck up a creek without a paddle as I am refusing to hand over any passwords

I read that to mean they had wanted the passwords but you refused rather than they didnt want them as they thought they wouldnt need them.

Posted

I had to do exactly this, step up from Tech to NM role due to illness.

I was able to as I knew the passwords, the server set up and if needed speak to the relevant companies for assistance.

 

It isnt easy, but providing you have the support from the staff and most importantly the SLT it is possible. A lot of slack was given to us which helped.

  • Thanks 1
Posted
I'm curious what the line is between ICT Technician and Network Manager. I'm currently paid and employed as 'ICT Tech', but I'm the only one here, hold all the passwords, set everything up. When can you call yourself 'Network Manager'?
Posted
I'm curious what the line is between ICT Technician and Network Manager. I'm currently paid and employed as 'ICT Tech', but I'm the only one here, hold all the passwords, set everything up. When can you call yourself 'Network Manager'?

 

When you have control of the budget and staff to manage usually.

Posted

I have one but not the other.

 

I am asking as there is a Network Manager job going at a nearby school, and I'm wondering if I should apply.

Posted
I'm curious what the line is between ICT Technician and Network Manager. I'm currently paid and employed as 'ICT Tech', but I'm the only one here, hold all the passwords, set everything up. When can you call yourself 'Network Manager'?

 

See other discussions about titles and pay: http://www.edugeek.net/forums/behind-red-door/159293-technician-network-manager-advice.html

 

Depends on your job description, LA - if you have one, etc etc. I call myself NM to outside contractors and suppliers - unless I don't want to talk to them when I am "just" a tech :)

 

*edit YES, apply!

Posted
I call myself NM to outside contractors and suppliers - unless I don't want to talk to them when I am "just" a tech :)

 

*edit YES, apply!

 

 

That made me laugh! There are a lot of people I don't want to talk too.

Posted
When you have control of the budget and staff to manage usually.

 

I'm a senior tech who manages the budget sheet, can authorise purchases and line manages two members of staff.

 

Anything else this thread can throw at me to show i should be paid more? :p

Posted
I'm curious what the line is between ICT Technician and Network Manager. I'm currently paid and employed as 'ICT Tech', but I'm the only one here, hold all the passwords, set everything up. When can you call yourself 'Network Manager'?

When the JD says "network manager". The role does vary from school to school. Here the NM is mainly a technical post, she manages the network and has LM responsibility for our Senior Systems Engineer but has no budget responsibility.

Posted
Depends on your job description, LA - if you have one, etc etc. I call myself NM to outside contractors and suppliers - unless I don't want to talk to them when I am "just" a tech :)

Heh for me its if I want to take responsibility for something ("I'm the Network Manager so I will take responsibility for that" vs "I'm just a tech, that should go to management" :p )

Posted

Here, there is a considerable lack of documentation - something that I really want to change.

That's not to say that there isn't any documentation at all, because there is a list of passwords in the safe and lots of pieces of info dotted about on my Network-Team Shared area/drive, but it is pretty hard to find, and to find the latest version.

I would say that my teckies would do quite well on their own, but only for day-to-day stuff.

I've had a search through the forums, with limited success - does anyone know if there is a thread on here or a good website as a guide on how best to document a network/software/procedures from scratch? The more I think about it - the more I think that I wont have time as it is such a huge can of worms.

Posted

When I started here the previous Tech had died leaving a wife and 3 kids - one still at this school. All the documentation had been in his head - as well as the passwords as far as I can tell. He seems to have been a good bloke with lots of ideas - unfortunately a lot of them were still in the experimental stage!!

 

As a result the first few weeks were rather difficult - lots of problems that had been outstanding for a whole term - the LEA was 'helping out' in the meantime - and the staff here are not very IT literate beyond WWW and Powerpoint.

 

Hence, I have started a green book that is kept safe and has all the passwords, access methods and critial IP address stuff in it.

 

I work on the assumption that anyone taking over would ahve the knowledge to work out server setup, DHCP parameters, DNS etc etc based on that - if not then they shouldn't be messing with it!!

 

If I get run over by a runaway elephant or bus then the person who takes over is NOT going to be left with that sort of mess!!

Posted
.......would your technicians be able to do all that you do?

 

What's your thoughts on this? For all you network managers out there can your technicians do all that you do in the event of you not being there?

 

Also, if your a one man band what would you do in this situation.

 

By the way, I have a documentation manual that covers all relevant items.

 

Day to day stuff they should be okay, there will be a ton of extras and obviously the plans/budgets wouldn't get done.

Posted

Quite interesting though as until you get to tech level 3 no server side is involved which is what I stated here that it is beyond their job description as an IT Technician.

Documentation is long winded but definitely worth it. It's taken me several years to put together, and it's one of those things when I get 5 minutes I update it a little bit more.

Even as NM, it comes in useful at times when there's something you don't do very often.

Still writing it to this day.

Started from scratch but there are some sample handover document templates online, although I haven't found them in depth.

Just as and when I do something on the network I check to make sure that item appears in the docs somewhere.

Posted

Put all the docs into docuwiki, on wikiserver for techs eyes only. carry around on usbstick, print off any major changes at the end of the month, file em offsite… that sorta thing.

NMs have been pretty surprised at the openness of this… but I've been doing this now for twenty years… amazing how nothing regarding documentation changes!

Erm… learnt the hard way… no point leaving your disaster recovery documents in the school that just caught fire… or college that suffered a flood… on the second floor… hmmm…

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...