Discussion Locked

Planning Windows 2000 Network

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi there. I am planning a Windows 2000 Server network
installation and i would apreciate some help on this
subject. My network will have about 30 workstatios and i
would like to know your opinion about using one or more
servers. We are planning to buy Backoffice Server 2000.I
have two scenarios:
Scenario 1:
I could set up two servers one of wich would be my Domain
Controller running Windows 2000 Server with Exchange
Server 2000 and the other server running Windows 2000
Server and SQL Server 2000.
Scenario 2:
I could set up just one server wich would run all my
Server products ( Windows 2000 Server, Exchange Server
2000 and SQL Server 2000 ). In this case my Server would
be the Domain Controller of mydomain.com and at the same
time my database server.
Adittional Information:
I will have about 30 users logging on the domain 25 of
them using simultaneasly the database.
My Database has in this moment about 3,5GB
My new Server has the following main characteristics:
2 Pentium Xeon Processors 2.4 GHz with 512K cache each;
2GB RAM;
2 HDD 36,7GB Ultra 160 SCSI SCA wich i intend to use has
my system partition implemented with RAID1;
3 HDD 73GB Ultra 160 SCSI SCA wich i intend to use has my
database partition implemented with RAID5;
Do you think i could use this server as the only server on
my network or should i set up it as a member server of
mydomain.com using another server as the domain controller?
Thanks
Ricardo Ferreira

9 replies

by timwalsh

While SBS looks like a great deal, by integrating the most commonly used server packages from MS, you may want to rethink buying SBS for the following reasons:
1. All the SBS applications must be installed on the same server which also must be theDomain Controller.
2. Licensing caps out at 50 users. Since you already have 30 users, that doesn't leave you a lot of room for growth. The only way to grow beyond that 50-user cap is to purchase the stand-alone versions of each server package.3. SBS (and Exchange 2000 as included with SBS) cannot be installed as part of a larger Active Directory (or Exchange) organization.

Having said that, if you don't forsee any large-scale business growth for the foreseeable future (or any merger possibilities), and if you don't mind having all your apps running on one server (the hardware configuration you mention above is plenty robust to handle that), SBS may in fact meet your needs. I would recommend installing a second server as an additional Domain Controller from the standpoint of "best practices," although it is NOT absolutely necessary. If you do choose to do this, you can use a standard version of Win2K server.

by admin

a lot of features I needed even though it had the right programs. My first Network attempt was a fiasco with SBS and we aborted it. It was my first and best lesson, and I was lucky to work for people that willingly paid for a somewhat expensive learning experience. It may work for you, but for too many reasons to list, it didn't meet our needs (we were at about 40 ws at the time) I have had no problems with the full versions.

I'm not saying it won't work, but research it well, don't assume that any program packaged with it will have the full features of the full version.

by ghstinshll

I do see how SBS would be an option, but I've never used it in an environment as large as yours. Given Tim's reference to limited growth opportunities, the licensing would either cost you a lot more money down the road OR limit your growth. I'd assume the first is what would be more likely to happen.

You're probably not going to buy a new server or any additional servers for 4-7 more years, so this would implicate that you'll probably grow past the 50 CAL limit on SBS. I'm also not a firm believer in putting all your services on one server, regardless of hardware, esp when it comes to domain controller + DB + Exchange... That's a lot of hay to pull behind that horse!

Given your scenario, I would use the old server for your PDC, use the 2nd server for a BDC & service server. Then purchase the individual software packages you need. This will give you the growth you aren't able to see right now. Purchase enough licenses for your current users, but this model allows you to add additional functionality & additional users easily. You'll also have the logon redundancy for users to get logged on...

One last thing to cover is to make SURE you have at least 3 drives - in a RAID5 array. Since you don't have additional servers to cluster with, you'll need to keep uptime in mind. Add that extra drive for $400 to ensure if a drive fails, you'll stay running.

by ghstinshll

To add-on to my previous, ONLY use SBS if you can guarantee that in the 7 years you won't grow past the 50 CAL limit of SBS. If you can't, plan on doing it the long way.

Since you're running the environment you're in, good firewall security should be considered as well. Some kind of a Cisco PIX should be implemented, running NAT and having a secure configuration on it. This is a must for SBS, but a highly miportant ojbect to have regardless of your network design.

by rcdoferreira

For a firewall solution i intend to use a PC with 2 NIC, running windows 2000 server and i intend to implement IP routing with NAT. One of my nic will be connected to a cable modem connection to my ISP and the other nic will be connected to my private network. On this machine i am planning to install a firewall software, perhaps the wingate firewall solution. You see i don?t think my Boss is able to buy a hardware firewall specially from cisco. What do you think about my solution?

by admin

in this scenario is the other fatal flaw. When one thing goes and everyone and every service is down it's a nightmare. The cost to his company hourly over a year when everyone can't work should be staggering enough to quickly to have a BDC or another AD + back-up. I would also think it would pay off to put Exchange and the DB on seperate boxes rather quickly. People can usually workaround interruptions in one service at a time, and as you say, it's also going to be down more often running all this on one.

Good Advice. I just thought I'd add to it because I thought it was so good :)

by hal 9000

But wouldn't you be better off waiting till next month when 2003 becomes available as it has some better features than 2000 as well as a longer life expency from Microsoft. As previously stated you are looking at a 5-7 year use of this equiptment and Windows only has a 5 year life support from MS so I wait the few extra weeks for the new Windows as it will give you a longer operating life without the need to upgrade/mirgrate in a few years. Bear in mind the 2000 is already over 2 years old and will only be supported for another 3 years or so and the mirgration to 2003 will cause a lot of pain and sleepless nights so I'd wait. Also as we don't know what will follow 2003 there could be a very big problem trying to mirgrate to whatever Microsoft produce in the future.

by admin

This will work, but for much less you could run linux on an old box & use the software packaged with most distro's or else even use an old box, as Lord Infidel pointed out, with bbiagent and get the necessary linux and firewall\router software for 36$ US. Then you have no expensive licensing issues and can use the 2k box to run exchange on.

It's just an idea. :)

by ghstinshll

A PIX 501 firewall costs just $400, I think that's as much as a PC, and having a PC on the network as the NAT box doesn't truly supply a layer 3 security device... It routes, but only a true layer 3 device can really supply what you need in security.

This discussion is closed to new replies.