Ingredients for a new network!

[port27374]

Hello folks!

I have been requested to build a new network and was hoping i could verify some of the steps i take in order to build this new network with some of you peepz here!

the network will comprise of 1 server connected to a 24port network switch - which will also have a ADSL router plugged into it. this will also have 16 workstations plugged into it via RJ45 jacks wall mounted and hard-wired in the room.(which i will be doing myself also, once the electrician has done his bit with the power cabling).

I have PROVISIONALLY decided the best setup would be as follows:

1) 1 x Server (something like a P4 3.4Ghz, 2GB RAM, [2x160GB HDD {Mirrored}] etc...)

2) Netgear 24 port switch
3) Netgear ADSL router
4) Patch panel and cabinet which will contain switch router and patch panel. this cabinet will be wall mounted in a high place.

5) 16 x Pentium 4 machines - network ready.
6) 1 x HP 4100TN Laserjet printer
7) Epson 1290 A3 professional printer
(both network ready)

8)Server OS = Windows 2003 server (which version??) with 20 CALS.
9) Workstation OS = windows 2000 pro
10) Office XP Pro x16

11) all the networking cabling, power cords etc....
12) Security locks for equipment?

I believe these are the main hardware & software ingredients for the network i am required to build! (please feel free to add or suggest others)

Now then ... some questions i was hoping to get help with!

a) the server - what would be the main purpose of this server? i.e. it is not required for printing - it is not required for communications (i.e. exchange)... it is merely required for controlling username and password etc... which all i can be done through windows active directory?

Does the latest version of windows server come with some kind of dployment software for deploying images to workstations? if not what is a good solution for this?

b) Licensing - what is the best way to license the OS and office XP Pro? whats the difference between volume licensing and individually licensing each copy?

c) Server-architecture... the envisioned architecture of the server storage is as follows

MASTER1: 40GB System partition (this is where the OS will reside and this will be the main c
SLAVE1: DVD+-RW (For backup purposes)

MASTER2: 160GB HDD
SLAVE2 : 160GB HDD
These 2 will be mirrored for extra security of any data stored on the Server itself! this may also be used for storing initial backups of the active directory structure or configuration of the server.

does this sound ok?

d)Config question: should the server contain 2 NIC's with one connected directly to the router and the other connected to network switch?

OR

should i have the server with one NIC and connect everything into the main network switch?

whats the difference?

e) Service contract - the client is requesting a service contract, what factors would i consider before providing them with a quote... what would be required to maintain such a network for an off-site engineer?
is there a quick and simple rule to work out these costs (generally speaking)?

f) Any suggestions on a fairly secure and cheap solution for security locks for equipment.


Sorry about all the questions - im a little new to the networking game - please expect follow ups of any replies you post to this post - thankyou!

i really do appreciate any help and thankyou in advance!!!

best regards
Mo

 

[jimbopalmer]

I would consider a (72 gig?) tape backup to using 225 CDs as a backup solution.

http://www.certance.com/products/dds-dat/dat72/CD72LWE-SS

No idea what you intend to do with this office, but consider a Copier instead of the HP

http://www.office.xerox.com/perl-bin/product.pl?product=DC426ST

I tried to remain child-like, all I acheived was childish.

 

[crisper99]

Well you have a lot of questions there. I am quite experienced in quoting these solutions so here goes:

A) The main purpose in a small office for a server is mostly for file sharing and security. Each user would have an account and their profile information would be stored and be portable to pretty much any other machine inside the Active Directory Structure.

B) The difference in licensing for Microsoft is mainly if you are a partner or not. If you are a partner or a large corporation you can get the volume licensing rates from Microsoft. Sometimes you can get software alot cheaper from Microsoft Gold and other partners who get big discounts and often get the best orders.

C) The server seems fine the only thing is that you MUST buy a tape drive for this system. It is an extra expense but given what can happen to small business it is _ESSENTIAL_ that they purchase a backup drive, prefferably a DDS3 Drive with 36/72G Tapes that should be enough. keep in mind someone will have to rotate the tapes unless you plan on having one active backup which is not prefferential.

D) The server should be plugged into the same switch that the rest of the dektops are plugged into. If you are going to use netgear products then it doesn't really matter where you plug it in since the backplane is all shared anyway. The server should only have one NIC connected to the switch NOT both, which I have seen done and causes some interesting problems with Active Directory. The reason for this is that if you have your server plugged into the router then you will have to turn the server into a router which is not a good idea. The correct way to set things up for larger clients is to have a switch with VLAN's or virtual LAN's then the server would sit on its own VLAN, the client on another and then another interface to allow routing to the internet or WAN.

E) As far as a service contract is concerned you should clearly define the amount of hours that the contract will include. This solution is not something you can put a monthly cost on without sticking your neck out and losing money. I would say $150/hour with 2 - 4 hours of support included per month with on-site support if necessary. If you can't sell them on that then they are cheap.

F) Not much experience with this but unless the server cannot be carried by one person the locks are pretty much useless. If someone needs the server or the data on it then you can expect them to break in and walk out with it. Just like you can do in many datacenters....