Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Design / January 2005

Tip: Looking for answers? Try searching our database.

best practises during exchange 2k3 server standard edition deploym

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
sphilip - 22 Jan 2005 08:41 GMT
we are deploying exchange 2003 std edition on our windows 2k3 std
edition.....is this ideal?

please advice me or point me to web pages on the best practises, configs
that i must keep in mind to setup our exchange server for 200 users, using
OL2k3.

cheers
Rui J.M. Silva - 26 Jan 2005 09:59 GMT
Exchange standard has a limitation of 1 single storage group, 1 mailbox
store, maximum size 16GB.
I think that will be just fine for 200 users.
The best advise I can give you has to do with file location. If possible
install Exchange Logs and DBs on separate disks:
Logs: RAID 1
DB: ideally RAID 0+1, if not possible, RAID 5

At the end of your installation you can run Exchange Best Practices Analyzer
Tool (www.exbpa.com).
There's lots of good documentation at the Exchange Server 2003 Technical
Documentation Library
(http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.mspx)

Signature

Blog "subject: exchange"
http://spaces.msn.com/members/ehlo

> we are deploying exchange 2003 std edition on our windows 2k3 std
> edition.....is this ideal?
[quoted text clipped - 4 lines]
>
> cheers
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.