• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

need help with possible win2k3 server purchase

StickyLoad

Limp Gawd
Joined
Feb 1, 2002
Messages
488
Hello Hardforum

I need some help here. We are looking at possibly implemening a win2k3 domain environment for 40 users. I have no idea what kind of hardware requirements I should be looking at. Do I go for the 32 bit or 64 bit version? Will ide drives work, or should I look at scsi?

We are wanting to run microsoft project on this machine, along with iis, sus server, probably dns.

I guess my biggest question is really with the hardware stuff, so any similiar experiences would be great. We run a unix server as our primary server in this office, which is a dual amd 64 bit machine.

As always, thanks in advance.
 
When you say run Microsoft Project on it, do you mean a Project Server? Or Project the application? Project server requires SQL Server on your network, so it can get pricy fast. And I do not recommend running applications on any server.

For 40 users, you do not need 64bit.. if the CPU is x86-64 or EM64T it doesn't matter, just run the normal version of server 2003 (or even small business edition, if you want SQL and Exchange etc.)

As for specs, even a P3 would be fast enough for the things you list.. I highly recommend you get a server from a vender like HP, IBM, or even Dell (last choise) over building your own. (HP Proliants are my favorite)

What kind of uptime do you need? The more critical that uptime is, the more you spend.. on things like redundant power supplies, battery backed RAID cards, separate UPS's for each power supply etc. etc. (I don't have separate UPS's, but do have redundant PS's on my servers.. because I actually share the UPS's between servers, so if a UPS dies, the server will run off the UPS of another server till it is replaced, not perfect, but good enough in my case)

As for SCSI/IDE, depends on the I/O load on the server, I personaly use SCSI for all my servers, and IDE only for near term backups. (in addition to Tape)

==>Lazn
 
Lazn_Work, thanks for the reply.

Its not going to be a super mission critical server as our unix server we run does a bulk of the work in our office. It would be running project server edition so users could access it from anywhere with an internet connection.

I haven't had a lot of expirience with microsoft servers and thought this was a good place to start. Thanks again!
 
http://www.microsoft.com/office/project/prodinfo/serverreq.mspx

You really don't need much horsepower.. but:
"Project Server 2003 processor, RAM, and hard-disk requirements are highly dependent on the number of services installed on the computer and the load on the server. Minimum requirements assume one server on which all Project Server components and supporting technologies (that is, Microsoft SQL Server™, Microsoft Windows® SharePoint™ Services) are installed. Windows SharePoint Services is required for project collaboration; Windows SharePoint Services requires Windows Server 2003 or later and the NTFS file system; Microsoft SQL Server Analysis Services with SP3 or later (included with Microsoft SQL Server) is required for Portfolio Analyzer (OLAP Reporting); e-mail requires Microsoft Exchange 5.5, 2000, or later; Internet Simple Mail Transfer Protocol/Post Office Protocol 3 (SMTP/POP3), Internet Message Access Protocol 4 (IMAP4), or MAPI-compliant messaging software is required for e-mail notifications"

So all the needed support software stuff can add up your cost way over the actual hardware.

One thing is you should keep the server behind a firewall and only forward the ports necessary to give your user access from the internet.. Because you do not want a Windows box on the internet directly.

==>Lazn
 
Back
Top