Hi,
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 -
http://technet.microsoft.com/en-us/library/aa996719(EXCHG.140).aspx
http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx
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:
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!
For the few who are still working with Windows 2000 Domain, I would like to share with you a few articles I collected that can help with the process of upgrading your Domain to Windows Server 2003.
You should also know that besides the benefits of Windows Server 2003 Active Directory (http://www.microsoft.com/windowsserver2003/evaluation/overview/technologies/activedirectory.mspx), An 2003 forest level is essential for the full functionality and advanced features of Exchange Server 2007.
Here are the articles -
How to upgrade Windows 2000 domain controllers to Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
In this article, there is a part talking about upgrading environment with Windows 2000 Forest when there is Exchange 2000 present. This part explains how to manually update Exchange Attributes before the upgrade.
Access is denied when you run Dcpromo.exe to create a replica domain controller, you receive the "Failed to modify the necessary properties for the machine account”:
http://support.microsoft.com/kb/232070
You will probably encounter this error if you hardened your servers using Group Policy and changed the permissions for the Enable Computer and User Accounts to be trusted for Delegation value.
How to Enable Schema Modifications for a Windows 2000 Server Domain:
http://technet.microsoft.com/en-us/library/bb632955.aspx
On Windows Server 2003 domains the schema is enabled for updates by default. For Windows 2000 Server domains, you must manually enable updates on the schema master.
Steps for Extending the Schema:
http://technet.microsoft.com/en-us/library/cc773360.aspx
This article will guide you through the steps of checking Active Directory functionality, how to extend the Schema and how to verify the schema extension.
How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003:
http://support.microsoft.com/kb/325473
I most cases, the domain controller is also functioning as the DHCP server. When upgrading Windows 2000 Server DHCP to Windows Server 2003 DHCP, you should use DHCPExim to export the DHCP database from Windows 2000 and use NETSH to import the database to Windows Server 2003.
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain:
http://support.microsoft.com/kb/555040
Very good article that will give you guidelines and links that will help you with the upgrade.
Hope it Helps…
Thanks for Reading!