On Fri, 5 Jun 2009 11:54:37 -0700 (PDT), Gre0145
We just finished a similar migration to you.
A couple of points about that config:
Where is the OS/programs going to be installed (it is best practice to
have it separate from data/logs storage).
It is also best to have log storage separate from the databases.
We went with a PE 1950 with 2 quad-core processors, with RAID-1
mirrored disks for the OS, and 8GB of RAM (will probably upgrade to
We purchased a MD1000 drive enclosure for this and have in the
enclosure 7 300GB drives - 4 of which are RAID-10 for the data volume,
2 are RAID-1 for the logs and 1 is a global hot spare.
All roles on one server (except for edge obviously).
Have you looked into redundancy?
It is best not to make the server a DC - it needs to be a domain
member though. Depending on your user base/requirements have you
looked into Small Business server or Essential Business Server? If
you are adding Exchange into the mix with the current configuration I
would also recommend a second domain controller, because they are
essential for Exchange operations.
This was how our previous system worked also, and it isn't really a
supported configuration in the Exchange 2007 space. The Exchange
servers need to be on the same side of the network as the domain
controllers (no firewall between them). The only server that is
allowed on the DMZ is the Edge server, and if you like us have a
policy of only allowing publishing external resources on the DMZ side
(not allowing to publish internal servers), then you may need to
invest in something like ISA 2006 to publish the POP3, IMAP, HTTP etc
from the Exchange server to the external interface on the ISA box, and
thus to the DMZ of the firewall.