Update Rollup 1 for Exchange Server 2010 Service Pack 1 (KB2407028) is now available to download.
The Microsoft Exchange Team has posted additional information regarding this update on their blog, from which I would like to highlight the following:
Note for Forefront users
For those of you running Forefront, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable ForeFront via fscutility /disable before installing the patch and then re-enable after the patch by running fscutility /enable to start it up again post installation.
According to the same blog post, Rollup 2 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in early December.
Update Rollup 1 for Exchange Server 2010 Service Pack 1 resolves issues that were found in Exchange Server 2010 Service Pack 1 since the software was released. This update rollup is highly recommended for all Exchange Server 2010 Service Pack 1 customers.
For a list of changes that are included in this update rollup, see KB2407028.
- Supported Operating Systems:Windows 7;Windows Server 2008 R2;Windows Server 2008 Service Pack 2;Windows Vista Service Pack 2
- Exchange Server 2010 Service Pack 1 must be installed prior to installing this update rollup.
- Any Interim Updates for Exchange Server 2010 must be uninstalled prior to installing this update rollup.
Ross Smith IV announced at the Microsoft Exchange Team Blog that the Exchange 2010 Mailbox Server Role Requirements Calculator has been updated to version 12.8.
According to the Updates Tracking page, here’s the list of changes:
Enhancements (introduced in version 12.1)
- Open a web browser and got to www.spec.org.
- Click on Results, highlight CPU2006 and then select Search CPU2006 Results.
- Under Available Configurations, select SPECint2006 Rates and click Go. Under Simple Request, enter the search criteria (e.g. Processor matches x5550).
- Find the server and processor you are planning to deploy and take note of the result value. For example, let’s say you are deploying a Dell PowerEdge M710 8-core server with Intel x5550 2.67GHz processors (2670 Hertz); the SPECint_rate2006 results value is 240.
- Added Megacycle Multiplication Factor – this works exactly like the IOPS Multiplication Feature does and was added as a result of RIM providing E2010 guidance on megacycle impact due to Blackberry devices.
- Active/Active user distribution scenarios. Yes, really! An Active/Active user distribution architecture has the user population dispersed across both datacenters (usually evenly) with each datacenter being the primary datacenter for its specific user population. In the event of a failure, the user population can be activated in the secondary datacenter (either via cross-datacenter single database *over or via full datacenter activation).
- Added a new worksheet/section that documents the Activation Scenarios for DAG deployments.
- Added error reporting validation logic if HA solution results in greater than 16 servers in a DAG to not show any results, since the design is invalid.
- Dumpster size calculations have been optimized as calendar versioning storage has been reduced from 5.8% impact to 3% impact in SP1.
- Fixed total number of databases/server calculation to deal with Active/Active (Single DAG) scenario correctly with respect to dedicated DR servers
- Fixed storage design disk calculations formulas for Active/Active (Single DAG) scenario, i.e., don’t recommend JBOD in scenario where only single copy is deployed (e.g., lagged copy deployed in secondary datacenter without dedicated hardware)
- Fixed Number of Active Mailbox Servers in DC2 calculation to not double count lagged copies when deploying Active/Active (Single DAG) scenario and deploying lagged copy in both Primary and Secondary Datacenters
- Fixed # of Target Lagged Copy Log Stream calculations to not double count lagged copies when deploying Active/Active (Single DAG) scenario and deploying lagged copy in both Primary and Secondary Datacenters
- Fixed second DAG Member Layout Table to show number of servers for both Active/Active scenarios
To get the detailed instructions on how to use it, read Exchange 2010 Mailbox Server Role Requirements Calculator.
To download the tool itself, click here.
OK, this is not exactly new, it has been released a couple of weeks ago, but since I’ve been extremelly busy lately, I didn’t have the opportunity to blog about it earlier: Update Rollup 1 for Exchange Server 2007 Service Pack 3 was released and is available to download.
Update Rollup 1 for Exchange Server 2007 Service Pack 3 (SP3) resolves issues that were found in Exchange Server 2007 SP3 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP3 customers.
For a list of changes that are included in this update rollup, see KB2279665.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM), Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2).
For a list of update rollups applicable to Exchange Server 2007 RTM , Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2), refer to the Knowledge Base article KB937052.
For all of you technical geeks that want to know every single detail behind an Exchange implementation, this is must-read document: Exchange Server Active Directory Schema Changes Reference, September 2010.
This download includes the Exchange Server Active Directory Schema Reference, which provides information about the changes that Microsoft Exchange Server makes to the Active Directory schema when it is installed. The Exchange Server Active Directory Schema Changes Reference includes changes made by Exchange Server 2010 SP1, Exchange Server 2010, Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007, and Exchange Server 2003.