Discussion Locked

The New & Highly Expected IT Person

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

To any/all IT folk out there, I need help. I was hired 3 weeks ago as the IT specialist for a company in Illinois, not realizing that there hadn't been an on-staff IT person in over a year, maybe two.

My problem is the overwhelming lack of information regarding IT policies, network information, software & licensing information, etc. Basically, there is next to nothing to work with. The "Master IT" manual is dated 2003, to give you an idea. So my query is how to go about getting this organization squared away and secure my job in the process.

19 replies

by zlitocook

Welcome to the new guy club. Allot of companies thought that contracting or out sourcing was a cheaper way to go. In the last year or so there has been a big upswing in hireling IT for large and small companies in our area.
As the only IT person you need to meet with managers, CIO's and others to let them know that you will do what ever is needed to make their company run better and keep its information secure.
Now you need to let them know to do this you will need their help because it might mean changes in how they do things.
Like how they use the internet, how they use their computers and what users can do on their computers.
I am in the same position where I am at, and my boss is in another state. So I follow some of their polices and make some of my own.
PM me and I will give you more of what I do to keep the users happy.
I use MS allot for free how to's on Outlook, Excel and other office products.
You did not say if you need to answer to a high boss or if you are the only IT person. If you are the only IT person, you need to find out what you can and can not do! Ask the people in charge what can I do and not do?
This may let you know if you need to look for another job fast.

by gralfus

I'd bet they probably don't have up-to-date patches on their servers or PCs, and may have been compromised severely by now. There are probably spyware and other nasties if they are all admins on their computers.

I'd recommend doing a bit of recon to determine what needs to happen, present it to the management so they understand the dangers, and recommend a clear course of action. They will still probably resist because they are used to unbridled freedom with their equipment.

by ayambeng

Hello,
What I suggest is you should draw up an action plan which consists of what you intend to do and the amount of time you intend to spend doing it. This should fall within a specific time frame say three months. One thing for sure is, you are going to work yourself out. You should be as realistic as possible when drawing up your action plan since you will have to present it to hierarchy for prior approval. So do not insert what you cannot do. The action plan should be result oriented ie you should present the expected results at the end of the period. Actually, what you are trying to bring out here is to let the Administration know you are thinking of and intend to take good care of their business. This is what has to come out at the end of the day.

by raynetoday

This is the FIRST thing John needs to do, in spite of the excellent responses down thread. John needs to let the Administration know that the first order of business is to cover their behinds for them, that they have been exposed to a risk, and that he is going to address it immediately. He needs to explain that the risk is a lack of current Disaster Recovery planning, which includes an updated snapshot of the existing system, documentation of information flow, and how to recover the infrastructure and data in the event of disaster. (Any hesitation by management -- and some managers are stupid or weenie enough to hesitate -- should be answered by the word, "Katrina".) If the business must be SOX or HIPAA compliant, he can also explain that the secondary risk is lack of currency in compliance, and that he is going to reduce their risks as soon as applicable Disaster Recovery documentation has been completed.

Doing these two things, letting management know how critical the documentation is and why, will buy John the time he needs to do his job. Remember that some businesses, especially those with only a single IT person, don't necessarily understand the value of documentation and may not perceive value from any IT work that is not directly and immediately visible as cost-saving or productivity-enhancing to management or the users. (Been there, done that, now consult on it.) If management understands they have been exposed to a quantifiable risk, they will let John have space and time he needs to get the documentation done.

That said, John also needs to ask why the last IT person left and why so long to replace them; there's an issue right here, and it also needs consideration. This gap might explain a lot about the business's condition and management attitude towards IT, helping John formulate a position in dealing with management about IT. If there were cost/expense issues involved, John needs to frame his efforts in those terms. If a lack of understanding about IT's importance was involved, he's going to need to have education/training sessions or prepare "explainers" (short briefs that provide an overview of particular IT issues and impact on business).

And of course, as all other IT folks in SMB's know too well, do all this while users are breaking every known security maxim at the same time. Heh.

Good luck, John!

by cuteelf

Is a great tool to use anytime you're having PC troubles: either the box itself or the cerebral PC department!

START WITH THE PHYSICAL AND WORK YOUR WAY UP.

So.

Do a physical audit of the network and the lan and the EVERYTHING.
Including rack #, slot#, serial#, version firmware#, .......got idea?

This will show you what you're dealing w/ as a whole.

Whos the ISP?
Where are the fire exits?
What's your TOS w/ the ISP?......

Start physical in your bldg.
Work up from network into the PC's themselves.
Build a DB or spreadsheet on your inventory.

Personally I'd use a network sweep and get version/patch/serial #s/liscneces.

Get this written out and drawn out for your department.

Then let it sit for a week or 3 and watch the problems in your world go by. Get a baseline to compare of net traffic, net usage, idiot calls....

Set five goals to achive by end of year.

Find any existing paperwork from legal dpt about network usage, security settings...anything?

Also listen to the users. Setup a webpage for user inputs/suggestions SPECIFICALLY for computer related questions & problems.

Pile those up and find a common denominator. Who bitches the most? Why are they whining? What box do they use (you know by now) What kind of job do they have???

Good luck, and remember: if you do piss someone off, you're doing the right thing by documenting thier crap. The lawyers will thank you some day.

CuteElf

by jbrare

As you inherited an unknown, you really can't begin anywhere until you define where you are at currently, and where you wish to be in a given period of time. The first thing is to do a complete hardware and software inventory, complete with hardware specifics (RAM, CPU, drives,all network access points, etc.) and software versions, license and per seat usage. This type of inventory will give you an idea of where you are. After that you will have to design the permission(s), priveleges, and security available. Good luck

by amarie.singh

I know exactly how you feel. The best thing to do is start with your inventory(licensing, machines, servers, firewall, switches). Software to use could TrackIt or Remedy. Have discussions(needs\support) with the managers of various departments. Helpdesk will definitely be a huge issue. Outsourcing some consultants would assist. I know alot of companies in the Caribbean invest alot in outsourcing. Search up SOX - based on documentation - standardized docuemtation. http://en.wikipedia.org/wiki/Information_technology_controls

by nocubes4me

John,
I walked into a similar situation, and then watched as my supervisor attempted to "reign in" everything at once without much buy-in from above (or even laterally). Not a pretty sight.

The points already made are excellent - documentation, planning, change management, change documentation (in particular).

The main things we both learned from the adventure were:

1.) One thing at a time - which means assess, get a feel from the community (top to bottom), prioritize, and establish realistic timelines. Then communicate. Constantly.
2.) No buy-in, no backing. Earn management buy-in.
3.) No credibility, no possibility - note that I said "Earn management buy-in." Doesn't matter if it's the best plan and all of the right folks are behind you - if they don't believe in you, they don't believe in "it", either.
3.) No authority, no point. You can't drag the company, and you won't get much accomplished if you don't have some degree of authority to carry out "the plan".

by purecoffee

Time to "Come to Jesus". I have recently been down this road. I would just start with an inventory of computers, servers, etc. Did any of them come with licenses etc. Write it all down and just start organizing. Break it down into categories and prioritize. Start with Server, server software and licensing and then move to individual pc's. Ask the business units what their expecations are and what their needs are. What do they expect that employees would have on their pc's and what is acceptable. With that,create an Acceptable Use policy. Buy a copy of Visio and start on the network documentation. Talk to the old vendors if you can and see what they did or did not do.
Your task is going to be a long haul project and won't be done over night. Creat an IT Plan and present it to the company on the problem (no docs etc.) and then your solution with an expected timeline given the resources you have. THis will give you instant credibility if done right.

hope this helps.
P.S. YOU CAN DO IT!!
Remember, Failure is an event, not a person!

by stephenmoriarty

Management might sense the panic, I had the sam issue 5 years ago. first thing i did was find what servers were critical to the day to day running of business. those were brought up to current levels, then I started checking disaster plans or lack of them, once i had main servers up to snuff I started looking at all the others in use and what they were doing, chances are consolidation might be needed especially if all the it have been listening to in tha past were sales weasels. as for bread and butter machines..I used a software product called Look@lan www.lookatlan.com to give me a quick list of what people were running and login names easy to dump in spreadsheet. Then on individual machines at random I used a product Aida32 google search it it will tell you all thats inside any machine that its run on and give you a list to look at for hardware and software. both still good free tools. Once I had an idea what the bewnchmark machine was and how it was being used I then decided what software should be on there and what should not and started rolling on imaging old machines to fit my packadge. Once they were replaced, then all I had to deal with were the winers about why they could not have there home games and other crap loaded..I'll admit I was not popular for 6 months.

by stephenmoriarty

Document...Document...Document..rember you may not be there fore ever and the next guy may not be so smart as to ask for help. I would document from the street to the Pc screen...skip nothing...The longer your on the job the more detailed it should become. When my company was bought out and assorbed into a bigger one my documentation was extreamly useful to the new parent.

by kevin fitzgerald

If it is any size, I suspect either they have been using third party support or someone within the company is fairly (IT) knowledgeable or it would have collapsed long ago. Glean what information you can from who ever has been keeping the network running.

Don't do admin just for the sake of it the last thing they will be looking for is a jobs worth.

Carry out a quick inventory on the critical things Anti Virus, Firewall, Back Up & Servers etc. If there is a weakness in any of these prioritise what has do be done first. Talk to your line manager explain what needs doing and why. Ask do you have a budget?

Avoid being distracted too much by help desk calls of a trivial nature I suspect after 1 to 2 years there will be a lot of justifiable demand from users for help. Until you get to know your people, this could be difficult.

Document everything you do.

Good luck been there didn't much like the T-shirt.

by dryflies

3 years ago - roughly - I was hired in as an IT spec for my unit that had not had a professional IT person in two years and had been getting by with a part time student. A poli-sci major.
The network was completely undocumented, the backup server had several GB of music on it - but few backups - and there was no policy in place for any of the usual things, acceptable use, backups, media disposal, nothing.

My first step was to creat a map of the network and the assets. I started by wandering around taking down locations, mac addresses, maintenance numbers. Next I located all of the hubs, switches, routers and other network appliances for the network.

I recorded all of this information in a visio diagram. both a physical diagram and a logical diagram. if you try to put connections and locations on the same diagram it gets too busy.

I Identified critical nodes of the network and longest paths WRT my workstation. reconfigured desktop firewalls to allow access by my desktop machine. created a list of nodes that when pinged, accessed, every switch, router, hub, printer and server. wrote a script, to test each of the critical paths, nodes, and resources on the network. set a scheduled task to run it 15 minutes before I come in to work each day. I gave the script to TR, it is posted on the site https://www.techrepublic.com.com/5100-1035_11-6021514.html

If you can, reset the passwords to all of your network appliances so you can access them. Access to your switches will give you the valuable cross reference of switch port to plug number by taking the mac address of each of your nodes and linking the physical location to the port number of the switch. I just got this ability and am having a fine time redocumenting my network.

by usbport1

I've been the sole IT person at the company I currently work for 6 years now. I originally worked for an IT company that had been hired to meet this company's IT needs which 2 years previous had replaced their IT person who had let the network decay. Being one of several IT techs, I had been here several times, but right after Y2K the IT company went out of business and this company offered me the job of MIS Manager (I manage myself). The biggest thing that I could tell you is to keep everyone happy first by keeping all the servers and PCs up and running and responding to every help call ASAP. Once everyone gets used to, and you to them, then start implementing major upgrades and IT policies. I got my biggest raise (10K) doing this after my 2nd year and was told that was the sole reason - system uptime and user happiness with the stability of their PCs. I too was overwhelmed at first but as time goes by it wears off. Secure your job first then organize and upgrade second.

by john

To all who have been so kind with your responses:

I am not sure how much longer I will be with this organization (or lack thereof). It seems that this place is set in their ways, i.e. - using "work-study" to get things done (contracting out to their students to do IT work) and then not keeping lists of who-does-what nor any documentation regarding what has been done.

It is quite frustrating working with these unknown variables and I can see that my immediate supervisor is getting upset with my lack of understanding of their ways (although no steps have been taken to ensure I get that understanding).

I will try to stick it out here with all of the daily projects that are continually thrown at me along with the long-term project of bringing this place up-to-speed.

Any advice on telling your boss that you don't think it is working out?

Thanks!!

by breadtrk

Get out now. You have already admitted defeat and are questioning if this is a gig made for you. Be realistic and don't dwadle here any longer than is absolutly necessary. Get out and deliver Pizza's until you get a real job.

by ericsaddress

The best advice I can give you is to not to give up so soon. Follow the 100 day rule..sit back and observe the organization for the next 100 days taking notes and writing down your recommendations. I am not sure what type of organization you are in (sounds like a college or university), but I know from working IT in academia that people are reluctant to change. I found that it is better to gain trust first and then come with your recommendations after everyone has gotten comfortable with you. That is much better received than walking in trying to change things without examining how things are.

Good Luck!!!

by shep5_7

There hasn't been an IT guy for about a year. I am getting information about the network from the person who i am suppose to supervise, bc the last IT guy showed him some things. My boss doesnt really have a clue he just tells me to get it from my employee and does not tell me what I need to be obtaining. The last guy left documentation about the physical part so My question is should I go by his info or just skip that step.

This discussion is closed to new replies.