Hello All, I am the IT guy for a public Library. We have 7 public machines on one network, 12 public machines on a separate network. I'm familiar with installing XP, setting up a peer-2-peer network, setting security permissions and User Management. I've worked with Group Policies and am well-versed with cloning/imaging software, formatting PCs, basic networking. We used to run a Windows 2000 Server that I did not setup for the 7 machines, but it seemed to be pointless for what it was used for (Active Directory, Firewall, Domain Controller). In other words, it wasn't very well managed. I'm interested in starting on a Windows 2003 project for the summer. I figured perhaps I'd start with the 7 XP Gateways and once I've got it under control, start up with the 12 Dells. I figured that at some point, we will probably have a total of 30 computers with 50/50 on each network, so it is sort of a pain right now to have to go to each machine to make a simple policy change. I do have a Network Administrator from another Library who could help me for $50/hr but being the only IT guy for this rather large library, I'd like to get to try and handle as much as possible on my own. I guess since i'm working with 7 Gateway XPs, I should get a Gateway Server and install a fresh copy of Windows Server 2003 myself. Not really sure how the licenses work, anyone have any ideas what I would need? Again, hoping to setup Domain Controller, Active Directory, and perhaps a Firewall. Let me know where you think I should start.

It's your personal opinion on what make/model server you want to purchase. Personally, I tend to sway towards Dells or HPs. The best way is to get quotes from multiple vendors (most government agencies are required to get multiple quotes). It requires a little more time but it’s the best method to ensure you're getting a good deal. My basics for servers consist of the following: Needs to support at least Dual processors (single can be purchased initially) At least 2 GB of memory Tape Backup Unit/Software Dual Nics Other than being a DC will it perform any other roles, i.e. DNS, DHCP, Exchange, File, Print, etc? I do not recommend running ISA or any other firewall applications on a DC. You may want to invest in a network appliance or o low-end server to handle Internet/Intranet traffic. What type of WAN connection do you have? Are you tied into any other libraries? In terms of the project, I do not believe you'll need an additional resource. Since this will be a new server with nothing in place, you have time to configure yourself. And the Windows 2003 interface is relatively straight forward. With all the wizards and online help, you should be able to handle the configuration and troubleshooting. Windows licenses: Per Seat - meaning each client much have a license to access resources on the server (typically used in small mid-sized environments) - OR - Per Server - Each server has a set number of CALs (Client Access License) that it issues out to clients accessing its resources. In your network, I would use Per Seat license. Windows Standard usually comes with 5 CALs. So, you’ll have to purchase additional CALs to be compliant with Microsoft. If you fill in the blanks, I’ll try and help you further.