Building a Windows Server 2003 Network

Associate
Joined
31 Jan 2007
Posts
1,860
Hello,
I am part way through my course at uni and one unit has us setting up a Windows Server 2003 network and it is confusing the hell out of me due to the lecturer being rubbish so I ahve decided that I would ahve a go at home and I ahve got myself a disk of Windows Server 2003 and have several questions:

1). I have several spare machines laying aound which I can use for the server and the rest as clients but I need a KVM to allow me to switch the keyboard, mouse and monitor (and speakers) over to each machine. Could someone reccommend me a cheapish KVM whcih I can plug into at least 4 machines and allows me to use a VGA monitor, 3.5mm audio jack, 2 usb ports and PS2 ports.

2). I also need a switch to connect all the machines too. I just need a basic 5 port switch. I ahve no idea how to configure it or which one to buy so reccommendations would be appreciated.

3). I then need some links to easy to understand and follow guides or tutorials on how to set the system up from scratch. Just basic things like Installing active directory (what active directory is and does), how to configure what users are able to do when they log on and off, domains, profiles, set up the server as a DHCP server, GRoup Policies. That sort of stuff. I have listed things that have been talked about over the past few weeks but have confused me so I need to learn what they are, what they do and how to use them and configure them.

I really would appreciate all your help

Thanks
 
sorry this doesnt really answer your question, but how about using virtual machines instead of 'real' ones?
 
I'd rather use real machines so I can see it all working and I ahve plenty of spare machines laying around to use but need help on choosing the two bits of hardware I specified above and tutorials on settings the server up
 
If your desktop is pretty decent then use VirtualBox - you could easily run a 2k3 DC plus some basic 2k3/XP clients - the only bit you wouldn't be able to see is the physical switch connections (as it would be virtual :p) Other than that it's exactly the same.
 
I have said I wish to use real machines. I might as well use them as they are sat here. I DO NOT WANT TO HAVE AN ARGUMENT about using virtual or real machines. I just want help with understanding how it works and reccommendations on what I asked in my OP!
 
For testing purposes I would just use virtual machines as posted. They can be networked together and means you could have a number of servers and clients either on one PC or just a couple. No need for extra cables and all the electric.

If you really want to go down the physical route.

You will need a simple 5 Port 10/100MB Switch. No need for configuring (just get an unmanaged one £5-£10)

As for setting up from scratch and researching what AD is / does etc. It would be worth picking up a MS Press book, for a good overview. something like 70-290 would be best. There is a lot to learn but that should cover the basics.

Its hard to tell what your current level of knowledge is. But the press book should help, and if you want to sit the exam at any point you have the material right there.

If you don't want the book, there are hundreds of guides on the net.

I could run through a quick overview, but there would be a lot to cover. Active Directory is as it suggests - as 'simple' database that holds information on users, groups, computers etc. Group policy is as you suggest a method of pushing changes to machines (mostly through registry), the changes can be targated at machines and users.

DHCP is simply a server role that allows the server to give an IP address to the computers on the network. This is so they can all communicate, and reduces the amount of administrative overhead if the IP strategy changes. Servers are generally configured manually, to ensure a single consistant IP address.

DNS is a biggy, basically it contains a list of every machine name so 'computer1' and the IP address it has so '192.168.0.15', this allows you to then use friendly names to locate resources via use of UNC \\server\resource or \\server.domain\resource. DNS underpins active directory and is extremely important.
 
Last edited:
DHCP is simply a server role that allows the server to give an IP address to the computers on the network. This is so they can all communicate, and reduces the amount of administrative overhead if the IP strategy changes. Servers are generally configured manually, to ensure a single consistant IP address.

DNS is a biggy, basically it contains a list of every machine name so 'computer1' and the IP address it has so '192.168.0.15', this allows you to then use friendly names to locate resources via use of UNC \\server\resource or \\server.domain\resource. DNS underpins active directory and is extremely important.

Remember, if using a router, you are *likely* to have that providing DNS and DHCP Server services. You will need to switch these off at the router, and let the server control both.
 
just get a KVM from an auction site... should be around £20 or so. Get one with cables, will save hassles later. You don't need USB or audio. don't bother with it.

Any switch will do - can get them for a few pounds from most places...

With only one screen it's going to be really tricky to 'do stuff'

In saying that, you'd be better off getting a tri or quad screen setup, and running a virtual network. But it seems you won't realise this until you have built a physical network.
 
Thanks guys. I would prefer to do it physically this time around and it won;t be connected to our home router which provides our internet connection so thats fine. We do it at college with just one screen and a kvm to flick between the machines and that works fine. I need to find one with usb as my mouse uses a usb connection so could someone reccomend one?
 
Just get a Ps/2 mouse. You'll pay extra for a KVM with USB. (seriously you can pick up 8+ port PS2 KVMS for peanuts if you know where to look. I got a quality 8 port one (no cables) for £3 at a boot sale)
 
Last edited:
Back
Top Bottom