Interesting question. Right up the alley for all us designers and designer wannabe's. First of all, and presuming you meant "fool proof plan" keep in mind that there is no such thing as fool proof. A fool can screw up anything! Secondly, while number of users is one factor, the applications and services used by those users is every bit as important. Are people doing collaborative sharing of CAD-CAM drawings ( lots of network strain ) or clerical work ( mostly invoices, letters, etc ) and perhaps less network strain? Exchange can be resource intensive, but on the other hand, one server can support thousands of users, so maybe exchange can be collocated with some of your other services? DHCP is in general fairly benign as a resource user, especially for so few users, as an example. I know of several small client shops where their e-mail, DNS, and proxy are all run on a single box. Organization of user data and shares? I can guarantee that no ma what scheme you come up with, there will be those who don't fit your pattern, and as a result will require exceptions to the rules you determine. For example, when I worked in brokerage, the rule was that no broker was permitted to see another broker's files. However, brokers often shared sales assistants, who did have to see files for multiple brokers. Then one day broker Joe and broker Mary would get together on a project or work a deal to share their business, and now both need to see each other's stuff. Or worse, they would need to see some things and not others. Rhyme and reason went to hell real fast. IIS - for e-commerce? How much traffic? Security issues? I think in general I'd want that box to be self contained, and in my DMZ with some hard and fast firewall rules. For internal use only? Again, depends on usage. But it might be shared with other services, especially if it is serving up SQL based information. I hope this is giving you an idea of how best to approach this. To quote a sage who graces this group from time to time, think in terms of Top Down Network Design. It makes it a lot easier to come up with a plan. Best wishes. Chuck -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Kevin O'Gilvie Sent: Monday, May 21, 2001 12:10 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server Architechture/ Data Organization [7:5310] Hi Everyone, I am in the process of reorginizing this my network, Prior to me everything was just put everywhere and I need to come up with a full proof plan. My questions are: -For a 60 user enviorment how many servers do I need to run Active Directory on, Should AD be on a dedicated box? -How should I organize data, (users / corp data/ Fin Data) What restrictions should I put on these shares? -DNS, Wins, DHCP, Exchange, SQL, IIS5, Inoculate, Backup Exec, Print Services, .... What should be on dedicated boxes what shouldnt? TIA, Kevin _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=5334&t=5334 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
