From the Microsoft Exchange Team blog:

This update contains a number of customer-reported and internally found issues since the release of RU5. See KB 2608656: Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3′ for more details.

We would like to specifically call out the following fixes which are included in this release:

• DST Cadence Release for Dec 2011 – Exchange 2007
• 22656040 An Exchange Server 2007 Client Access server may respond slowly or stop responding when users try to synchronize the Exchange ActiveSync devices with their mailboxes
• 2498852 ”0×80041606″ error message when you perform a prefix search by using Outlook in online mode in an Exchange Server 2007 environment
• 22653334 The reseed process is unsuccessful on the SCR passive node when the circular logging feature is enabled in an Exchange Server 2007 environment
• 22617784 Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2007 environment
• 2289607 The week numbers displayed in OWA do not match the week numbers displayed in Outlook for English users and French users in an Exchange Server 2007 environment

Update Rollup 6 can be downloaded here.

Related posts:

• Serious Risk of Database Corruption with Exchange 2007 SP3 Update Rollup 3
• Update Rollup 3 for Exchange 2010 SP1 and Exchange 2007 SP3
• Exchange Server 2007 SP2 Update Rollup 2 Released
• Exchange Server 2007 SP1 Update Rollup 8 Released
• Exchange Server 2007 Update Rollup 6 (Critical)

This article Update Rollup 6 for Exchange 2007 SP3 Released is © 2012 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

To update the DAG members with new patches, update rollups or service packs, the update process should be managed to prevent all of the DAG members from being offline at the same time.

To do this you can move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.

This tutorial demonstrates how to update the servers in an Exchange Server 2010 Database Availability Group without causing downtime. Because this process differs depending on the version of Exchange Server 2010 you’re running I’ve covered each method here.

• Preparing an Exchange Server 2010 RTM DAG member for updates, or
• Preparing an Exchange Server 2010 SP1 DAG member for updates
• Stopping Conflicting Services
• Disabling Server Monitoring
• Updating the Server
• Verifying the Update
• Returning an Exchange Server 2010 RTM DAG member to production, or
• Returning an Exchange Server 2010 SP1 DAG member to production

For this tutorial Update Rollup 4 for Exchange Server 2010 is being installed.

Preparing an Exchange Server 2010 RTM DAG Member for Updates

The first step is to move active mailbox databases to another DAG member so that the server can be updated.

To see a list of mailbox databases and their current active server use the Get-MailboxDatabase cmdlet.

[PS] C:\>Get-MailboxDatabase

Name                           Server          Recovery        ReplicationType
----                           ------          --------        ---------------
Mailbox Database 02            EX1             False           Remote
Mailbox Database 01            EX2             False           Remote

In this example I want to apply updates to server EX1, and I can see that it currently hosts the active copy of Mailbox Database 02.

If your environment has a lot of DAG members and mailbox databases you can refine this query to only show active mailbox databases for a specific server.

[PS] C:\>Get-MailboxDatabase | where {$_.Server -eq "EX1"}

Name                           Server          Recovery        ReplicationType
----                           ------          --------        ---------------
Mailbox Database 02            EX1             False           Remote

Move the mailbox databases using the Move-ActiveMailboxDatabase cmdlet.

[PS] C:\>Move-ActiveMailboxDatabase "Mailbox Database 02" -ActivateOnServer EX2

Confirm
Are you sure you want to perform this action?
Moving mailbox database "Mailbox Database 02" from server "ex1.exchangeserverpro.local" to server
"EX2.exchangeserverpro.local".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y

Identity        ActiveServerAtS ActiveServerAtE Status     NumberOfLogsLost   RecoveryPoint MountStatus MountStatus
                tart            nd                                            Objective     AtMoveStart AtMoveEnd
--------        --------------- --------------- ------     ----------------   ------------- ----------- -----------
Mailbox Data... ex1             ex2             Succeeded  0                  14/09/2010... Mounted     Mounted

All of the mailbox databases are now active on server EX2.

[PS] C:\>Get-MailboxDatabase

Name                           Server          Recovery        ReplicationType
----                           ------          --------        ---------------
Mailbox Database 02            EX2             False           Remote
Mailbox Database 01            EX2             False           Remote

As another example, if there were multiple databases active on a server you can move all of them with a single command.

[PS] C:\>Get-MailboxDatabase | where {$_.Server -eq "EX1"} | Move-ActiveMailboxDatabase -ActivateOnServer EX2 -Confirm:$false

Identity        ActiveServerAtS ActiveServerAtE Status     NumberOfLogsLost   RecoveryPoint MountStatus MountStatus
                tart            nd                                            Objective     AtMoveStart AtMoveEnd
--------        --------------- --------------- ------     ----------------   ------------- ----------- -----------
Mailbox Data... ex1             ex2             Succeeded  0                  14/09/2010... Mounted     Mounted
Mailbox Data... ex1             ex2             Succeeded  0                  14/09/2010... Mounted     Mountede

Note the use of -Confirm:$false to avoid having to confirm each move. Use this option with caution.

After moving all active mailbox databases off the server that you are planning to update, the final preparation step is to block activation on the server to prevent it from automatically reactiving a database copy while you are performing maintenance.

First check the current activation policy on the server using Get-MailboxServer.

[PS] C:\>Get-MailboxServer EX1 | fl Name,DatabaseCopyAutoActivationPolicy

Name                             : EX1
DatabaseCopyAutoActivationPolicy : Unrestricted

Next, use Set-MailboxServer to block activation.

[PS] C:\>Set-MailboxServer EX1 -DatabaseCopyAutoActivationPolicy Blocked

Preparing an Exchange Server 2010 SP1 DAG Member for Updates

For Exchange 2010 with Service Pack 1 the process is a little easier thanks to some scripts provided by Microsoft. Open the Exchange Management Shell and navigate to the scripts folder on the Exchange server.

cd $exscripts

Next run the StartDagServerMaintenance.ps1 PowerShell script.

.\StartDagServerMaintenance.ps1 -serverName ho-ex2010-mb1

The script will automatically do the following tasks for you:

• Calls Suspend-MailboxDatabaseCopy on the database copies.
• Pauses the node in Failover Clustering so that it can not become the Primary Active Manager.
• Suspends database activation on each mailbox database.
• Sets the DatabaseCopyAutoActivationPolicy to Blocked on the server.
• Moves databases and cluster group off of the designated server.

Stopping Conflicting Services

If the mailbox server is running any Exchange-integrated services, such as antivirus software, these should be disabled prior to the update.

For example to disable Forefront use the FSUtility command.

C:\> fsutility /disable

Another example is Data Protection Manager 2010, which may be configured to perform Copy backups from passive database copies at frequent intervals through the day. Make sure these jobs are paused to prevent errors or conflicts from occuring.

Disabling Server Monitoring

If the DAG members are monitored using SCOM or a similar system then this should also be disabled or placed into maintenance mode.

This will prevent alarms from being raised as well as prevent any automatic remediation actions from being run by the monitoring agent that may cause the server updates to fail.

Updating the Server

Install the update following the deployment notes for that update type.

Update rollups come in the form of a .MSP file (Windows Installer Patch) that is applied to the server. Simply double-click the file or launch it from a command line window.

Service packs are a complete reissue of the Exchange Server setup files and are installed by running setup in upgrade mode, which can be run in either graphical or command line mode.

C:\> setup /m:upgrade

Both update rollups and service packs can take some time to install, so plan a large window of time for these updates.

Verifying the Update

After the update has completed, and if necessary the server rebooted, you should check the server’s health before placing it back into production in the CAS array.

Event Logs – look for error or warning events that have started since the update was applied.

Setup Logs – service packs write a complete setup log file to C:\ExchangeSetupLogs

Services – check the Exchange services are running (or at least those that you expect to be running, some such as IMAP and POP will be stopped if you have not explicitly enabled them)

[PS] C:\>Get-Service *exchange*

Status   Name               DisplayName
------   ----               -----------
Running  MSExchangeADTop... Microsoft Exchange Active Directory...
Running  MSExchangeIS       Microsoft Exchange Information Store
Running  MSExchangeMailb... Microsoft Exchange Mailbox Assistants
Running  MSExchangeMailS... Microsoft Exchange Mail Submission
Stopped  MSExchangeMonit... Microsoft Exchange Monitoring
Running  MSExchangeRepl     Microsoft Exchange Replication
Running  MSExchangeRPC      Microsoft Exchange RPC Client Access
Running  MSExchangeSA       Microsoft Exchange System Attendant
Running  MSExchangeSearch   Microsoft Exchange Search Indexer
Running  MSExchangeServi... Microsoft Exchange Service Host
Running  MSExchangeThrot... Microsoft Exchange Throttling
Running  MSExchangeTrans... Microsoft Exchange Transport Log Se...
Running  msftesql-Exchange  Microsoft Search  (Exchange)
Running  vmickvpexchange    Hyper-V Data Exchange Service
Stopped  wsbexchange        Microsoft Exchange Server Extension...

Returning an Exchange Server 2010 RTM DAG Member to Production

If the update was successful and the server healthy then it can be placed back into production.

Re-enable services such as Forefront Protection for Exchange.

C:\> fsutility /enable

Re-enable monitoring agents and alarms for the server.

Set the server’s activation policy back to its original setting.

[PS] C:\>Set-MailboxServer EX1 -DatabaseCopyAutoActivationPolicy Unrestricted

At this stage you might move all of the active mailbox databases to the server that was just updated so that you can update the other servers in the DAG. After all of the DAG members have been updated it is likely that mailbox databases will be active on servers that are not their first activation preference.

For Exchange Server 2010 RTM you can view the activation preferences for each database, and manually move active mailbox databases to their preferred server.

[PS] C:\>Get-MailboxDatabase | fl name,activationpreference

Name                 : Mailbox Database 02
ActivationPreference : {[EX2, 1], [EX1, 2]}

Name                 : Mailbox Database 01
ActivationPreference : {[EX1, 1], [EX2, 2]}

[PS] C:\>Move-ActiveMailboxDatabase "Mailbox Database 01" -ActivateOnServer EX1

Confirm
Are you sure you want to perform this action?
Moving mailbox database "Mailbox Database 01" from server "EX2.exchangeserverpro.local" to server
"ex1.exchangeserverpro.local".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y

Identity        ActiveServerAtS ActiveServerAtE Status     NumberOfLogsLost   RecoveryPoint MountStatus MountStatus
                tart            nd                                            Objective     AtMoveStart AtMoveEnd
--------        --------------- --------------- ------     ----------------   ------------- ----------- -----------
Mailbox Data... ex2             ex1             Succeeded  0                  14/09/2010... Mounted     Mounted

Returning an Exchange Server 2010 RTM DAG Member to Production

Once again Exchange 2010 with Service Pack 1 makes this task easier thanks to a script provided by Microsoft. Open the Exchange Management Shell and navigate to the scripts folder on the Exchange server.

cd $exscripts

Next run the StopDagServerMaintenance.ps1 PowerShell script.

.\StopDagServerMaintenance.ps1 -serverName ho-ex2010-mb1

The script will automatically reverse each of the actions made by StartDagServerMaintenance.ps1 except that it will not move active mailbox databases back to the server.

To move the active mailbox databases you can continue to go to each mailbox server in the DAG and run StartDagServerMaintenance.ps1 and perform your updates. When all of the servers have been updated you can rebalance the DAG automatically using a script from Microsoft which is demonstrated here.

Related posts:

• Exchange 2010: Are Passive Database Copies Included in Backups of DAG Members?
• Exchange Recovery: Failed DAG Member in Exchange Server 2010
• How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010
• Exchange Server 2010 Database Availability Group Installation Step by Step
• Upgrading to Exchange Server 2010 Service Pack 2

This article How to Install Updates on Exchange Server 2010 Database Availability Groups is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server Pro reader Jens Jensen reported the following problem after installing Update Rollup 4 for Exchange Server 2010 SP1.

After installing the update, I cannot copy folder structures in Public Folders. When I copy a folder with subfolders, only the top folder is copied.

Same problem occurs if I move a folder structure from a Public folder to a mailbox or to another piblic folder. The top folder and messages are moved, but all subfolders and content is not moved, just deleted…

I’ve tested this scenario in my own Exchange 2010 lab and sure enough, after installing UR4 and copying a Public Folder to a new location in the Public Folder tree only the parent folder is copied, none of the sub-folders are copied as well.

After removing UR4 from the Mailbox server hosting the public folder database and repeating the same copy operation it copied both the parent folder and all sub-folders.

Jens has also left a comment on the Microsoft Exchange Team blog about this issue in the last hour or so and hopefully we’ll see a response soon.

Update: 1st July 2011

The Microsoft Exchange team has provided an update on the issue:

In SP1 RU4 we addressed the issue where you could not recover deleted public folders from dumpster. However, Outlook incorrectly passes a flag that indicates the item has been deleted when it has not. As a result, when you perform a copy or move in the manner Jens described, the sub-folders are deleted. As mentioned previously, you can recover these deleted folders from dumpster. We’ve contacted the Outlook team to assist in further diagnosis of the issue and to help us determine the right vehicle for a fix, we’ll provide more details soon.

Update: 6th July 2011

The bug affecting UR4 and Outlook seems to be impacting more than just public folder interaction. Another commentor, Rob, on the Microsoft Exchange Team blog reports the following:

Similarly to the Public Folders issue, after installing RU4 on ExSrvr2010, when a Folder is copied from a user mailbox to a PST, only the folder itself survives the copy, all messages are deleted. Singular or groups of messages will copy OK, but not a folder with messages. Tested (and failed) with both Outlook 2007 and 2010.

Related posts:

• How to Install Updates on Exchange Server 2010 Database Availability Groups
• Poll: Do You Still Use Public Folders in Your Exchange Environment?
• How to Remove an Exchange 2010 Public Folder Database
• Exchange 2010 FAQ: Can I Access Public Folders Using IMAP?
• Exchange Server 2010 Service Pack 2 Announced

This article Risk of Data Loss After Installing Update Rollup 4 for Exchange 2010 SP1 is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

With SP2, the following new features and capabilities will be included:

• Outlook Web App (OWA) Mini: A browse-only version of OWA designed for low bandwidth and resolution devices. Based on the existing Exchange 2010 SP1 OWA infrastructure, this feature provides a simple text based interface to navigate the user’s mailbox and access to the global address list from a plurality of mobile devices.
• Cross-Site Silent Redirection for Outlook Web App: With Service Pack 2, you will have the ability to enable silent redirection when CAS must redirect an OWA request to CAS infrastructure located in another Active Directory site.  Silent redirection can also provide a single sign-on experience when Forms-Based Authentication is used.
• Hybrid Configuration Wizard: Organizations can choose to deploy a hybrid scenario where some mailboxes are on-premises and some are in Exchange Online with Microsoft Office 365. Hybrid deployments may be needed for migrations taking place over weeks, months or indefinite timeframes. This wizard helps simplify the configuration of Exchange sharing features, like: calendar and free/busy sharing, secure mailflow, mailbox moves, as well as online archive.
• Address Book Policies: Allows organizations to segment their address books into smaller scoped subsets of users providing a more refined user experience than the previous manual configuration approach. We also blogged about this new feature recently in GAL Segmentation, Exchange Server 2010 and Address Book Policies.
• Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 2 will also be contained within SP2. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

One thing to note is that SP2 will require an Active Directory schema update.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We’ve heard the feedback loud and clear from our customers on multiple occasions regarding delays that can be caused to deployment as a result of needing to update your schema and as such with the release of Exchange 2010 SP2 are communicating the required changes ahead of release in order to assist our customers with planning their upgrade path ahead of time.

This is a service pack I know many customers will be looking forward to.

Related posts:

• Exchange Server 2010 Service Pack 2
• Upgrading to Exchange Server 2010 Service Pack 2
• Initialization Failed: The Operation Couldn’t Be Completed Because a Change Occurred in the Remote Forest
• Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade
• How to Install Updates on Exchange Server 2010 Database Availability Groups

This article Exchange Server 2010 Service Pack 2 Announced is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

The symptoms of the problem are:

• Exchange Management Shell does not start
• Exchange Management Console does not start
• There might be a crash in Exchange Mailbox Replication Service (it is not clear yet if this is related)
• Event Viewer might have trouble opening

This comes after problems in recent weeks with the update rollups for Exchange 2007 SP3 and Exchange 2010 SP1.

In discussing these recent dramas with other Exchange administrators it is clear that after a long run of trouble-free updates we’ve sadly returned to the days of thorough testing and a “wait and see” approach to installing updates on Exchange servers.

Related posts:

• How to Install Updates on Exchange Server 2010 Database Availability Groups
• Risk of Data Loss After Installing Update Rollup 4 for Exchange 2010 SP1
• Exchange Server 2010 Service Pack 2 Announced
• Exchange Server 2010 SP1 Update Rollup 1 Released
• How to Install Updates on Exchange Server 2010 CAS Arrays

This article Exchange Server 2010 Customers Warned of Another Bad Microsoft Update is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Original post continues below.

Microsoft has announced that a small number of customers running Exchange Server 2007 SP3 who have upgraded to Update Rollup 3 (UR3) have experienced a database corruption issue.

As a result of this issue they have removed Update Rollup 3 from the Microsoft website and are advising all customers who have deployed UR3 already to uninstall it.

While only a small number of customers have been affected to date, we believe the risk is significant enough that we are recommending all customers to uninstall Exchange 2007 SP3 RU3 on all Mailbox Servers and Transport servers. Uninstalling the rollup will revert the system back to the previously installed version. We have also removed the Exchange 2007 SP3 RU3 download from the Microsoft Download Center and from Microsoft Update until we are able to produce a new version of the rollup.

The removal steps are not trivial for customers running clustered mailbox servers.  The Microsoft Exchange team has provided some guidance in this blog post.

This issue comes hot on the heels of a problem with Exchange 2010 SP1 UR3 that also resulted in that update being removed from the Microsoft website.  As Michel De Rooij says:

This isn’t doing the product image any good guys.

Two incidents like this are not going to help customers quickly roll out new updates when they are released.  We’ve seen in the past how a bad service pack for an operating system shatters the confidence of system administrators and can take years to repair.

Related posts:

• Update Rollup 6 for Exchange 2007 SP3 Released
• Exchange Server 2007 SP2 Update Rollup 2 Released
• Exchange Server 2007 SP1 Update Rollup 8 Released
• Exchange Server 2007 Update Rollup 6 (Critical)
• Exchange 2007 OWA stops working with “reason=0” error

This article Serious Risk of Database Corruption with Exchange 2007 SP3 Update Rollup 3 is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

From the MS Exchange Team blog:

Earlier today the Exchange CXP team released Update Rollup 1 for Exchange Server 2010 SP1 to the Download Center. The release of the rollup via Microsoft Update will happen on October 12th.

This update includes new fixes for the following server roles:

• Client Access
• Mailbox
• Edge Server
• Hub Transport

In particular we would like to call out the following fixes which have been included in this release:

• 2028967 Event ID 3022 is logged and you still cannot replicate a public folder from one Exchange Server 2010 server to another
• 2251610 The email address of a user is updated unexpectedly after you run the Update-Recipient cmdlet on an Exchange Server 2010 server
• 978292 An IMAP4 client cannot send an email message that has a large attachment in a mixed Exchange Server 2010 and Exchange Server 2003 environment

If you are planning to install this update in your environment check out these two guides to help you ensure a smooth deployment.

• How to Install Updates on Exchange Server 2010 Database Availability Groups
• How to Install Updates on Exchange Server 2010 CAS Arrays

Link: Download Update Rollup 1 for Exchange Server 2010 Service Pack 1

Related posts:

• How to Install Updates on Exchange Server 2010 Database Availability Groups
• Risk of Data Loss After Installing Update Rollup 4 for Exchange 2010 SP1
• Exchange Server 2010 Service Pack 2 Announced
• Exchange Server 2010 Customers Warned of Another Bad Microsoft Update
• How to Install Updates on Exchange Server 2010 CAS Arrays

This article Exchange Server 2010 SP1 Update Rollup 1 Released is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

So when it comes time to update the CAS array members with patches, update rollups or service packs, the update process needs to be managed in a way that prevents all of the CAS array members from being offline at the same time.

Typically this means installing the updates to CAS array members one at a time, allowing each one to complete the update and (if necessary) reboot before updating the next member.

This tutorial demonstrates how to update a Client Access Server array without causing the entire array to go offline at once.  For this tutorial Update Rollup 4 for Exchange Server 2010 RTM is being installed.

Preparing the NLB Cluster for Updates

The first step is to remove the server that is about to be updated from the Network Load Balancing (NLB) cluster.

There are two ways to take a CAS array member our of the NLB cluster:

• Issue a Stop command to the server
• Issue a Drainstop command to the server

The difference between the two is that Stop will immediately stop the server regardless of who is currently connected to it, while Drainstop will put the server in a state where it will not accept new connections but will continue serving existing connections until they disconnect.

For urgent updates a Stop command may be necessary, but for planned maintenance a Drainstop has the least potential impact on active client connections to the CAS array.

To issue a Drainstop launch Network Load Balancing Manager, right-click on the desired server, choose Control Host and then Drainstop.

When the server has no more active connections it will be in a stopped state.

Right click the server and choose Properties.  Set the default state of the server to Stopped.  This will prevent it from automatically starting and accepting client connections after any reboots that the updates require, to allow you time to verify the updates were successful first before rejoining the NLB cluster.

Stop Conflicting Services

The Client Access Server role is often installed on the same server as the Hub Transport server role, even when deployed as a CAS array.

Hub Transport servers often run additional applications such as antivirus and anti-spam software that hooks into the Exchange Server services.  These can cause conflicts with Exchange Server updates, for example if a third party application tries to automatically restart a service that it depends on that has been stopped by the update process.

Forefront is one example of this, so for servers running Forefront Protection for Exchange those services can be stopped using FSUtility.

C:\> fsutility /disable

Disabling Monitoring

If the CAS array members are monitored using SCOM or another system this should also be disabled, or placed into maintenance mode before the update is performed.  This prevents unnecessary alarms in the monitoring system due to stopped services or server restarts, and also prevents the monitoring agent from trying to perform any automatic remediation such as restarting services.

Backing Up the Server

Some organizations will require an ad-hoc backup be run of at least one CAS array member before updates are applied.  Others will be happy to rely on the latest scheduled backup instead.  And some will even be satisfied that multiple CAS array members exist and so if a bad update puts one of them out of action there is no outage to end users, and the server can simply be manually reinstalled.

Updating the Server

Install the update following the procedure for that update type.

Update rollups come in the form of a .MSP file (Windows Installer Patch) that is applied to the server.  Simply double-click the file or launch it from a command line window.

Service packs are a complete reissue of the Exchange Server setup files and are installed by running setup in upgrade mode, which can be run in either graphical or command line mode.

C:\> setup /m:upgrade

Both update rollups and service packs can take some time to install, so plan a large window of time for these updates.

Verifying the Update

After the update has completed, and if necessary the server rebooted, you should check the server’s health before placing it back into production in the CAS array.

Event Logs – look for error or warning events that have started since the update was applied.

Setup Logs – service packs write a complete setup log file to C:\ExchangeSetupLogs

Services – check the Exchange services are running (or at least those that you expect to be running, some such as IMAP and POP will be stopped if you have not explicitly enabled them)

[PS] C:\>get-service *exchange*

Status   Name               DisplayName
------   ----               -----------
Running  MSExchangeAB       Microsoft Exchange Address Book
Running  MSExchangeADTop... Microsoft Exchange Active Directory...
Running  MSExchangeAntis... Microsoft Exchange Anti-spam Update
Running  MSExchangeEdgeSync Microsoft Exchange EdgeSync
Running  MSExchangeFBA      Microsoft Exchange Forms-Based Auth...
Running  MSExchangeFDS      Microsoft Exchange File Distribution
Stopped  MSExchangeImap4    Microsoft Exchange IMAP4
Running  MSExchangeMailb... Microsoft Exchange Mailbox Replication
Stopped  MSExchangeMonit... Microsoft Exchange Monitoring
Stopped  MSExchangePop3     Microsoft Exchange POP3
Running  MSExchangeProte... Microsoft Exchange Protected Servic...
Running  MSExchangeRPC      Microsoft Exchange RPC Client Access
Running  MSExchangeServi... Microsoft Exchange Service Host
Running  MSExchangeTrans... Microsoft Exchange Transport
Running  MSExchangeTrans... Microsoft Exchange Transport Log Se...
Stopped  msftesql-Exchange  Microsoft Search  (Exchange)
Running  vmickvpexchange    Hyper-V Data Exchange Service

Returning the Server to Production

If the update was successful and the server healthy then it can be placed back into production.

Re-enable services such as Forefront Protection for Exchange.

C:\> fsutility /enable

Start the server in the NLB cluster.

Set the NLB initial host state to Started.

And re-enable monitoring agents and alarms for the server.

After the first CAS array member has been successfully updated you can move on to the next one.

Related posts:

• Upgrading to Exchange Server 2010 Service Pack 2
• Exchange Server 2010 Service Pack 2
• How to Install Updates on Exchange Server 2010 Database Availability Groups
• TechEd Video: Load Balancing with Microsoft Exchange Server 2010
• Risk of Data Loss After Installing Update Rollup 4 for Exchange 2010 SP1

This article How to Install Updates on Exchange Server 2010 CAS Arrays is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

A full description of the update is available here or you can download the update files from here.

Related posts:

• Update Rollup 6 for Exchange 2007 SP3 Released
• Serious Risk of Database Corruption with Exchange 2007 SP3 Update Rollup 3
• Exchange Server 2007 SP1 Update Rollup 8 Released
• Exchange Server 2007 Update Rollup 6 (Critical)
• Exchange 2007 OWA stops working with “reason=0” error

This article Exchange Server 2007 SP2 Update Rollup 2 Released is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

The 32-bit and 64-bit update files are available for download here.

Related posts:

• Update Rollup 6 for Exchange 2007 SP3 Released
• Serious Risk of Database Corruption with Exchange 2007 SP3 Update Rollup 3
• Exchange Server 2007 SP2 Update Rollup 2 Released
• Exchange Server 2007 Update Rollup 6 (Critical)
• Exchange 2007 OWA stops working with “reason=0” error

This article Exchange Server 2007 SP1 Update Rollup 8 Released is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com