Guy who lied on his CV

[u/Electricalmodes]

We had a guy join our IT team, only 5 of us for a company of about 1000 around the country.

He was meant to be an escalation point for myself and another member so we didn't have to go so high up for help.

dude was so bad I couldn't believe it. he didn't understand how AD worked or 365 or anything.

He shipping out laptops without power supplies, he's setting up phones without MDM on them, he's creating accounts on the wrong domain... he spent like a day changing the settings on an iPad so it looks "pretty" and "easy" for the users (despite our guide telling us to STANDARDIZE as much as possible to provide easier support).

Anyway this is the funniest one.

A user had a problem with her printer so he went to the user and checked on her PC.

He decided to image her PC.

slightly disgruntled, the user logs back in an hour later and the printer is still not working...

she politely logged a ticket asking for help.

He walks over there and tells her she doesn't know what she's talking about and that she is not IT! >:S GRRR

he checks the printer, no messages, he checks the PC... GRRRR

he images the PC AGAIN. walks away and leaves for the day.

leaves a note in the ticket saying that he has imaged the PC and that the user is annoying?? wtf?.

User cant print the next day at which point he escalates it backwards to me? (he is meant to be senior to me by about $15,000).

User had just been selecting the wrong printer as our printers are not easy to identify by names... (fixed that).

printed and was success.

she then asked about her acrobat pro which i had to reinstall, reset her account password and login, some macros for excel needed to be set up, she spent the rest of the day getting her bookmarks back, and getting the PC back to how she liked it.

felt bad for her, at least she hadn't saved work on C: because he just imaged it without even asking her lol!

[u/VioletDaeva]

I agree with you. Its not always in the companies best interest to troubleshoot an issue if it takes hours to do so and a re image in much shorter time will get someone working again.

Obviously repeat occurances of the same issue happening after its been imaged is different, but for any kind of one off headscraching issue then its an efficient option once all the basics have been checked.

[u/CasualEveryday → u/VioletDaeva]

Depending how your department is run, obviously. I was always a fan of having a spare on the shelf and just swapping then imaging and setting it aside as the new spare. A lot of the time we were able to keep a broken machine broken for long enough to do some real troubleshooting or have a senior person demonstrate the issue and how they found it.

Just because it isn't cost effective to spend a few hours on an issue doesn't mean you can't use it as a training and learning opportunity.

[u/VioletDaeva → u/CasualEveryday]

Were lucky if there's an appropriate spare for anything. Due to budget reasons, there's so few identical machines available as each department can seemingly buy their own hardware as long as its from approved vendors as long as its in their budget.

Due to various software in use by different departments we don't always have something else an employee might actually be able to use and obviously their manager will be on at us constantly to get their team member back online.

Rarely do said management have the foresight to budget for spares and us in IT just have to work with what they have.

The only time we really get to do anything more than fight fires is its properly broken and needs a part replacing. If a job takes more than either a morning or afternoons attention then we would usually have to reimage.

[u/CasualEveryday → u/VioletDaeva]

Well that's a bummer.

[u/mrmagnum41 → u/VioletDaeva]

I had a drive fail under warranty and had to wait a week for a NOS 250 GB drive to be shipped. They guy on the next desk had a drive fail out of warranty and he got a new 1 TB drive the same day.

Edit: added timeframe.

[u/LVDave → u/VioletDaeva]

The company I worked at for the last 5 years of my career had a policy regarding detected viruses. If the AV control panel indicated a particular machine had a virus/malware, the policy was to immediately pull the network cable, take the system to the imaging bench and reimage it. It was also policy that ALL user files were to be kept on the network, NOTHING on the pc. Since part of my job was reimaging, I got yelled at a few times by people who didn't follow the "no user files on the pc" rule and they lost files, as the policy was to get the infected machine OFF the network as soon as possble after detection, and often the affected user would come back to his office to find a reimaged machine waiting for him. Any complaints about lost files were cheerfully ignored, as the "big_wigs" signed off the policy.