Just started at a new network question? 2

[wolwol]

This network has been neglected for about 5 months now; it is part of 5 other divisions.

1. All computers are white boxes.
2. Most users don’t know very much about computers.
3. The server backups are not working.
4. I don’t know where any software or license is located.
5. Two servers are very old compaq’s
6. One server is a huge white box.
7. Two servers are newer HP systems.
8. Now documentation that I can find.

How would you pros plan to get this network in order?

Thanks

 

[dberg35]

Start by getting all backup working, then do a complete assessment of each box (hardware, software)and see what is working fine and what has issues...check event logs. Most of all make a plan and budget to work with.

 

[TheLad]

I would absolutely agree with the above. Data loss is a killer for companies...

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[58sniper]

1. Not ideal, but....
2. Welcome to IT
3. Your #1 priority
4. You can't fix it without the software. Your #2 priority.
5. But, are they working?
6. But, is it working?
7. You see where I'm going with this?
8. Create your own as you learn your way around.

It always scares the crap out of me when there is no backup. Focus on that, along with learning the network. Document as you go, and you'll end up with a list of installed software that you can then try to find.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[ison67]

I agree with others, get your backups working.

First, how big of a network are you working on? What kind, what's the setup? You've got to know what you're working with before you can know where to start. What's in the documentation? Welcome to IT.

Best of luck to you,
DJ

 

[allywilson]

NMAP and powershell combinations, get the network topology and server info - but only after you figure out what needs backed up, onto what device and using which server and software!

 

[cckens]

Dberg hit it right on. Get backups running, if for no other reason than having that safety net...

I was in your shoes 3 months ago, but at least the backups were working when I got there. Now look at me... (still working on it). Don't worry about the users. As long as they can do the jobs they were hired to, they can wait until you've got a better picture of what you've got.

First thing I would recommend is getting an inventory of the network and status. For the price (free), try Spiceworks (

http://www.spiceworks.com)

and let it run it's scans if you are able to. It gives a pretty good impromptu assessment. It's free for the basics and I've found that it at least lets you see what's out there and the status.

Software licensing is another issue. My company had all the software in the server closet. Dig and find what you can. Then talk to accounting and see who the bills were paid to for IT services. That will give you a starting point as to who got what from where (or at least where the money was going). After that, just start making calls to those companies.

Documentation... a real sore spot for me. I can write documentation, but why should I when I don't have to. If you've got Domain Admin rights, scour the network for documents. God knows I found about 30% of what I have now on the network that someone else had written. I modified and updated for the times and VOILA! Some place to start...

It's funny, when you do a job for 11 years you realize everything that you learned and did comes into play. I'd never been solely responsible for a network until now, but when I walked in the door the first day I immediately knew what needed to be done. Not that I had a clue how to get it done, but that is where TekTips came in. And you were smart to come here.

Just my 2 cents...



cckens

"Not always my best shot, but I hit the target now and then"
-me