| Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free! |
Taking over a network
|
Original Message
|
Name: RanmaP
Date: May 16, 2005 at 10:04:42 Pacific
Subject: Taking over a networkOS: 2000/2003CPU/Ram: Various |
Comment: Hi guy/gals, I know that this is a support forum but there are alot of Network Admins here. For those who do this as a living I would like some advice. I am starting to do my network stuff and I am told I will start manage the company's network. I would like some pointers... everything is running as far as I can tell. But what are some things you would do if you just took responsiblity of a network? There are about 20 servers... at least 3 of those are Windows 2003 others are all Windows 2000. A check list of things to do now to create logs so I can start working on these one by one to maintain them would me nice. Please help a newbie! HELP DESK
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: StuartS
Date: May 16, 2005 at 12:35:35 Pacific
|
Reply: (edit)If I was taking over a network with 20 server's, (don't you mean 20 clients) the first thing I would do is dig out the manuals and documentation and spend a few hours reading them. Save loads of time in the future. Stuart
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: RanmaP
Date: May 16, 2005 at 15:14:17 Pacific
|
Reply: (edit)No, we have over 150 clients. I don't have anything for these servers. I wasn't here when it was built from the ground up. The network admin here isn't the most organized person so... imagine that. HELP DESK
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: StuartS
Date: May 16, 2005 at 16:45:20 Pacific
|
Reply: (edit)One thing anyone having anything to do with computers needs to be is accurate, concise and lucid in their communications. If you had said that you had 20 servers and 120 clients I would have know exactly what you meant without having to guess - did he mean servers or did he mean clients. A 20 server/120 client network without any documentation! The first thing I would do is draw up a form of indemnity absolving me from any blame when things go wrong as they surly will. Stuart
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: josh (by jpag3074)
Date: May 16, 2005 at 21:37:53 Pacific
|
Reply: (edit)I agree with Rick....New Job....Otherwise start buy books Learning server 2000, and 2003 Learning Networking Learing Windows XP/2000 Learning Domains Learning Computer Repair Also, why in the blue hell do you have 20 servers for a 120 node netowrk...? I would start combining servers by there specific duties for easier maintence...have fun
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: krispy
Date: May 17, 2005 at 06:51:02 Pacific
|
Reply: (edit)Another thing you may wish to do is study and document the topology of the network infrastructue, it may take a little time but will help loads if any of your network devices (e.g switches)fail.
Report Offensive Follow Up For Removal
|

Post Locked
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Networking Forum Home