Author Archive

Update Rollup 5 for Exchange Server 2010 Service Pack 1 (KB 2582113)

Posted by on Wednesday, 24 August, 2011
Date Published: 23/8/2011

Microsoft has released the following update rollup for Exchange Server 2010 SP1:

Update Rollup 5 for Exchange Server 2010 SP1 (KB2582113) Download the rollup here.

This update rollup is highly recommended for all Exchange Server 2010 customers.

For a list of changes that are included in this update rollup, see KB2582113.

 

Here is a list of the fixes included in update rollup 5 for Exchange 2010 SP1:

  • 2275156 (http://support.microsoft.com/kb/2275156/ ) The inline
    contents disposition is removed when you send a “Content-Disposition: inline”
    email message by using EWS in an Exchange Server 2010 environment
  • 2499044 (http://support.microsoft.com/kb/2499044/ ) You cannot save
    attachments in an email message by using OWA if the subject line contains
    special characters in an Exchange Server 2010 environment
  • 2509306 (http://support.microsoft.com/kb/2509306/ ) Journal reports
    are expired or lost when the Microsoft Exchange Transport service is restarted
    in an Exchange Server 2010 environment
  • 2514766 (http://support.microsoft.com/kb/2514766/ ) A RBAC role
    assignee can unexpectedly run the Add-ADPermission command on an Exchange Server
    2010 server that is outside the role assignment scope
  • 2529715 (http://support.microsoft.com/kb/2529715/ ) Slow network or
    replication issues after you change the number of virus scanning API threads in
    Microsoft Exchange Server 2010
  • 2536704 (http://support.microsoft.com/kb/2536704/ ) Mailbox users who
    are migrated by using ILM 2007 cannot use the Options menu in OWA in an Exchange
    Server 2010 environment
  • 2537094 (http://support.microsoft.com/kb/2537094/ ) French
    translation errors occur when you edit a response to a meeting request by using
    OWA in an Exchange Server 2010 SP1 environment
  • 2554604 (http://support.microsoft.com/kb/2554604/ ) A RBAC role
    assignee can unexpectedly manage certificates that are outside the role
    assignment scope in an Exchange Server 2010 environment
  • 2555800 (http://support.microsoft.com/kb/2555800/ ) You cannot use
    the GetItem operation in EWS to retrieve properties of an email message in an
    Exchange Server 2010 environment
  • 2555850 (http://support.microsoft.com/kb/2555850/ ) You cannot
    delete a mailbox folder that starts with a special character in its name by
    using Outlook in an Exchange Server 2010 environment
  • 2556096 (http://support.microsoft.com/kb/2556096/ ) The columns in
    the .csv logging file are not lined up correctly when you perform a discovery
    search on a mailbox in an Exchange Server 2010 environment
  • 2556107 (http://support.microsoft.com/kb/2556107/ ) The columns in
    the .csv logging file are not lined up correctly when you perform a discovery
    search on a mailbox in an Exchange Server 2010 environment
  • 2556133 (http://support.microsoft.com/kb/2556133/ ) A device that
    uses Exchange ActiveSync cannot access mailboxes in an Exchange Server 2010
    environment
  • 2556156 (http://support.microsoft.com/kb/2556156/ ) Extra.exe crashes
    when it performs RPC activity checks against an Exchange Server 2010 server
  • 2556352 (http://support.microsoft.com/kb/2556352/ ) “ChangeKey is
    required for this operation” error message in Outlook for Mac 2011 in an
    Exchange Server 2010 environment
  • 2556407 (http://support.microsoft.com/kb/2556407/ ) Certain
    client-only message rules do not take effect on email messages that are saved as
    drafts in an Exchange Server 2010 environment
  • 2559926 (http://support.microsoft.com/kb/2559926/ ) “There are no
    items to show in this view.” error message when you try to view a folder by
    using Outlook in an Exchange Server 2010 environment
  • 2572958 (http://support.microsoft.com/kb/2572958/ ) The
    “Test-OutlookConnectivity -Protocol HTTP” command fails with an HTTP 401 error
    in an Exchange Server 2010 environment

Note to Forefront users:

If you don’t disable Forefront before installing a rollup or service pack, and enable afterwards, you run the risk of Exchange related services not starting. You can disable Forefront by going to a command prompt and navigating to the Forefront directory and running FSCUtility /disable. To enable Forefront after installation of a UR or SP, run FSCUtility /enable.

An Update on Exchange Server 2010 SP1 Rollup Update 4

Posted by on Wednesday, 3 August, 2011

Microsoft has published this article to give you an update about Exchange 2010 SP1 Rollup 4.

————————————————————————————————–

The Exchange Sustained Engineering team recently made the decision to recall
the June 22, 2011 release of Exchange 2010 SP1 Rollup 4. This was not an action
we took lightly and we understand how disruptive this was to customers. We would
like to provide you with some details that will give you a deeper understanding
of what actually happened and, more importantly, what improvements we are making
to prevent this in the future.

 

     

    Q: What actually triggered the recall?

    A: While fixing a bug that prevented deleted public folders from being
    recovered, we exposed an untested set of conditions with the Outlook client.
    When moving or copying a folder, Outlook passes a flag on a remote procedure
    call that instructs the Information Store to open deleted items which haven’t
    been purged. Our fix inadvertently caused the RPC to skip all content that
    wasn’t marked for deletion because we were not expecting this flag on the call
    from Outlook on the copy and move operations.

       

      Q: Why didn’t you test this scenario?

      A: The short answer is we thought we did. We didn’t realize we missed a key
      interaction between Exchange and Outlook. The Exchange team has well over
      100,000 automated tests that we use to validate our product before we ship it.
      With the richness and number of scenarios and behaviors that Exchange supports,
      automated testing is the only scalable solution. We execute these tests in
      varying scenarios and conditions repeatedly before we release the software to
      our customers. We also supplement these tests with manual validation where
      necessary. The downside of our tests is that they primarily exercise the
      interfaces we expose and are designed around our specifications. They do test
      positive and negative conditions to catch unexpected behavior and we did execute
      numerous folder copy and move tests against the modified code which all passed.
      What we did not realize is that our tests were not emulating the procedure call
      as executed by Outlook.

         

        Q: Exchange has been around a while, why did this happen
        now?

        A: In Exchange 2010 we introduced a feature called RPC Client
        Access
        . This functionality is responsible for serving as the MAPI endpoint for
        Outlook clients. It allowed us to abstract client connections away from the
        Information Store (on Mailbox servers) and cause all Outlook clients to connect
        to the RPC Client Access service.

         

        As part of our investigation, we discovered that there was some specific code
        added to the Exchange 2003 Information Store to handle the procedure call from
        Outlook using the extra flag. This code was also carried forward into Exchange
        2007. But when the Exchange team added the RPC Client Access service to Exchange
        2010, that code was not incorporated into the RPC Client Access service because
        it was mistakenly believed to be legacy Outlook behavior that was no longer
        required. That, unfortunately, turned out not to be the case. The fact that we
        were not allowing a deleted public folder to be recovered was masking this new
        bug completely.

           

          Q: Are there other similar issues lurking in RPC Client
          Access?

          A: We do not believe so. The RPC Client Access functionality has been
          well-tested at scale and proven to be reliable for the millions of mailboxes
          hosted in on-premises deployment and in our own Office 365 and Live@EDU
          services.

             

            Q: What are you doing to prevent similar things from
            happening in the future?

            A: We have conducted a top-to-bottom review of the process we use to triage,
            develop and validate changes for Rollups and Service Packs and are making
            several improvements. We have changed the way we evaluate a customer requested
            fix to ensure that we more accurately identify the risk and usage scenarios that
            must be validated for a given fix. Recognizing the diversity of clients used to
            connect to Exchange, we are increasing our client driven test coverage to
            broaden the usage patterns validated prior to release. Most notably, we are
            working even closer with our counterparts in Outlook to use their automated test
            coverage against each of our releases as well. We are also looking to increase
            coverage for other clients as well.

            ————————————————————————————————–

            Update Rollup 4 (UR4) for Exchange Server 2010 SP1 removed from downloads

            Posted by on Wednesday, 20 July, 2011

            Microsoft has discovered an issue impacting some customers who have installed
            Exchange 2010 SP1 RU4 into their Exchange environment and as a result have
            removed SP1 RU4 from Download Center and recommend customers do not proceed with
            any planned deployments of SP1 RU4.

             

            A small number of customers have reported when the Outlook client is used to
            move or copy a folder that subfolders and content for the moved folder are
            deleted. After investigation we have determined that the folder and item
            contents do not appear in the destination folder as expected but may be
            recovered from the Recoverable Items folder (what was previously known as
            Dumpster in older versions of Exchange) from the original folder. This behavior
            occurs due to a customer requested change in SP1 RU4 which allowed deleted
            Public Folders to be recovered. Outlook and Exchange are not correctly
            processing the folder move and copy operations causing the folder contents to
            appear to be deleted. OWA and Exchange Web Services clients are not affected by
            this change and process the folder move or copy actions correctly.

             

            Microsoft will be providing a fix in Exchange 2010 SP1 RU5, scheduled for release in
            August, which prevents the content loss in the target location during the
            move/copy process. In addition, we are also working with the Outlook development
            team to examine their code for proper behavior and identify if a fix is
            necessary from the client. If you have already deployed SP1 RU4, Microsoft recommend
            obtaining an Interim Update that resolves this issue.

             

            If you are a customer seeing this issue or would like to receive the Interim
            Update, please contact Microsoft Customer Support.  When contacting Microsoft Customer Support, you can
            reference KB 2581545 (please note that this article will be available at a later
            date on support.microsoft.com).  When installing the Interim Update, you need to
            install this on all Client Access and Mailbox servers that have SP1 RU4
            installed.

            Update Rollup 4 (UR4) for Exchange Server 2010 SP1 released

            Posted by on Wednesday, 22 June, 2011

            Microsoft has released the following update rollup for Exchange Server 2010:

            • Update Rollup 4 for Exchange Server 2010 SP1 (2509910)

            If you’re running Exchange Server 2010 SP1, you need to apply Update Rollup 4 for Exchange 2010 to address the issues listed below.

            Remember, you only need to download the latest update for the version of Exchange that you’re running.

            Here is a list of the fixes included in update rollup 4:

            1. 2537099 “80040154” error message when you try to configure external Client Access namespaces on an Exchange Server 2010 server
            2. 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
            3. 2536517 The Microsoft Exchange RPC Client Access service crashes intermittently on an Exchange Server 2010 server
            4. 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
            5. 2535648 The EMC takes a long time to open in an Exchange Server 2010 environment
            6. 2535130 Performance in Outlook or in OWA decreases when you use IMAP4 to access the contacts folder in an Exchange Server 2010 environment
            7. 2535105 There is no option to disable the Availability service in an Exchange Server 2010 environment
            8. 2533543 Event ID 2153 is logged on each database availability group member in an Exchange Server 2010 environment
            9. 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
            10. 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
            11. 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
            12. 2518850 You cannot receive email messages on a mobile phone by using ActiveSync in an Exchange Server 2010 environment
            13. 2517088 Public folder conflict resolution does not work as usual in an Exchange Server 2010 environment
            14. 2515259 “The items could not be copied.” error message when you run the Get-MailboxSearch cmdlet in an Exchange Server 2010 SP1 environment
            15. 2514709 Event ID 1001 after you successfully the install Exchange Server 2010 Unified Messaging server role
            16. 2514574 The Exchange RPC Client Access service crashes in an Exchange Server 2010 environment
            17. 2513723 The “New-MailboxImportRequest” cmdlet does not import all messages in a .pst file in the ANSI format in an Exchange Server 2010 environment
            18. 2512023 “GetUserOofSettings”, “SetUserOofSettings” and “GetUserAvailability” operations do not support Exchange Impersonation on the Exchange Server 2010 SP1 schema
            19. 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
            20. 2507463 You cannot move a mailbox that contains a corrupted Search Folder in an Exchange Server 2010 environment
            21. 2506820 The free/busy information does not display of a user whose mailbox is located on an Exchange Server 2003 server
            22. 2506049 The hierarchy of a new public folder database on an Exchange Server 2010 SP1 server is not replicated
            23. 2505968 The EdgeTransport.exe process crashes when you apply a rule that contains a bad email address in an Exchange Server 2010 environment
            24. 2504453 You cannot retrieve statistical information about a public folder by using the “Get-PublicFolderStatistics” cmdlet in an Exchange Server 2010 SP1 environment
            25. 2503337 Comments of your meeting response message is missing when you decline a meeting request in an Exchange Server 2010 environment
            26. 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
            27. 2500903 A space is missing in the subject line of a “Tentative” meeting response in an Exchange Server 2010 environment
            28. 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
            29. 2495167 You cannot recover a deleted public folder by using Outlook or MFCMAPI in an Exchange Server 2010 environment
            30. 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
            31. 2493393 You cannot use ECP to perform a wipe on a mobile phone in an Exchange Server 2010 SP1 environment
            32. 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
            33. 2491354 You cannot view the free/busy information of users in a mixed Exchange Server 2007 and Exchange Server 2010 environment
            34. 2490134 A deferred delivery email message is not delivered by using Outlook 2007 in online mode in an Exchange Server 2010 environment
            35. 2489964 An update enables range 0x-0x1F characters in the display name of an Exchange Server 2010 user account
            36. 2489938 The “Connect-ExchangeServer” function does not change the target Exchange server in Exchange Server 2010
            37. 2489130 A RBAC role assignee can unexpectedly change mailbox properties that are outside the management role group scope in an Exchange Server 2010 environment
            38. 2488643 Outlook downloads duplicated POP3 email messages in an Exchange Server 2010 environment
            39. 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
            40. 2477273 The DomainController parameter does not work when you use the “MoveMailbox.ps1” script to move mailboxes in an Exchange Server 2010 environment
            41. 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
            42. 2467619 A user who manages a distribution group cannot remove another user whose mailbox is disabled in an Exchange Server 2010 environment
            43. 2465292 “MAPI_E_FAILONEPROVIDER (0x8004011D)” error message when you access an Exchange Server 2010 mailbox by using a MAPI application
            44. 2446908 ESE event descriptions are missing in Event Viewer when the Eseutil utility is called on an Exchange Server 2010 SP1 server
            45. 2394554 An email message is not delivered if it contains unsupported encoded characters in the subject line in an Exchange Server 2010 environment
            46. 2491951 You cannot install Exchange Server 2010 SP1 if the NetBIOS domain name of the domain controller contains an ampersand (&) character
            47. 2507066 Administrator audit logging is disabled unexpectedly during an Exchange Server 2010 SP1 installation

            Download the rollup here.

            Note to Forefront users:

            If you don’t disable Forefront before installing a rollup or service pack, and enable afterwards, you run the risk of Exchange related services not starting. You can disable Forefront by going to a command prompt and navigating to the Forefront directory and running FSCUtility /disable. To enable Forefront after installation of a UR or SP, run FSCUtility /enable.

            Update!! – Exchange Server Deployment Assistant for Exchange 2007 and Office 365 Coexistence

            Posted by on Thursday, 28 April, 2011

            The Exchange Server Deployment Assistant has been enhanced to include support for configuring
            rich coexistence for organizations interested in maintaining some users
            on-premises with Exchange 2007 and some users hosted by Microsoft Office 365
            Beta for enterprises in the cloud. This scenario is in addition to the existing
            support for configuring rich coexistence between on-premises Exchange 2003
            organizations and Office 365 Beta. The coexistence information is only available
            in English at this time and additional rich coexistence support for Exchange
            2010 will be added the Deployment Assistant soon.

            Rich coexistence (“hybrid deployment”) offers organizations the ability to
            extend the feature-rich experience and administrative control they have with
            their existing on-premises Microsoft Exchange organization to the cloud. It
            provides the seamless look and feel of a single Exchange organization between an
            on-premises organization and a cloud-based organization. In addition,
            coexistence can serve as an intermediate step to moving completely to a
            cloud-based Exchange organization. This approach is different than the simple
            exchange migration (“cutover migration”) and staged Exchange migration options
            currently offered by Office 365 Beta outlined in E-Mail
            Migration Overview
            .

            http://technet.microsoft.com/en-us/exdeploy2010

            OpsMgr/SCOM 2007 R2 – AD Replication Monitoring Failed (fSMORoleOwner attribute)

            Posted by on Friday, 22 April, 2011

            We get a warning in OpsMgr/SCOM 2007 R2 from the Active Directory 2008 Management Pack. Active Directory is running fine but OpsMgr find something what seems like corruption.

            We get Warnings from all the Domain Controllers “Script Based Test Failed to Complete“. And event id 1000 are show in the “OperationManager” event log on the DC.

            Detail of an Warning:

            AD Replication Monitoring : encountered a runtime error.
            Failed to obtain the InfrastructureMaster using a well known GUID.
            The error returned was: ‘Failed to get the ‘fSMORoleOwner’ attribute from the object ‘LDAP://nlnbdcsrv01.more2know.local/<WKGUID=2fbac1870ade11d297c400c04fd8d5cd, DC=ForestDnsZones,DC=more2know,DC=local>’.
            The error returned was: ‘There is no such object on the server.’ (0x80072030)’ (0x80072030)

            If you read the warning, The real error is “There is no such object on the server”

            The problem is that the AD Attribute “fSMORoleOwner” for the infrastructureMaster is set to an Old DC. The value was “CN=NTDS Settings\0ADEL:b6bc57e7-dbbf-41e5-82d2-7bc4b166af3f,CN=<OLDServername>\0ADEL:ae94f589-9bd8-4ec3-af7f-54afaf662beb,CN=Servers,CN=<SiteName>,CN=Sites,CN=Configuration,DC=domain,DC=local”.
            It was referencing an old DC that was demote a long time ago. It was demoted a long time ago. These settings are in the partition ForestDnsZones and DomainDNSZones.

            We must have so change the value to the DN of the current Infrastructure Master. Microsoft has the seam error when you want to Run adprep /rodcprep. See. http://support.microsoft.com/kb/949257

            1. Find out what the correct DN of the Infrastructure Master

            1. Run Adsiedit.msc
            2. Connect to the server which hold the infrastructure Role
            3. Connect to CN=Configuration,DC=<domain>,DC=<suffix>.
            4. Expand CN=Sites -> CN=”Site of the IM” -> CN=Servers -> CN=”Infrasturcte Master”
            5. Open the Properties of CN=NTDS Settings
            6. Find DistinguishedName and copy the value


                 
             

            2. Change the ForestDnsZone fSMORoleOwner

            1. Run Adsiedit.msc
            2. Connect to the server which hold the infrastructure Role
            3. Connect to DC=ForestDnsZones,DC=<domain>,DC=<suffix>.
            4. Open the properties for the Infrastructure object.
            5. Check the fSMORoleOwner attribute.
            6. Specify an infrastructure role owner that is online for the partition. You can do this by manually modifying the fSMORoleOwner attribute on the object.

            The value is formatted like:

            CN=NTDS Settings,CN=<hostname>,CN=Servers,CN=<sitename>,CN=Sites, CN=Configuration,DC=domain,DC=local


            Connect to de Infrastructure Master (IM) and select ForestDnsZones


            Change the fSMORoleOwner

            3. Change the DomainDnsZone fSMORoleOwner

            1. Run Adsiedit.msc
            2. Connect to the server which hold the infrastructure Role
            3. Connect to DC=DomainDnsZones,DC=<domain>,DC=<suffix>.
            4. Open the properties for the Infrastructure object.
            5. Check the fSMORoleOwner attribute.
            6. Specify an infrastructure role owner that is online for the partition. You can do this by manually modifying the fSMORoleOwner attribute on the object.

              The value is formatted like:
              CN=NTDS Settings,CN=<hostname>,CN=Servers,CN=<sitename>,CN=Sites, CN=Configuration,DC=domain,DC=local

            !! Note. You need to connect to the DC that currently is the Infrastructure FSMO. If you connect to any other DC you will get a error message saying “000020Ae: svcErr:DSID-031524F1, problem 5003 (WILL_NOT_PERFORM), data 0

            Opsmgr/SCOM 2007 R2 – BUG DPM 2010 MP – Discovery failed – Eventid 21406

            Posted by on Friday, 22 April, 2011

            When you use Opsmgr to Monitor Data Protection Manager, and you find out that Opsmgr don’t discovery all the data from de DPM server.

            The first thing you should notice is that you don’t get any alerts or warnings from the DPM server.

            Issue: The DPM Discovery Failed.

            First always check if Opsmgr discover all the data from the DPM servers. You can see all dicoverd information if you go to monitoring and expand the Management Pack “Data Protection Manager”.
            By selecting “DPM Server State” you must see all the data from you DPM servers. If Discovery Fails you don’t see de DPM Servion, Number of protection Groups, ect.
            When you monitor the Operation Manager eventlog on the DPM Servers you will see Eventid 21406.

            Eventid 21406

            The process started at 13:03:17 failed to create System.Discovery.Data. Errors found in output:
             
            C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\8332\DPMDataDiscovery.vbs(274, 1) Microsoft VBScript runtime error: Object required: ‘root’
            Command executed: “C:\Windows\system32\cscript.exe” /nologo “DPMDataDiscovery.vbs” 0 {E776E9E1-CAAE-A72D-350D-C65CABF15D80} {28275A4B-D281-0E8B-C594-250955B2928B} “dpm servername”
            Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\8332\
            One or more workflows were affected by this.
             
            Workflow name: Microsoft.Windows.SystemCenterDPM2010.DPMDataDiscovery
            Instance name: “dpm servername”
            Instance ID: {28275A4B-D281-0E8B-C594-250955B2928B}
             

            The Problem is that you use an “&” string in a name of one of the protection Groups.
            Change the name of the protection Group where you have used an “&” symbol . Restart the “System Center Management” and you should see that the discovery success.

            Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

            Posted by on Saturday, 16 April, 2011

            The Exchange Team have been aware of a problem that impacts Exchange management tools on servers running Exchange 2010 on Windows Server 2008 SP2.

            Note: Windows 2008 R2 systems do not seem to be impacted.

            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

            The following events could be logged in the Application event log:

            • Event ID: 1023
              Source: .NET Runtime
              Event ID: 1023
              Level: Error
              Description: .NET Runtime version 2.0.50727.5653 – Fatal Execution Engine Error (000007FEF9216D36) (80131506)
            • Event ID: 1000
              Source: Application Error
              Level: Error
              Description: Faulting application PowerShell.exe, version 6.0.6002.18111, time stamp 0x4acfacc6, faulting module mscorwks.dll, version 2.0.50727.5653, time stamp 0x4d54a59c, exception code 0xc0000005, fault offset 0x00000000001d9e19, process id 0x%9, application start time 0x%10.

            While Microsoft is still investigating this problem, the failures seem to start after the .NET security update KB 2449742 (MS11-028) is installed. The only workaround that we have identified up to now is a removal of this security update.

            Warning: We Microsoft not recommend that you uninstall any security updates, but Microsoft are providing this information so that you can implement this procedure at your own discretion. Use this procedure at your own risk. Removing a security update could may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses.

            Exchange 2010 SP1 Database Integrity checking: New-MailboxRepairRequest

            Posted by on Thursday, 27 January, 2011

            Exchange 2010 SP1: Database Integrity checking

            Since the earliest versions of Exchange Server, the Information Store Integrity Checker
            (ISInteg) has offered Exchange administrators a way to check mailbox and public folder database integrity. ISInteg checks and fixes Exchange database errors that may prevent the database from mounting, prevent the user from logging on or from receiving, opening or deleting email. Curious to know what changes are coming to ISInteg in Exchange 2010 SP1? Let’s take a look.

            In Exchange 2010 SP1, ISInteg is no longer a standalone program.

            The functionality provided by the ISInteg tool has been rolled into two new Exchange Management Shell cmdlets:

            • New-MailboxRepairRequest
            • New-PublicFolderDatabaseRepairRequest

            Note: Like other Shell cmdlets, these are subject to Role-Based Access Control (RBAC) scoping restrictions. For details, see Understanding Management Role Scopes.

            Cool Features

            These new ISInteg cmdlets come with some cool new functionality!

            • The cmdlets work with the database mounted. It’s no longer required to unmount the database to perform an integrity check or fix database errors.
            • You can repair logical corruption at the mailbox level.
            • You can fix corrupt search folders.
            • You can fix the Provisional Fid.
            • You can fix Aggregate Counts.

            ISInteg can now work at the database or mailbox level

            How does it do that? Well, the new schema in Exchange 2010 effectively partitions the database by mailbox. So the top problems fixed by ISInteg are now mostly limited to the affected mailboxes only. Previous versions of ISInteg required the database to be offline while validation and fixing are in progress. In Exchange 2010 SP1, the ability to do these checks at the mailbox level removes the need to dismount the database. It is actually required to have ISInteg operate against an online database!

            New-MailboxRepairRequest

            The New-MailboxRepairRequest cmdlet detects and fixes the following types of mailbox corruptions:

            • Search folder corruptions (SearchFolder): Repair tasks now look for all folders named in ptagSearchBacklinks, ptagSearchFIDs, and ptagRecursiveSearchFIDs and verifies that each folder exists. If the folder no longer exists, then it will remove that folder from the list.
            • Aggregate counts on folders that aren’t reflecting correct values (AggregateCounts): Repair tasks tally all messages in a folder and keep a running total of various counts and sizes. Once the iteration is complete, it will verify the computed counts against the persisted counts on the Folders table record for the folder. If there is a discrepancy, it will update the persisted counts to reflect the computed counts.
            • Views on folders that aren’t returning correct contents (FolderView): Repair tasks will iterate over all views for a folder and for each one, bring the view fully up to date and then reconstruct a temp copy. If there is a discrepancy between the existing view and the contents of the temp table, it will delete the view so it can be rebuilt from scratch the next time it is requested.
            • Provisioned folders that are incorrectly pointing into unprovisioned parent folders (ProvisionedFolder): Repair tasks can fix Provisioned folders incorrectly pointing into unprovisioned parents or vice versa.

            Syntax

            New-MailboxRepairRequest -Mailbox <MailboxIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Archive <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

            New-MailboxRepairRequest -Database <DatabaseIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

            Parameters

            · Database, Mailbox and Archive: You can repair an entire mailbox database or a specified mailbox by specifying either the Database or the Mailbox parameter. You can’t use both. To repair the archive mailbox for the specified user, use the Archive switch.

            · CorruptionType: (at least 1 required) you are already familiar with, we discussed them above:

            • SearchFolder
            • AggregateCounts
            • ProvisionedFolder
            • FolderView

            You can run a repair task with multiple parameters if you separate them with a comma (as shown in the Examples section below).

            · DetectOnly: (Optional) The DetectOnly switch secifies that you want this command to report errors, but not fix them. You don’t have to specify a value with this switch.

            · Other Optional Parameters: This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable. For more information, type “get-help about_commonparameters”.

            New-PublicFolderDatabaseRepairRequest

            The New-PublicFolderDatabaseRepairRequest cmdlet detects and fixes Public Folder replication state problems.

            Syntax

            New-PublicFolderDatabaseRepairRequest -Database <DatabaseIdParameter> -CorruptionType <PublicFolderDatabaseCorruptionType[]> [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

            Parameters

            • Database: (required) Specifies the Public Folder database on which you will run this command. You can use one of the following values:
              • GUID of the database
              • Database name
            • CorruptionType: (required) Pretty easy, there’s only one value.
              • ReplState
            • DetectOnly: (optional) Specifies that you want this command to report errors, but not fix them. You don’t have to specify a value with this parameter.
            • Other Optional Parameters: This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable. For more information, type “get-help about_commonparameters”.

            Examples

            New-MailboxRepairRequest -Mailbox administrator@contoso.com -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

            New-MailboxRepairRequest -Mailbox administrator -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView -WhatIf

            New-PublicFolderDatabaseRepairRequest -Database PFD01 -CorruptionType ReplState -DetectOnly

            Some additional examples are provided in the cmdlet help. You can retrieve them using the following commands, or refer to New-MailboxRepairRequest and New-PublicFolderDatabaseRepairRequest cmdlet reference:

            Get-help New-MailboxRepairRequest -examples
            Get-help New-PublicFolderDatabaseRepairRequest -examples

            I recommend that you get to know the cmdlets by using the cmdlet reference docs, or by using the following commands to retrieve detailed help from the shell:

            Get-help New-MailboxRepairRequest -detailed (or -full)
            Get-help New-PublicFolderDatabaseRepairRequest -detailed (or -full)

            Event Reporting

            After submitting the Mailbox or Public Folder repair request, you can monitor its progress with the Event Viewer. That’s right, no more text logs to weed through. The events are logged under the MSExchangeIS Mailbox Store source.

            The following event IDs will be logged for repair requests:

            • 10047 A mailbox-level repair request started
            • 10064 A Public Folder repair request started
            • 10048 The repair request successfully completed.
            • 10050 The mailbox repair request task skipped a mailbox .
            • 10059 A database-level repair request started.
            • 10062 Corruption was detected.


            Figure 1: Mailbox or Public Folder database repair request events are logged in the Application event log

            Note: the repair events will only show up on the mailbox server where the mailbox or Public Folder is located.

            This is very important to remember. Just because you fired off a repair task on a mailbox server does not mean the events will show up on that server. The repair task will be run on the database where the mailbox itself is, and the events will be in the event log on that mailbox server and that server alone.

            Things to remember:

            • Only 1 active repair task is permitted to be running per server if the active task is a database level repair.
            • Only 100 mailbox level active repair tasks are permitted to be running at once per server.
            • There is no -Server parameter to do all databases or mailboxes on a server.
            • The repair task dies on database dismount or store stop/crash.
            • The only way to stop a repair is to stop the store or dismount the database.
            • Mailbox access will be disrupted for the mailbox that is being repaired.
            • Repair for a mailbox will skip a mailbox if it has been quarantined.
            • Repair will cause a move-mailbox operation to be delayed until the repair is completed.

            Update Rollup 5 for Exchange Server 2010 (KB2407113)

            Posted by on Tuesday, 18 January, 2011

            Microsoft has released the following update rollup for Exchange Server 2010:

            • Update Rollup 5 for Exchange Server 2010 (KB2407113)  Download the rollup here.

            This update rollup is highly recommended for all Exchange Server 2010 customers.

            For a list of changes that are included in this update rollup, see KB2407113.

            Here is a list of the fixes included in update rollup 5:

            1. 2266458 Setup cannot perform a mode:/uninstall on a HT role server since RU2 delivered MSFTE.msi

            Download the rollup here.  

            Note to Forefront users:

            If you don’t disable Forefront before installing a rollup or service pack, and enable afterwards, you run the risk of Exchange related services not starting. You can disable Forefront by going to a command prompt and navigating to the Forefront directory and running FSCUtility /disable. To enable Forefront after installation of a UR or SP, run FSCUtility /enable.