I've been asked by a friend to set up a 2000 network for his small company. He wants to set up 7 xp clients to access a 2000 server. I have been into networking for about 8 years now and I have my A+ and Net+, however, I have never configured a 2000 server from scratch like this. Any advice? Any websites that break it down step by step in general? Or other resources? Like I said, it's going to be a small network so it shouldn't be too complicated. What considerations should I take? Just want to be sure I don't forget anything. Setting up the infrastructure doesn't bother me at all, it's just configuring 2K server from scratch. Advice? Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
2000 from scratch 2
- Thread starter tb913
- Start date
-
1
- #2
Hi. You should probably do a search on Microsoft's TechNet and Knowledge Base, as well as the internet. There are thousands of sites available to help.
Change the local administrator password, by default it is blank.
Run Windows Update and install all service packs and security patches. Do this before you install any additional software.
After each SW install, make a copy of the system state data.
Click Start>Run and type in MMC. Click CONSOLE, then click Add/Remove snap-in. Click ADD in the window that opens and check out all the specific ways you can configure the server. WRITE DOWN what you change, and where.
Create an Emergency Repair Disk (ERD).
Add Firewall and Anti-Virus.
There are a million more tips. I hope these few give you a place to start.
Corie
Change the local administrator password, by default it is blank.
Run Windows Update and install all service packs and security patches. Do this before you install any additional software.
After each SW install, make a copy of the system state data.
Click Start>Run and type in MMC. Click CONSOLE, then click Add/Remove snap-in. Click ADD in the window that opens and check out all the specific ways you can configure the server. WRITE DOWN what you change, and where.
Create an Emergency Repair Disk (ERD).
Add Firewall and Anti-Virus.
There are a million more tips. I hope these few give you a place to start.
Corie
-
1
- #3
TSMJ
MIS
- Nov 27, 2002
- 83
Hi
Depends what your mate wants from the server really - you can either just get it running as a fileserver (simply providing shared drives to the network) or get it running Active Directory which'll give you an actual domain for the network and allow users on the workstations to log onto the server to get their own settings. Roaming profiles is loaded into AD and is also an option - any changes made on a workstation by a user are loaded onto the server when they log off, and then applied to whatever machine they log onto next time - which is good for small networks like yours.
Setting it up as a fileserver is very simple (tahoe2 gave you a load of good things make sure you do before doing anything), and setting it up as a DC (Domain Controller) for the LAN is also fairly self explanatory (requires a bit of fiddling) - nothing such a qualified person can't handle!
Going 'Start>>Programs>>Administrative Tools>>Configure your server' will give you wizards to guide you through both of the options I described. If you set it up as a DC then run the DNS wizard it'll pop-up at you aswell, and before joining the clients to the domain make sure their Primary DNS is set to the IP of the DC. You join clients to the domain by Going 'My computer (Properties)>>Network Identification'.
Hope this helps.
Depends what your mate wants from the server really - you can either just get it running as a fileserver (simply providing shared drives to the network) or get it running Active Directory which'll give you an actual domain for the network and allow users on the workstations to log onto the server to get their own settings. Roaming profiles is loaded into AD and is also an option - any changes made on a workstation by a user are loaded onto the server when they log off, and then applied to whatever machine they log onto next time - which is good for small networks like yours.
Setting it up as a fileserver is very simple (tahoe2 gave you a load of good things make sure you do before doing anything), and setting it up as a DC (Domain Controller) for the LAN is also fairly self explanatory (requires a bit of fiddling) - nothing such a qualified person can't handle!
Going 'Start>>Programs>>Administrative Tools>>Configure your server' will give you wizards to guide you through both of the options I described. If you set it up as a DC then run the DNS wizard it'll pop-up at you aswell, and before joining the clients to the domain make sure their Primary DNS is set to the IP of the DC. You join clients to the domain by Going 'My computer (Properties)>>Network Identification'.
Hope this helps.
- Thread starter
- #4
Hey, thanks a ton for the info. I think I will need to set up active directory and have the clients join the domain because they have an application that they are going to run on the server, so it's not just going to be a fileserver. I think I'll set up a box at home and stage the whole thing there first so I can work through some of the kinks before I actually dive into it at the client's site.
- Status
Similar threads
