New IT Employee
-
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.
-
@scottalanmiller said:
@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.
I'm familiar with a Fortune 100 that's working on implementing VDI. Bigger companies are doing it, but it's more of a phase-in process. Because of this, it isn't as widely known. Most implementations start with a PoC at a smaller division, then grow from there.
