New IT Employee
-
@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
-
You can't make it too easy on him. The challenges to getting up and running are part of the hazing process for the noobs.
-
What's his job? I'm currently preparing for a new IT employee and that list you posted is basically his or her task list for their first week.
-
For an entry-level employee, I can see doing some prepwork. For an experienced employee, a typical rite of passage often is having them set up their own workstation, join it to the domain, etc. Watching how they go about this and paying attentention to the questions they ask will give great insight on how to go about training them in an effective fashion.
-
@alexntg said:
For an entry-level employee, I can see doing some prepwork. For an experienced employee, a typical rite of passage often is having them set up their own workstation, join it to the domain, etc. Watching how they go about this and paying attentention to the questions they ask will give great insight on how to go about training them in an effective fashion.
Few large companies would give desktop admin rights to average IT folk. And far fewer would let them join to the domain.
-
@scottalanmiller said:
@alexntg said:
For an entry-level employee, I can see doing some prepwork. For an experienced employee, a typical rite of passage often is having them set up their own workstation, join it to the domain, etc. Watching how they go about this and paying attentention to the questions they ask will give great insight on how to go about training them in an effective fashion.
Few large companies would give desktop admin rights to average IT folk. And far fewer would let them join to the domain.
Most larger companies would use something like SCCM or VDI, so joining the computer to the domain would have already been done.
-
@alexntg said:
@scottalanmiller said:
@alexntg said:
For an entry-level employee, I can see doing some prepwork. For an experienced employee, a typical rite of passage often is having them set up their own workstation, join it to the domain, etc. Watching how they go about this and paying attentention to the questions they ask will give great insight on how to go about training them in an effective fashion.
Few large companies would give desktop admin rights to average IT folk. And far fewer would let them join to the domain.
Most larger companies would use something like SCCM or VDI, so joining the computer to the domain would have already been done.
I don't think that VDI is as common as you would imagine. I've yet to hear of Fortune 500s even discussing it yet. I only work in so many, but from what I've been seeing it is a long way off from common adoption for normal users in the large space. It seems to be mostly small companies doing it. I'm sure some large companies are going that way, but I've not seen it not really heard about it. Now small companies, I hear them doing it every day.
-
SCCM or other autodeployment systems, though, yes, that should be everywhere large. Pushing out images instantly is a really big deal. Big companies know better than to spend time troubleshooting desktops.
-
How many big companies have you worked for, Scott? I've worked for a handful and found that big companies are often effectively just a collection of small companies, and don't have any have real unified IT support and management function. I consulted for Rolls Royce for a while, and they were very amateurish (although this was a long time ago).
I also worked for Getz Bros who are the largest non-commodity marketing and distribution services company in the US. I got a job as IT Manager for their Hong Kong office. I had no previous experience of IT management (I was previously an analyst programmer), there was no external or internal support in place (I just had a mate who knew a bit that I could ask questions down the pub) and most of the desktops were running Chinese Windows and I only could only support them via an interpreter telling me what all the messages meant (I got real good at recognising Microsoft icons).
From day one I was Domain Admin for an NT network, despite never actually having worked anywhere running an NT network. Miraculously, I somehow survived without killing the network.
-
@Carnival-Boy I started my career working in the Fortune 100 in the 1980s. I've worked at least nine years of my career for two different top tens (IBM and CitiGroup) plus worked some amount for HP, Compaq, Dell, Lockheed, Eastman Kodak (back when it was top 20), UPMC, University of Rochester (replaced Kodak as the largest employer in Rochester), Wegmans (mid sized company but 35K employees over about six states), Pioneer, and more if you count non-IT jobs.
