Hey everyone, I recently just started a job managing a small network at my university. I am familiar with peer to peer networks and had an IT guy set to take me under his wings and train me for a while. He however recently quit and I am stuck with a network that is in poor shape. Right now we have two servers, 8 workstations, and 2 specialized machines for gathering scientific data, and a laserjet 4600. I have a few questions if anyone can help me out. I have been reading my a$# off by the way :) and trying really hard to learn everything. Basically the servers constantly had svchost errors and nothing shows up in the event viewer. The server has to be restarted about 4 times a week currently because the network drive constantly fails to connect on the workstations. I want to do a fresh install of 2003 on the server (change it to a 1 server setup) and also reinstall xp pro on all of the workstations. The only thing the server needs to do is have a shared network drive (each user needs a quota and his own folder), maybe act as a print server for the laserjet, and possibly in the near future I would like to set up ftp access. Also we have a licensed program sigmaplot that I believe needs to be run off of this server as well. Oh ya remote login to the machines is a must too (our lab currently has 15 IP addresses we can use for the lab). Any recommendations on whethere a romaing profile is a good idea? I have never done an install of 2003 however Im pretty sure I can get it installed easily. I really was wondering if anyone had any tips on what services should be installed on this small network. Active directory of course is a must. Im just not sure what is installed by default and what seperately. After that my next action is to install symantec corporate on the server. Then I need to add the set IP address under Local Area Connections....then under my comp->properties I can changed the computer name and add it to the domain (vcom.xxxxxx.edu). And hopefully I should be connected to our parent network. From there I can take care of everything else. Does this process sound correct. Any advice is greatly appreciated. Sorry this is soo long! Scott

Are you connecting to an existing AD infrastructure ("parent network")? Or will this be from scratch?

You definitely need more planning. Is this network internet connected? What is your plan for a DNS infrastructure, since that will be needed for AD? What are the requirements for this app (sigmaplot)? If you setup AD, is a single point of failure acceptable since you only have one server? You really should have two DC's. "I can changed the computer name and add it to the domain (vcom.xxxxxx.edu)." How are you gonna join it to another domain while it's going to be a dc for a new domain. This has disaster written all over it. You're in over your head. Please help survivors of Hurricane Katrina! www.redcross.org

Get a qualified consultant. Not only are you going to get fired when this goes bad, you might get sued/be liable. You talk about setting up remote access/combining multiple servers/functions to one server, circumventing security/etc....bad for you when it blows up. Sounds like the NW admin that left left you hung out to dry. No shame in admitting to them you need help.

Wow guys thanks you for all of your help I appreciate it. Yes I realize I may be in over my head right now :(. Let me try to elaborate a little more here. There is already a big network above me and I just have to connect to it (vcom.vt.edu). Our small lab is in another building. It is an existing AD structure that I will be part of and under vcom.vt.edu in the AD we are under \VCOM\Neurolab right now. So I do not have to setup the AD which is nice. This network is internet connected. There is another DNS server above me that I do not manage. So I also do not believe I have to set up the DNS structure or any DC machines. Single point of failure is acceptable for this small lab. It is not a critical network. This sigmla plot I am not 100% sure about. All I know is that when the network fails so this program. It wouldn't be a problem just to purchase a bunch of multiple licenses I guess for it, but just a waste of money. I will look through the documentation and see what I can find. This part... "How are you gonna join it to another domain while it's going to be a dc for a new domain." is this still applicable? I am fairly sure this server does not have to be a DC I just have to connect it to the existing domain on another DC server. I appreciate your adivce guys and I will probably get a qualified consultant in here. I am not planning on doing anything anytime soon and definately am not looking to get sued. But like I said this is a very small netowork, probably the most simplistic you can get so I'm kind of looking at this in a positive light and if anything I will learn a lot of new skills from it. I am young (about 21) so I'm just starting out learning everything and definately got hung to dry. However I wouldn't mind hearing your advice/answers to some of these questions I just asked. I ordered a book by Minasi "Mastering Windows Server 2003" http://www.amazon.com/Mastering-Windows-Server-Mark-Minasi/dp/0782141307 Anybody have any other good books they would recommend? Also what is the going price for consultants usually so I can speak with my boss. Thanks again everyone!

"There is already a big network above me and I just have to connect to it (vcom.vt.edu)." Virginia Tech! Dude, you HAVE to have resources to consult with there! "So I also do not believe I have to set up the DNS structure or any DC machines." Correct. "Single point of failure is acceptable for this small lab. It is not a critical network." If you are a part of an existing AD infrastructure, then they should have multiple DC's, so that's not even a part of the equation. "This sigmla plot I am not 100% sure about. All I know is that when the network fails so this program." Now is the time to get sure about it. And when the network fails, it fails...well, congrats on knowing it's a network app. :-) Seriously, consult the documentation for the product, or get training to know how it works on a network level. What services/protocols/technologies does it depend upon to function? etc. "This part... "How are you gonna join it to another domain while it's going to be a dc for a new domain." is this still applicable?" No. You're using AD infrastructure already in place. Sounds like the AD admins should make an OU for your lab, and place all relevant computer/user accounts into it, and delegate this OU to you. "I appreciate your adivce guys and I will probably get a qualified consultant in here. I am not planning on doing anything anytime soon and definately am not looking to get sued." www.nortec.com They reach into the Blacksburg area. "I'm kind of looking at this in a positive light and if anything I will learn a lot of new skills from it." This is a good opportunity for you to learn, but you still should have some help and guidance. "I am young (about 21) so I'm just starting out learning everything and definately got hung to dry." Sink or swim = best way to learn sometimes. "Anybody have any other good books they would recommend?" Get a complete MCSE 2003 core set. "Also what is the going price for consultants usually so I can speak with my boss." Ranges wildly depending on how good the consultant or firm is. Give Nortec a call; they're exceptionally knowledgeable and will get you done right. 804.748.8077 Ask for Steve Estep. Tell him Aaron referred you. Please help survivors of Hurricane Katrina! www.redcross.org

Aaron, I really appreciate your help. I have spoke with the IT guy that heads the vcom subdomain and he helped me out a bit, however I believe I would be better off in the area of hiring a consultant from somewhere like notrec. Surprisingly though VT offers little in the area of consulting. Can I ask you a few more questions though? The active directory service is installed on the server and I can see many of the of other users of other OUs (I cannot change any of their permissions though). Is this normal of is there something wrong with how the AD admin has everything setup (did he delegate control of the OU improperly to me)? Also you say... "You're using AD infrastructure already in place. Sounds like the AD admins should make an OU for your lab, and place all relevant computer/user accounts into it, and delegate this OU to you." Right now I can add new printers users computer OU into my OU. I'm new to this stuff, but it seems that I shouldn't have access to this stuff, what do you think? As for that sigmaplot the newer version has a network license manager that is supposed to easily setup everything for you. I am still in the process of searching for the older manual blah :). You seem very experienced, what kind of network do you manage? Thanks again Aaron!