- Exchange 2010 (4)
- Exchange 2007 (0)
- Exchange 2003 (0)
- Exchange 2010 (3)
- Exchange 2007 (0)
- Exchange 2003 (0)
How-To
Exchange 2010
Exchange 2010 Update Rollup: What should you know about it?

Exchange 2010 Update Rollup 1 has released yesterday and it can be downloaded from here. UR1 is one of the component to support Blackberry service on Exchange 2010 and a prerequisites for it. Thus you may have to install it soon so what should you know before planning to install it on your Exchange 2010 servers?
Although all precaution points are mentioned in the KB article of UR, yet let me point out them here…
1. Microsoft Update and DAG
Microsoft Update cannot detect Update Rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG). You need to deploy UR manually on DAG members by switching over active databases to other members.
Refer Scott Schnoll’s guide on Installing Update Rollup 1 for Exchange 2010 on DAG Members.
2. Lack of Internet Connectivity
You may experience long installation times and you may receive the following message:
Creating Native images for .Net assemblies
This issue occurs because the Exchange server issues network requests to connect to http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crland look up the certificate revocation list at NGEN time for each assembly that it compiles to native code.
Because the Exchange server is not connected to the Internet, each request must wait to timeout before moving on.
Prevention Step: Turn off the Check for publisher’s certificate revocation option on the server that is being upgraded. Follow these steps:
In Windows Internet Explorer –> Tools –> Internet Options –> Advanced tab
In the Security section, uncheck or clear the box for below tow options
“Check for publisher’s certificate revocation”

It is considered safe to clear this security option in Internet Explorer if the computer is in a tightly controlled environment. After the setup has completed, turn on the Check for publisher’s certificate revocation option again.
3. Do you have Outlook Web Apps Customization?
When you apply an update rollup package, the update process will copy over the OWA files if it is necessary. If you have modified the Logon.aspx file or any other OWA file, the customizations will be overwritten to ensure that OWA is updated correctly.
Prevention Step: Always make a backup copy of any customized Outlook Web Apps files before you apply the update rollup.
After you apply the update rollup package, re-create Outlook Web Apps customization or restore from backup.
4. Do you have CAS-CAS Proxying deployed?
Apply the update rollup to the Internet-facing Client Access servers before you apply the update rollup to any non-Internet-facing Client Access servers.
5. Previous Interim Update (IU) Exists, Remove/Uninstall it.
Remove all interim updates for Exchange Server 2010 before you apply this update rollup.
6. Server Role Installation Order.
If you have CAS-CAS proxying configured in your environment, install Update Rollup on internet facing CAS server first. For other Exchange Server 2010 server roles, the order in which you apply the update rollup is not important.
Article Statistics: This page has been viewed 5657 times.

