New IT Employee
-
When I walk into a new client's office, usually there is NO documentation and no one knows anything. I guess it's SOP for small IT shops to leave no documentation for the client.
-
I have always walked into a mess as well. It seems like it takes about 2-4 months to get this kind of stuff down.
-
Sticking with my bourbon and coffee mug suggestion :-P. Yeah I inherit garbage that makes little to no sense, you're a great dude Joel.
-
that is awesome. I have walked into a few situations but there was always another IT employee willing to help. This is my first gig in a small IT department.
-
@RAM. said:
Sticking with my bourbon and coffee mug suggestion :-P. Yeah I inherit garbage that makes little to no sense, you're a great dude Joel.
The sooner he learns our network, the sooner he can help me out
undercover, eh?
-
I would be careful with initial admin passwords till you have a handle on how he/she tackles problems. It can be a pain correcting issues when 2-3 things are changed at the same time, and maybe not documented as well as you do it. If you have to go back, knowing where to go sure makes the battle a bit less hectic. Just my experience with teaching new employee's who may bump around in your system even with the well documented information you provide. Do you know his level of experience? For sure? I have had "Paper Techs" with certs, good at study and tests, but not at being inside or on an actual system. So I tend to err on caution, but if he/she is a performer then I have no issue allowing full access.
-
@IRJ said:
@RAM. said:
Sticking with my bourbon and coffee mug suggestion :-P. Yeah I inherit garbage that makes little to no sense, you're a great dude Joel.
The sooner he learns our network, the sooner he can help me out
undercover, eh?
Yes sir, after the snafoo went down, I don't want to be a recognizable house hold name, so I comment maybe one or twice a week on the other account to prove I'm not dead, but I'm hanging on my alt to remain somewhat anonymous. Oh and do you guys pay to relocate ;-).
-
@RAM. said:
@IRJ said:
@RAM. said:
Sticking with my bourbon and coffee mug suggestion :-P. Yeah I inherit garbage that makes little to no sense, you're a great dude Joel.
The sooner he learns our network, the sooner he can help me out
undercover, eh?
Yes sir, after the snafoo went down, I don't want to be a recognizable house hold name, so I comment maybe one or twice a week on the other account to prove I'm not dead, but I'm hanging on my alt to remain somewhat anonymous. Oh and do you guys pay to relocate ;-).
I dont know. I think they might if they found the right fit.
-
@IRJ said:
@RAM. said:
@IRJ said:
@RAM. said:
Sticking with my bourbon and coffee mug suggestion :-P. Yeah I inherit garbage that makes little to no sense, you're a great dude Joel.
The sooner he learns our network, the sooner he can help me out
undercover, eh?
Yes sir, after the snafoo went down, I don't want to be a recognizable house hold name, so I comment maybe one or twice a week on the other account to prove I'm not dead, but I'm hanging on my alt to remain somewhat anonymous. Oh and do you guys pay to relocate ;-).
I dont know. I think they might if they found the right fit.
well if you guys need anything
-
@ChrisJ said:
I would be careful with initial admin passwords till you have a handle on how he/she tackles problems. It can be a pain correcting issues when 2-3 things are changed at the same time, and maybe not documented as well as you do it. If you have to go back, knowing where to go sure makes the battle a bit less hectic. Just my experience with teaching new employee's who may bump around in your system even with the well documented information you provide. Do you know his level of experience? For sure? I have had "Paper Techs" with certs, good at study and tests, but not at being inside or on an actual system. So I tend to err on caution, but if he/she is a performer then I have no issue allowing full access.
I thought about the password thing and here is my take on it. If it doesnt work out, I will have to change all the passwords anyway. Why put him through the torture of recording each password on his own?
Either way, if he leaves I would have to reset all the passwords.
-
-
@RAM. said:
@IRJ said:
@RAM. said:
@IRJ said:
@RAM. said:
Sticking with my bourbon and coffee mug suggestion :-P. Yeah I inherit garbage that makes little to no sense, you're a great dude Joel.
The sooner he learns our network, the sooner he can help me out
undercover, eh?
Yes sir, after the snafoo went down, I don't want to be a recognizable house hold name, so I comment maybe one or twice a week on the other account to prove I'm not dead, but I'm hanging on my alt to remain somewhat anonymous. Oh and do you guys pay to relocate ;-).
I dont know. I think they might if they found the right fit.
well if you guys need anything
We work very closely with a MSP. They are short staffed right now. We have had many tickets opened with them for weeks. Maybe they could use a remote person? One of their guys had a skydiving accident and he works from home a few hours a week as he is able to.
-
We have on Sharepoint a welcome guide. Very handy. Steps you through a lot of new hire stuff.
-
If your business stops supporting a client, does the client normally have any documentation of their network, hardware inventory, etc?
-
@technobabble said:
If your business stops supporting a client, does the client normally have any documentation of their network, hardware inventory, etc?
I am not a MSP. I am an IT employee for a company
-
@IRJ said:
@technobabble said:
If your business stops supporting a client, does the client normally have any documentation of their network, hardware inventory, etc?
I am not a MSP. I am an IT employee for a company
I am more curious in general do MSP or IT shops usually provide documentation for the client to keep. I have documentation for my clients, but I have never actually given my clients any documentation since it seems that none of the other "tech companies" have ever left anything behind. I would presume if a MSP was handling the office, they would get monthly documentation.
-
Documentation is part of the agreement. It cost money to produce. Few firms want to pay for that. So generally, no.
-
@scottalanmiller Thank you...that makes sense.
-
@technobabble said:
@IRJ said:
@technobabble said:
If your business stops supporting a client, does the client normally have any documentation of their network, hardware inventory, etc?
I am not a MSP. I am an IT employee for a company
I am more curious in general do MSP or IT shops usually provide documentation for the client to keep. I have documentation for my clients, but I have never actually given my clients any documentation since it seems that none of the other "tech companies" have ever left anything behind. I would presume if a MSP was handling the office, they would get monthly documentation.
It really depends on the situation. If it's a polite, clean break, quite possibly. If it's on bad terms, possibly not. We make sure that they have proper access to administer their systems at any given time, so should something happen, they still have passwords, etc. Some clients like to keep their own documentation and get cross-trained as changes happen. Others don't care. If a customer requested documentation prior to ending service, we'd provide it along their guidelines.
-
Exactly. Like all things, it depends. Much like "do we manage their servers". Maybe, maybe not. Depends what they hire us to do
