Microsoft recently released a beta version of the next Exchange server – Exchange 2010.
With a quick registration, you can download the beta from http://technet.microsoft.com/en-us/evalcenter/dd185495.aspx .
The download size is only 295 MB (About 500 MB when extracted), but don’t forget this is only a first beta.
This beta release is only available in x64 so you’ll need a supported CPU for testing. If you are going to install the beta on a virtual machine, you’ll need an application that support it. Be aware that Virtual PC only supports x86 guests.
Exchange 2010 Setup
A full system requirements and prerequisite can be found in the following links –
To make the long story short, I’ll summaries all the pre installation here, for a Typical Installation (Cas/Hub/Mailbox) of Exchange 2010.
First of all, Exchange 2010 must be installed on Windows Server 2008 or Windows Vista SP1 (!?) and must be a member server in an Active Directory Domain. After installing the operating system and configuring it as a Domain Controller (It can be the same server if it’s just for testing…), you should run Windows Update to patch the server with the latest security/critical/recommended updates.
Secondly, there are 4 components that have to be installed before starting the exchange installation:
Installing these components requires a restart, so please do so.
At first I thought that that was enough, so I started the installation which result with the following screen:
After checking the error log and Technet for specific installation requirements, I found out that I’m far from over and there is still some more job to do… so, here are the rest of the requirements:
After the server is up again from the previous restart , you’ll need to install the IIS components.
Because we are running Windows Server 2008 with PowerShell, type the following Cmdlets to get the job done:
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i NET-HTTP-Activation
ServerManagerCmd -I RPC-over-HTTP-proxy (If Needed for ‘Outlook Anywhere’…)
You should also install the Remote Server Administration Tools by using the following Cmdlet:
ServerManagerCmd -i RSAT-ADDS
That’s not all. The next step is to install the following required updates:
- Update that extends the mechanism for displaying snap-in context Help topics is available for the MMC in Windows Server 2008
- 2007 Office System Converter: Microsoft Filter Pack
- You cannot create multiple RMS Client sessions for one user context on a Windows Vista-based computer
- A Windows Server 2008 update lets you use the RPC redirection (RDR) interface to enable or disable custom load balancing based on server name and port number
About IPv6 and Exchange 2010 – From my experience with the installation, disabling the IPv6 from the network card is not a good idea… It appears that IPv6 is required for the Hub Transport Role. If you disable IPv6, it will result with the Hub Transport Role service not starting which will cause the installation to fail.
Well.. that’s all. You are now ready to install a typical installation of Exchange 2010.
Here are the installation screens from my test installation:
Hope it helps with your testing!