Company is hiring a new sysadmin. Because we growing more rapidly, I'm transferring my sysadmin duties over so I can concentrate on managing and leading the development team. How can I make this transition go smoothly? What are some good initial steps to take? The new sysadmin will need to have access to all the server and DB management resources and I'm a bit concerned about how to give him all these responsibilities securely. And what are some usual protocols and policies to set up once the new sysadmin is onboard?
Asked
Active
Viewed 167 times
2 Answers
7
If you are asking these kinds of questions, then you need to buy one particular book NOW and read it through.
Do not wait. Do not pass Go. Do not collect $200.
Buy The Practice of Network and System Administration and read it.
Magellan
- 4,471
4
We know it happens to a degree no matter what you do, but the problem here is that the information is inside your head, not inside a documentation system of some kind. The links below are examples, not product recommendations
There are countless wiki and blog programs you could run internally to document this knowledge if you don't fancy/need one of the sophisticated helpdesk systems that also does documentation, in which case you should still be looking at the simpler helpdesk systems, because tracking this is important too.
As for passwords, these need to be more closely held of course. There are lots of secure password management programs around for that info that let you track who accessed this or changed that.
The main problem here is time management. It's difficult in an expanding company where everyone is already busy but you need to start things off right with your new sysadmin employee by introducing the mantra that documenting what you've done on a job is part of doing that job and therefore part of the time allocated to doing that job (and by which I mean increase the time allocated, not expect people to work faster!), rather than something that gets done on a 'when I have time' basis.
