The server that will host the Exchange Server 2007 installation needs to have a 64-bit processor and a 64-bit edition of Windows Server 2003 or later installed.
However for testing and lab enviroments you can use the 32 bit version which is not supported in a production enviroment.
NOTE** Intel’s IA64 processors, known as Itanium, are not supported for Exchange 2007, eventhough Windows 2003 Server has a version for IA64.
The domain controllers and DNS servers in the environment, can have 32-bit processors and the 32-bit edition of Windows Server 2003 or later installed.
The server that hosts the Schema Master role must have Service Pack 1 or higher.
Exchange Server 2007 requires that there be a global catalog server deployed in each site in which Exchange is deployed.
Global catalog servers also must be patched with Service Pack 1 or higher if running Windows Server 2003 or be running Windows Server 2003 R2 or later.
Role Call!

Exchange 2007 was designed to be split up into roles.
With exception of the Edge Transport Server, and any clustered mailbox server (CCR or SCR).
(I will cover roles in more detail in another post)
All roles can reside on the same server meaning that initial deployment doesn't have to be as expensive as it first sounds.
However the first Exchange server you deploy should always be the Hub Transport Server Role, whether this be a new messaging organisation, or part of an existing one.
Software Pre Req's
Windows Server 2003-based computers require both
.NET Framework Version 3.0 and
.NET Framework Version 2.0.
Windows Server 2008-based computers only require
.NET Framework Version 3.0.
Microsoft Windows PowerShell (for the Exchange Management Shell) Windows 2003 Only (Included in Windows 2008)
Microsoft Management Console (MMC) 3.0
Memory Requirements

You need to be a member of The SysAdmin Network to add comments!
Join The SysAdmin Network