I.T Job - abbreviations

The best engineers / admins I met were not the ones who held every setting and bit of info in their heads on a particular technology but those who went off and found out the answer (from a book or google) when they weren't sure.

The worst engineers I had the pleasure of working with sat their and stated they didnt know what something was and where was their training course?

Sounds like you would be blagging this job if you applied which is fine if you fall into the first option. If would be a disaster if you fell in the second
 
That's not "learning" SCCM, that's learning how to point and click some pre-defined actions that were set up by someone with a clue.

Would you say that someone who knows how to open a document template "knows" how to format documents? no.

Learning how to point and click is 1st line support.

In this instance, it applies.

At no point has the OP said hes looking at a 3rd line support dedicated to vmware citrix sql sccm etc. He asked about simple 1st line support roles which all usually require is a simple bit of knowledge and the ability to pick stuff up quick.

SCCM - Deploy software, remote in - can I fix it? no.. pass to 2nd line. Thats all it will be at 1st line.

If it turns out the employer is looking for more (potentially by the "experienced" word, then this obviously isnt for him)
 
Last edited:
Learning how to point and click is 1st line support.

In this instance, it applies.

At no point has the OP said hes looking at a 3rd line support dedicated to vmware citrix sql sccm etc. He asked about simple 1st line support roles which all usually require is a simple bit of knowledge and the ability to pick stuff up quick.

SCCM - Deploy software, remote in - can I fix it? no.. pass to 2nd line. Thats all it will be at 1st line.

If it turns out the employer is looking for more (potentially by the "experienced" word, then this obviously isnt for him)

Yes but coming on a public forum for an answer when any search engine would have provided the answer....
 
If you don't know what AD or GPO's are then you will be looking at first line support at most..

Not entirely true ... I know plenty of third line Unix/Linux support people who know next to nothing about AD, GPO or SCCM beyond what the first one stands for ... but they don't need to as it's outside their specialist areas. Just because something is obvious if you work in one part of the industry doesn't mean it is in another part.

The best engineers / admins I met were not the ones who held every setting and bit of info in their heads on a particular technology but those who went off and found out the answer (from a book or google) when they weren't sure.

The worst engineers I had the pleasure of working with sat their and stated they didnt know what something was and where was their training course?

Can't agree more ... I have to spend far to much of my time some days dealing with escalations from 3rd line support for things which an ability to be able to use Google and actually think about what you are trying to do rather than expect the solution to be handed to you on a plate would mean that they should be able to handle it themselves.
 
Yes but coming on a public forum for an answer when any search engine would have provided the answer....

Yes I agree and also with your previous of the best engineers are almost the slightly stubborn ones who will persist with a problem (within a reasonable timeframe) using logical steps (google) to find an answer, and have pride in doing so.

In this case, I put it down the the assumption of the OP being young and not yet developed these skills :)
 
Wouldn't hire someone who didn't have the common sense to use a search engine to find something out that they should really know.

SCCM/AD aren't rocket science but if you don't understand them you can really mess things up, heck even experienced staff can still muck it up causing a lot of problems for larger organisations.

It can only take 1 ticky box and the whole organization comes crashing down. Anyone needing to ask what is AD/SCCM/GPOs e.t.c really shouldn't be in the job. Not having a pop at you OP but just saying it how it is.

If something done something wrong it could cost a business a lot of money, down time and frustration.
 
My first IT role involved domain user admin and using SMS (which then became SCCM) with no previous experience.

Did I know how it all worked? No (we didn't 'have' AD/GPOs then..).

But I was able to be told how to use it for the job pretty easily.

I guess it depends on what the chap recruiting is expecting from his 'experienced IT technician'. I wouldn't be expecting a technician to be dealing with the ins and outs of AD and SCCM etc. I'd be expecting someone who can use SCCM to deploy software and other general support tasks, basic user acc management in AD, basic GPO stuff etc.

All depends on what level the person recruiting is setting the bar at.

But tend to agree if he's looking for someone who already has experience of those technologies then it may not be ideal.

Heck you can specialise in SCCM and earn a fortune.

What I sort of did as I ended up leaving that first job after a number of years, after moving into the SMS and app packaging side of things quite heavily, for a nice contract.

I'm not in that area of IT now but I do miss it as found it relatively fun and interesting, app packaging especially used to be good when you had a good problem to get your head round.
 
Last edited:
They are the easy ones, the world of IT is full of them. Its when you come across abbreviations that are the same but can have 2 different meanings. The fun of IT :D
 
The first thing you need to learn about IT is that it is full of people who will patronise your knowledge at whatever level you are at :)

The only other thing I'll add is that my first job in IT had a rather grandiose job spec, but I turned up with little other than the right attitude and got the job.

OP's job is at a school, not at the bleeding edge of the industry ;)
 
The only other thing I'll add is that my first job in IT had a rather grandiose job spec, but I turned up with little other than the right attitude and got the job.

OP didn't google the acronyms he hadn't heard of. Right attitude?

OP's job is at a school, not at the bleeding edge of the industry ;)

Not sure Active Directory and Group Policy qualify as "bleeding edge"...
 
OP's job is at a school, not at the bleeding edge of the industry ;)

I work at a school. Bleeding edge it ain't, but you'll be part of a tiny team of people expected to manage a huge number of users, machines and varying software.

"experienced I.T. guy" is really vague, and schools often don't understand what they're really advertising for. If it's a junior <£20k job, then get yourself some first hand experience by making your own home lab and apply. If they want you to be in charge of the network, don't bother IMO.
 
Can't agree more ... I have to spend far to much of my time some days dealing with escalations from 3rd line support for things which an ability to be able to use Google and actually think about what you are trying to do rather than expect the solution to be handed to you on a plate would mean that they should be able to handle it themselves.

You have a **** 3rd line desk.

If my 3rd line guys passed a quick Google incident to my 4th line guys I'd be annoyed. Not just because they're wasting 4th line's time, but because they even accepted a rubbish incident that 2nd line should be answering.
 
Have to agree with Gilly. If we pass stuff to 4th line we better have exhausted ALL other avenues or be prepared to atone for our sins.

Also, if 2nd line pass over something that is simple Google-fu I take it as an opportunity to teach. If its the 3rd time I am doing it however I take a very different view...
 
You have a **** 3rd line desk.

If my 3rd line guys passed a quick Google incident to my 4th line guys I'd be annoyed. Not just because they're wasting 4th line's time, but because they even accepted a rubbish incident that 2nd line should be answering.

I'm second line support and sometimes I try for days to fix problems. I escalate them to be told to keep trouble shooting just because they don't want to fix the problems or can't be bothered.

When I'm asked why it took so long I say because I was troubleshooting then normally they say 'well why didn't you escalate it' ... boils my blood.
 
Back
Top Bottom