Asked by:
Exchange 2010 Release Candidate Ships!

General discussion
-
Earlier this morning, we released the Exchange Server 2010 Release Candidate to the Microsoft Download Center! The declared build number is 14.00.0639.011. The direct download link is http://www.microsoft.com/downloads/details.aspx?FamilyID=c6d27da1-ba2c-4570-a491-c0d7b39ede8b
This build is compatible with both Windows 2008 SP2 and Windows 2008 R2 (from RC1 through to RTM). As we changed the store schema between the Exchange Beta and RC, there’s no in-place upgrade from the Beta release. However, we will support in-place upgrade from the Release Candidate through to the final RTM build.
I hope you enjoy all the new features in this build. Keep the feedback coming!
Paul Bowden
Release Manager
Exchange Server
--------------------------------------------------------------------------------------------
Here’s a quick start guide to get you up and running as quickly as possible with the new build:
Windows 2008
1. Install Windows Server 2008 x64 (Standard or Enterprise – but not Core or Web Server) and join the appropriate domain
2. Install Service Pack 2 from http://technet.microsoft.com/en-us/windows/dd262148.aspx
3. Install .NET Framework 3.5 Service Pack 1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7
4. Install the .NET Framework 3.5 SP1 Update from http://www.microsoft.com/downloads/details.aspx?FamilyID=98E83614-C30A-4B75-9E05-0A9C3FBDD20D
5. Install the combined PowerShell v2/Windows Remote Management package (Windows 6.0-KB968930.msu) from https://connect.microsoft.com/windowsmanagement/Downloads/DownloadDetails.aspx?DownloadID=21268
6. For Hub Transport and/or Mailbox roles, install the Office Filter Pack from http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC
7. Open a command prompt, and use the installation scripts from the \Scripts sub-folder on the installation media to enable operating system components:
a. For a typical installation of Client Access, Hub Transport, and the Mailbox role, run:
· ServerManagerCmd –ip <media>\Scripts\Exchange-Typical.xml
a. For a Client Access role only, enter:
· ServerManagerCmd –ip <media>\Scripts\Exchange-CAS.xml
b. For a Hub Transport role, enter:
· ServerManagerCmd –ip <media>\Scripts\Exchange-Hub.xml
c. For a Mailbox role, enter:
· ServerManagerCmd –ip <media>\Scripts\Exchange-MBX.xml
d. For a Unified Messaging role, enter:
· ServerManagerCmd –ip <media>\Scripts\Exchange-UM.xml
e. For an Edge Transport role, enter:
· ServerManagerCmd –ip <media>\Scripts\Exchange-Edge.xml
8. For Client Access server roles, run “sc config NetTcpPortSharing start= auto” from a command-prompt
9. Restart the computer
10. Run the Setup.exe program from the Exchange 2010 download package
Windows 2008 R2
1. Install Windows Server 2008 R2 (Standard or Enterprise – but not Core, Web Server or Foundation Server) and join the appropriate domain
2. For Hub Transport and/or Mailbox roles, install the Office Filter Pack from http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC
3. Open a Windows PowerShell console window from the Accessories menu
4. Enter “Import-Module ServerManager” and press return
5. Use the Add-WindowsFeature cmdlet to enable operating system components:
a) For a typical installation of Client Access, Hub Transport, and the Mailbox role, enter:
· Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy
· Set-Service NetTcpPortSharing -StartupType Automatic
b) For a Client Access role only, enter:
· Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy
· Set-Service NetTcpPortSharing -StartupType Automatic
c) For a Hub Transport role or Mailbox role, enter:
· Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server
d) For a Unified Messaging role, enter:
· Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Desktop-Experience
e) For an Edge Transport role, enter:
· Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS
6. Restart the computer
7. Run the Setup.exe program from the Exchange 2010 download package
Active Directory Configuration
a. The schema master must be running a minimum of Windows Server 2003 with Service Pack 1
b. The forest must be in Windows Server 2003 functionality mode (or later)
c. All Exchange 2010 servers must be able to communicate with a global catalog server which is running Windows Server 2003 with Service Pack 1 (or later)
d. Read-only domain controllers (RODC) are not supported with Exchange 2010
e. We generally recommend that you install Exchange 2010 on member servers versus domain controllers. This helps to secure your installation
Tuesday, August 18, 2009 8:25 PM
All replies
-
Let the fun begin. Congratulations on the milestone, Paul!
Brian Day / MCSA / CCNA, Exchange/AD geek.Tuesday, August 18, 2009 8:43 PM -
Thanks Paul, I have downloaded it successfuly, lets play with it.
Shambhu :-)Wednesday, August 19, 2009 3:27 AM -
Thanks Paul! My night just became many many more hours later now :D-Garrett
Garrett Lynch, Lynch Research Group, LLC.- Edited by Garrett Lynch Wednesday, August 19, 2009 4:49 AM
Wednesday, August 19, 2009 4:48 AM -
...
5. Use the Add-WindowsFeature cmdlet to enable operating system components:
a) For a typical installation of Client Access, Hub Transport, and the Mailbox role, enter:
· Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy
· Set-Service NetTcpPortSharing -StartupType Automatic
Wednesday, August 19, 2009 11:58 AM -
For all you Web Services programmers out there, we shipped the Release Candidate of the Exchange Web Service API today. You can download it at http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=e8f38dd1-f123-4a16-b4c8-584d1f84af48
I'll have another Exchange 2010 download "goody" for you tomorrow!
Cheers, Paul.Thursday, August 20, 2009 1:18 AM -
Thanks Paul!Here is the quick installation guide with screenshots based on the steps outlined by Paul...Exchange 2010 RC: Quick Installation Guide
Amit Tank | MVP – Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
Saturday, August 22, 2009 5:03 PM -
I promised another Exchange 2010 download nugget for you. Here it is! The Exchange 2010 Release Candidate Management Pack for SCOM - http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a0047276-553c-4054-afc9-ec3b4ececf3c ...this is the version for 32-bit SCOM servers. I'll have the 64-bit version for you real soon.
Cheers, Paul.Sunday, August 23, 2009 7:24 PM -
2 Points to the startpost:
1. No RODC with Exchange 2010? Could you clear this out? Is it really not allowed to have RODCs in your Domain if you want to use Exchange 2010?
2. Where seems to be a minor bug in the RC: When I create "New managed Content Settings" under "Managed Default" folders for the Inbox for example I get as Action "Mark as Past Retention Limit" Twice.Tuesday, August 25, 2009 11:47 AM -
1. You can have as many RODCs in the forest/domain as you want to, but Exchange 2010 cannot make use of them. So for instance, if you have a branch site where you plan on deploying Exchange 2010, you must also have at least one "normal" domain controller located here.
2. I'll let others answer this one.
Henrik Walther | MVP: Exchange | MCM: Exchange 2007 | MSExchange.orgTuesday, August 25, 2009 12:09 PM