Tag Archives: Rollup

Exchange 2010 SP1 RU4 pulled

Posted on by
1

Just a quick notice that few minutes ago the Exchange Team pulled Exchange Server 2010 Service Pack 1 Rollup 4.

As reported earlier, there were potential data loss issues with this rollup when moving folders around in public folders or PST files using any version Outlook; Note that moving folders using OWA through Exchange Web Services works fine.

A fix for this issue will be incorporated in the RU5 update which is scheduled for August. So, like RU3 v2 v3 which took about a month to appear after the initial RU3 release was pulled, we’ll have to wait until August for RU5.

For those who already deployed RU4 an interim update has been made available that fixes this issue. The interim update can be obtained by contacting support.

 

Exchange 2007 SP3 Update Rollup 4

Posted on by
Reply

Today the Exchange Team released Rollup 4 for Exchange Server 2007 Service Pack 3 (KB2509911). This update raises Exchange 2007 version number to 8.3.192.1.

Here’s the big list of changes included in this rollup:

  • 2531208  You cannot synchronize a folder hierarchy by using Outlook for Mac 2011 in an Exchange Server 2007 SP3 environment
  • 2528437  EWS applications cannot connect to Exchange Server 2007 servers after you make changes on accepted domains
  • 2521063  You are incorrectly displayed as a meeting organizer after you synchronize the meeting by using your mobile device in an Exchange Server 2007 environment
  • 2517337  You cannot open a mailbox that has a “#” character in the primary SMTP email address by using OWA in an Exchange Server 2007 environment
  • 2515428  The MSExchangeMailboxAssistants.exe process crashes when the managed folder assistant tries to journal a message in an Exchange Server 2007 environment
  • 2508872  The W3WP.exe process in the Autodiscover application pool on the Exchange Server 2007 Client Access servers consumes excessive CPU resources
  • 2507374  “Cannot open this item” error message in Outlook online mode in an Exchange Server 2007 environment
  • 2506827  An UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2007 environment
  • 2502276  A meeting request series are deleted unexpectedly from the calendar in an Exchange Server 2007 environment
  • 2498924  “Could not connect to a directory server” error message when you click the last page button in the search results in Exchange Server 2007 OWA
  • 2498156  OLM/OLD incorrectly runs against databases in a RSG in an Exchange Server 2007 environment
  • 2496806  A mobile phone times out when you use ActiveSync to synchronize the calendar on the mobile phone with an Exchange Server 2007 mailbox
  • 2543879  A PDF attachment sent from a Mac Mail client does not display when you open the email message by using Outlook 2010 in an Exchange Server 2007 SP3 environment
  • 2491751  Spell checking does not function correctly in OWA when an S/MIME control is used and SSL Offloading is enabled in Exchange Server 2007
  • 2484147  “HTTP Error 400 Bad Request” error message when you use OWA to log on to a newly created Exchange Server 2007 mailbox
  • 2466220  Question mark (?) characters appear in the subject of a reply email message in an Exchange Server 2007 environment
  • 2223294  A new feature is available to disable the “No end date” check box in OWA when you create a recurring meeting item in an Exchange Server 2007 environment
  • 977906  You receive an error message when you run certain commands in the EMS on an Exchange Server 2007 server
  • 2495010  The EdgeTransport.exe process consumes 100% CPU usage on an Exchange Server 2010 Edge Transport server or an Exchange Server 2007 Edge Transport server
  • 2484817  A mailbox does not show in certain address lists after you run commands on an Exchange Server 2007 mailbox

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.

You can download Exchange 2007 SP3 Rollup 4 here.

Exchange 2010 SP1 Update Rollup 4 Issues

Posted on by
1

Be advised that in addition to earlier reports, there are not only data loss issues with Exchange 2010 SP1 Rollup 4 when moving folder structures from public folders to mailboxes or other public folders.  Apparantly, data loss can also occur when moving folder structures to PST files. In both cases, only the top folder and messages are moved, subfolders and their contents are not moved but deleted.

On the issue, Microsoft’s Ross Smith said the following:

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 – in the meantime please open a CSS case.

You can uninstall Rollup 4 from your Exchange servers to prevent potential data loss caused by these issues.

Note that Rollup 5 is scheduled for August, so you might start to wonder what will arrive first, RU5 or RU4v2.

Exchange 2010 SP1 Update Rollup 4

Posted on by
1

Update June, 29th: Reports of issues with PF after installing RU4 here (comments section). Exchange fellow Paul Cunningham reproduced a PF issue which can lead to data loss. More about this on his blog here. Once again I emphasize to properly test updates prior to implementing in production. Although I’m aware of possible budget constraints, not having a proper test environment in fact means you have no production environment.

Today the Exchange Team released Rollup 4 for Exchange Server 2010 Service Pack 1 (KB2509910). This update raises Exchange 2010 version number to 14.1.323.1.

After the rollup 3 debacle, I’d recommend to thoroughly test rollup 4 in a test and acceptance environment prior to implementing it in production.

Here’s the big list of changes included in this rollup:

  • 2537099  “80040154″ error message when you try to configure external Client Access namespaces on an Exchange Server 2010 server
  • 2536700  Outlook stops responding when you try to copy a folder to its subfolder by using Outlook in online mode in an Exchange Server 2010 SP1 environment
  • 2536517  The Microsoft Exchange RPC Client Access service crashes intermittently on an Exchange Server 2010 server
  • 2536494  It takes a long time to return results when you perform an Advanced Find search on a mailbox by using Outlook in online mode in an Exchange Server 2010 SP1 environment
  • 2535648  The EMC takes a long time to open in an Exchange Server 2010 environment
  • 2535130  Performance in Outlook or in OWA decreases when you use IMAP4 to access the contacts folder in an Exchange Server 2010 environment
  • 2535105  There is no option to disable the Availability service in an Exchange Server 2010 environment
  • 2533543  Event ID 2153 is logged on each database availability group member in an Exchange Server 2010 environment
  • 2533538  You cannot look up the free/busy information of a user who is located on an Exchange Server 2010 organization from another Exchange Server 2010 organization
  • 2533451  A RBAC role assignee can unexpectedly run the “Update-FileDistributionService” command on an Exchange Server 2010 server that is outside the role assignment scope
  • 2519359  “Changes to the rule cannot be saved.” error message when you try to create a reply rule by using Outlook in an Exchange Server 2010 environment
  • 2518850  You cannot receive email messages on a mobile phone by using ActiveSync in an Exchange Server 2010 environment
  • 2517088  Public folder conflict resolution does not work as usual in an Exchange Server 2010 environment
  • 2515259  “The items could not be copied.” error message when you run the Get-MailboxSearch cmdlet in an Exchange Server 2010 SP1 environment
  • 2514709  Event ID 1001 after you successfully the install Exchange Server 2010 Unified Messaging server role
  • 2514574  The Exchange RPC Client Access service crashes in an Exchange Server 2010 environment
  • 2513723  The “New-MailboxImportRequest” cmdlet does not import all messages in a .pst file in the ANSI format in an Exchange Server 2010 environment
  • 2512023  “GetUserOofSettings”, “SetUserOofSettings” and “GetUserAvailability” operations do not support Exchange Impersonation on the Exchange Server 2010 SP1 schema
  • 2511897  You cannot send an email message to a mailbox for a brief period when you move the mailbox by using online move in an Exchange Server 2010 environment
  • 2507463  You cannot move a mailbox that contains a corrupted Search Folder in an Exchange Server 2010 environment
  • 2506820  The free/busy information does not display of a user whose mailbox is located on an Exchange Server 2003 server
  • 2506049  The hierarchy of a new public folder database on an Exchange Server 2010 SP1 server is not replicated
  • 2505968  The EdgeTransport.exe process crashes when you apply a rule that contains a bad email address in an Exchange Server 2010 environment
  • 2504453  You cannot retrieve statistical information about a public folder by using the “Get-PublicFolderStatistics” cmdlet in an Exchange Server 2010 SP1 environment
  • 2503337  Comments of your meeting response message is missing when you decline a meeting request in an Exchange Server 2010 environment
  • 2501070  A RBAC role assignee can stop queue processing on an Exchange Server 2010 Hub Transport server or an Exchange Server 2010 Edge Transport server that is outside the role assignment scope
  • 2500903  A space is missing in the subject line of a “Tentative” meeting response in an Exchange Server 2010 environment
  • 2500648  “There are no items to show in this view.” error message when you try to view a folder in Outlook in an Exchange Server 2010 environment
  • 2495167  You cannot recover a deleted public folder by using Outlook or MFCMAPI in an Exchange Server 2010 environment
  • 2495010  The EdgeTransport.exe process consumes 100% CPU usage on an Exchange Server 2010 Edge Transport server or an Exchange Server 2007 Edge Transport server
  • 2493393  You cannot use ECP to perform a wipe on a mobile phone in an Exchange Server 2010 SP1 environment
  • 2492068  “The item cannot be saved to this folder.” error message when try to post an item to a mail-disabled public folder in an Exchange Server 2010 SP1 environment
  • 2491354  You cannot view the free/busy information of users in a mixed Exchange Server 2007 and Exchange Server 2010 environment
  • 2490134  A deferred delivery email message is not delivered by using Outlook 2007 in online mode in an Exchange Server 2010 environment
  • 2489964  An update enables range 0x-0x1F characters in the display name of an Exchange Server 2010 user account
  • 2489938  The “Connect-ExchangeServer” function does not change the target Exchange server in Exchange Server 2010
  • 2489130  A RBAC role assignee can unexpectedly change mailbox properties that are outside the management role group scope in an Exchange Server 2010 environment
  • 2488643  Outlook downloads duplicated POP3 email messages in an Exchange Server 2010 environment
  • 2479188  The iCal parts of an email message contain invalid entries when they are sent from an Exchange Server 2003 mailbox to an Exchange Server 2010 mailbox
  • 2477273  The DomainController parameter does not work when you use the “MoveMailbox.ps1″ script to move mailboxes in an Exchange Server 2010 environment
  • 2471964  A NDR is sent to the sender when you move an email message to a personal folder file in an Exchange Server 2010 SP1 or a later version environment
  • 2467619  A user who manages a distribution group cannot remove another user whose mailbox is disabled in an Exchange Server 2010 environment
  • 2465292  “MAPI_E_FAILONEPROVIDER (0x8004011D)” error message when you access an Exchange Server 2010 mailbox by using a MAPI application
  • 2446908  ESE event descriptions are missing in Event Viewer when the Eseutil utility is called on an Exchange Server 2010 SP1 server
  • 2394554  An email message is not delivered if it contains unsupported encoded characters in the subject line in an Exchange Server 2010 environment
  • 2491951  You cannot install Exchange Server 2010 SP1 if the NetBIOS domain name of the domain controller contains an ampersand (&) character
  • 2507066  Administrator audit logging is disabled unexpectedly during an Exchange Server 2010 SP1 installation

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

For the correct procedure on how to update a DAG and its members, check here.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.

You can download Exchange 2010 SP1 Rollup 4 here.

Forefront Protection for Exchange Rollup 3

Posted on by
Reply

Microsoft released Hotfix Rollup 3 for Forefront Protection for Exchange Server (KB2538719).

Here’s the list of fixes included in this rollup:

  1. Mail queues and sluggish Exchange/Outlook performance
  2. Increased “Available Disk Space” Health Point threshold to 250MB
  3. Error: The DNS Blocklist lookup domain blocklist.messaging.microsoft.com could not be contacted
  4. The Exchange Information store crashes with Forefront Protection for Exchange installed
  5. An attempted upgrade of Forefront Protection for Exchange fails with a “Registration Service Failed” error
  6. You receive Forefront Protection Health Notifications indicating a status of “Green to Green”
  7. Forefront generates a MaxDisabledWait error within 15 minutes after starting
  8. A MaxDisabledWait error occurs and Forefront Protection does not recover
  9. Forefront Protection doesn’t apply keyword filtering within hyperlink strings
  10. Forefront Protection for Exchange crashes while scanning a TAR file
  11. An engine update fails in Forefront Protection for Exchange
  12. Emails that are 90 MB or larger are being sent to the Forefront archive folder
  13. The Microsoft Forefront Server Protection Eventing Service will not start following an upgrade from a beta version of Forefront Protection for Exchange
  14. Forefront Protection for Exchange detects files as “Engine Error” when no engines have been enabled for scanning
  15. Messages quarantined due to engine error can now be delivered as complete email
  16. High CPU conditions in EdgeTransort.exe process result in crash
  17. You receive Forefront generated email notification that the Cloudmark engine or Worm list could not update
  18. Exchange email queues at startup following an abnormal shutdown

For more details on the fixes consult the related knowledge base article. You can request the hotfix rollup through the support center here.

Updating Exchange 2010 SP1 DAG Members

Posted on by
15

With all the (re-)releases of rollups, the question might rise on how to perform a proper up or downgrade of all DAG configuration members.

Basically, the procedure is straightforward and should be followed per DAG member:

  1. Appoint (next) DAG member;
  2. Move away all active copies on that DAG member;
  3. Prevent copies from activating on that DAG member;
  4. Perform maintenance, e.g. down or upgrade DAG member;
  5. Enable possible activation on that DAG member again;
  6. Optionally redistribute database copies.

Note that in a DAG configuration with 2 members, you need to be aware that during maintenance you have a temporary situation with no fail-over options. If that’s undesirable, consider implementing a 3rd DAG member.

To make the above procedure  easier and automated regarding moves and activation (un)blocking, additional scripts are available since SP1 for Exchange 2010. These scripts are located in the Scripts folder, below the Exchange installation folder. By default the location of the scripts will be C:\Program Files\Microsoft\Exchange Server\v14\Scripts.

Utilizing them, the procedure is quite easy as you can see below. Note that the example uses a DAG named DAG1 with nodes ex2010a and ex2010b as members. They both host 2 databases, ex2010mdb1 and ex2010mdb2; both host 1 active copy and a passive copy of the other database.

  1. Appoint (next) DAG member, e.g. ex2010a;
  2. Run StartDagServerMaintenance.ps1 targeting that DAG member, e.g.:
    .\StartDagServerMaintenance.ps1 –server ex2010a

    image
  3. Perform maintenance;
  4. Run StopDagServerMaintenance.ps1 targeting that DAG member, e.g.:
    .\StopDagServerMaintenance.ps1 –server ex2010a
  5. Repeat steps 2-3 for the other DAG member(s):image
  6. Optionally run RedistributeActiveDatabases.ps1 for the DAG, e.g.:
    .\RedistributeActiveDatabases.ps1 –DagName DAG1 –BalanceDBsByActivationPreference –Confirm:$false

    image

Exchange 2010 SP1 Rollup 3 v3

Posted on by
4

After pulling Rollup 3 for Exchange Server 2010 SP1 after an important Blackberry issue on March 15th, the Exchange team claim to have fixed the issue and and re-released the rollup. So, after re-releasing Exchange 2007 SP3 Rollup 3 after fixing potential store corruption issues, Exchange 2010 SP1 now also gets its own rollup re-release. Note that its officially a v3 release; I don’t know what happened to v2.

Exchange 2010 SP1 Rollup 3 v3 raises Exchange 2010′s version number to 14.1.289.7 (initial release was 14.1.289.3). The related knowledgebase article is kb2529939.

You can download Exchange 2010 SP1 Rollup3 v3 here.

Exchange 2007 SP3 RU3 potential database corruption (update)

Posted on by
1

Update: Exchange 2007 SP3 Rollup 3 has been re-released. Version 2 of the Rollup can be downloaded here. Rollup 3 version 2 raises Exchange 2007′s version number to 8.3.159.2 (initial release was 8.3.159.0). The related knowledgebase article is kb2530488.

Update: The related knowledgebase article kb2531163 can be found here.

A quick notice on a potential issue with Exchange 2007 SP3 and database corruption after installing Rollup 3. The issue may occurs in the following situations:

  • When transaction log replay is performed by the Replication Service as part of ensuring the passive database copy is up-to-date;
  • When a database is not cleanly shut down and recovery occurs.

Because of this, Rollup 3 for Exchange 2007 was pulled and you’re advised to uninstall Rollup 3 on Exchange 2007 Mailbox and Transport servers. For more information, consult the post on the Exchange Team’s blog here.

Note that the issue may affect all Mailbox servers, clustered or standalone, so you’re also advised to uninstall RU3 on standalone Mailbox servers. For those with the issue on CCR or SCC setups, it requires reseeding or restoring from backup so plan accordingly.

Looking at the issues with latest Rollups for Exchange 2010 and 2007, it gives to think about the quality control process or if the Exchange team’s priorities perhaps lay somewhere else (Office 365?).

Potential for database corruption as a result of installing Exchange 2007 SP3 RU3

Exchange 2010 SP1 RU3 pulled: Blackberry issue

Posted on by
1

For those looking for Exchange 2010 SP1 Rollup 3, you’re in for an unpleasant surprise. Today, Microsoft pulled the Rollup because of issues with Blackberry devices sending duplicate messages.

While Microsoft is working with RIM to identify and solve the issue, the advice is to wait for updates regarding this issue and meanwhile put RU3 implementations on hold. If you’ve already implemented RU3 and are seeing no issues, you can leave it installed.

More information regarding this issue on the (revised) EHLO page here.

Exchange 2010 SP1 Rollup 3 & Exchange 2007 Rollup 3

Posted on by
2

Today the Exchange Team released two Rollups, Rollup 3 for Exchange Server 2010 Service Pack 1 and Rollup 3 for Exchange Server 2007 SP3. No new Rollup for Exchange 2010 RTM.

The Exchange 2010 SP1 Rollup 3 (KB2492690) raises Exchange 2010′s version number to 14.1.289.3.

New fixes contained in this Rollup are:

  • 2009942 Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode
  • 2277649 You receive misleading information when you run the “New-TestCasConnectivityUser.ps1″ script on an Exchange Server 2010 server
  • 2398431 Using Pipelining in SMTP to check email addresses does not work correctly when you disable tarpitting functionality on a Receive connector in an Exchange Server 2010 environment
  • 2410571 A RBAC role assignee can unexpectedly change permissions of mailboxes that are outside the role assignment scope in an Exchange Server 2010 environment
  • 2417084 A public folder disappears from the Public Folder Favorites list of an Exchange Server 2010 mailbox
  • 2423754 The recipient response status is incorrect after you add another user to an occurrence of a meeting request in an Exchange Server 2010 environment
  • 2424801 The Microsoft Exchange Service Host service on an Exchange Server 2010 server crashes
  • 2426952 You cannot remove a mailbox database copy from a database on an Exchange Server 2010 server
  • 2432494 You cannot view the mailbox database copies that are hosted on certain Mailbox servers by using the Exchange Management Console after you install Exchange Server 2010 SP1
  • 2443688 Event ID 10003 and Event ID 4999 are logged when the EdgeTransport.exe process on an Exchange Server 2010 server crashes
  • 2445121 A memory leak occurs in the Microsoft.Exchange.Monitoring.exe process when you run the “Test-OwaConnectivity” cmdlet or the “Test-ActiveSyncConnectivity” cmdlet in the EMS on an Exchange Server 2010 server
  • 2447629 Event ID 4999 is logged when the Exchange Mail Submission Service crashes intermittently on an Exchange Server 2010 Mailbox server
  • 2451101 7BIT is not in quotation marks when you use the “FETCH (BODYSTRUCTURE)” command to request for a specific message in an Exchange Server 2010 environment
  • 2457304 You receive a synchronization failed email message when you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox
  • 2457688 Error message when you try to add an external email address to the safe sender list in OWA in an Exchange Server 2010 SP1 environment
  • 2457868 “HTTP Error 400 Bad Request” error message when you use OWA in Exchange Server 2010 SP1 to receive instant messages by using Internet Explorer 9
  • 2458522 Entries disappear from a junk email blocked list or a junk email safe list after you install Exchange Server 2010 SP1
  • 2458543 A memory leak occurs in the Exchange RPC Client Access service on Exchange Server 2010 servers
  • 2463798 Users may experience a decrease in performance in Outlook or in OWA when you use IMAP4 to access the calendar folder in an Exchange Server 2010 SP1 environment
  • 2463858 A request to join a distribution group does not contain the distribution group name in an Exchange Server 2010 SP1 environment
  • 2464564 You cannot change your password if the user name that you type in OWA is in UPN format when you enable Exchange Server 2010 SP1 Password Reset Tool
  • 2467565 You cannot install an update rollup for Exchange Server 2010 with a deployed GPO that defines a PowerShell execution policy for the server to be updated
  • 2468514 OWA 2010 removes Calendar links that you add into multiple calendar groups by using Outlook 2010 calendar
  • 2469341 Various issues occur after you forward a signed email message by using Outlook in online mode in an Exchange Server 2010 environment
  • 2476973 Event ID 2168 is logged when you try to back up Exchange data from a DAG in an Exchange Server 2010 SP1 environment
  • 2479227 A forwarding rule does not function and the EdgeTransport.exe process crashes on an Exchange Server 2010 server
  • 2479875 The Microsoft Exchange Mailbox Replication Service service crashes when you run the “New-MailboxImportRequest” cmdlet to import a .pst file into a mailbox in an Exchange Server 2010 environment
  • 2481283 Various issues occur after you use Outlook to sign and then forward an email message in an Exchange Server 2010 environment
  • 2482100 You cannot create or update an inbox rule that specifies the “NoResponseNecessary” value by using EWS in an Exchange Server 2010 environment
  • 2482103 It takes a long time to expand a distribution list by using EWS in an Exchange Server 2010 environment
  • 2482471 A content search fails in an IMAP client application that connects to an Exchange Server 2010 mailbox
  • 2484862 You cannot read an email message by using an IMAP client in an Exchange Server 2010 environment
  • 2487501 The body of an email message is empty when you try to use an IMAP client application to read it in an Exchange Server 2010 environment
  • 2487852 “You do not have sufficient permissions. This operation can only be performed by a manager of the group.” error message when you try to change the “ManagedBy” attribute in an Exchange Server 2010 SP1 environment
  • 2489602 The “Get-FederationInformation” cmdlet cannot query federation information from an external Exchange organization in an Exchange Server 2010 environment
  • 2489713 Exchange Server 2010 SP1 supports the remote archive feature after an update changes Outlook cookies name
  • 2489822 “The Mailbox you are trying to access isn’t currently available” error when you use OWA Premium to try to delete an item that is in a shared mailbox
  • 2494389 Unnecessary events are logged in the Application log when you run the “Test-EcpConnectivity” cmdlet in an Exchange Server 2010 environment
  • 2494798 Certain email messages cannot be downloaded when you log on to an Exchange Server 2010 mailbox by using an IMAP4 client application
  • 2497669 A meeting request cannot be opened after you disable the “Display sender’s name on messages” option in the EMC on an Exchange Server 2010 server
  • 2497682 The store.exe process crashes when you try to unmount an active copy of a mailbox database that is hosted by a mailbox server in an Exchange Server 2010 SP1 environment
  • 2506998 A call is disconnected when transferring the call from the main auto attendant to an auto attendant that has a different language configured in an Exchange Server 2010 environment

In other words, Outlook 2003 users rejoice – UDP notifications are back!

The team also released Rollup 3 for Exchange 2007 Service Pack 3 (KB2492691), raising the Exchange 2007 version number to 8.3.159.0. For a full list of changes consult the KB article.

You can download Exchange 2010 SP1 Rollup 3 here; Exchange 2007 SP3 Rollup 3 can be downloaded here.

Note that when running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enabling it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it by using fscutility /enable afterwards.

For those still unaware, update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but implement the latest rollup will suffice.