Exchange 2010 SP1 FAQ and Known Issues

Last week we released Exchange Server 2010 Service Pack 1. It has received some great feedback and reviews from customers, experts, analysts, and the Exchange community.

The starting point for SP1 setup/upgrade should be the What’s New in SP1, SP1 Release Notes, and Prerequisites docs. As with any new release, there are some frequently asked deployment questions, and known issues, or issues reported by some customers. You may not face these in your environment, but we’re posting these here along with some workarounds so you’re aware of them as you test and deploy SP1.

  1. Upgrade order

    The order of upgrade from Exchange 2010 RTM to SP1 hasn’t changed from what was done in Exchange 2007. Upgrade server roles in the following order:

    1. Client Access server
    2. Hub Transport server
    3. Unified Messaging server
    4. Mailbox server

    The Edge Transport server role can be upgraded at any time; however, we recommend upgrading Edge Transport either before all other server roles have been upgraded or after all other server roles have been upgraded. For more details, see Upgrade from Exchange 2010 RTM to Exchange 2010 SP1 in the documenation.

  2. Exchange 2010 SP1 Prerequisites

    Exchange 2010 SP1 requires the installation of 4-5 hotfixes, depending on the operating system – Windows Server 2008, or Windows Server 2008 R2. To install the Exchange 2010 SP1 administration tools on Windows 7 and Windows Vista, you requires 2 hotfixes.

    Note: Due to the shared code base for these updates, Windows Server 2008 and Windows Vista share the same updates. Similarly, Windows Server 2008 R2 and Windows 7 share the same updates. Make sure you select the x64 versions of each update to be installed on your Exchange 2010 servers.

    Update 2/11/2011: Windows 2008 R2 SP1 includes all the required hotfixes listed in this table — 979744, 983440, 979099, 982867 and 977020. If you’re installing Exchange 2010 SP1 on a server running Windows 2008 R2 SP1, you don’t need to install these hotfixes separately. For a complete list of all updates included in Windows 2008 R2 SP1, see Updates in Win7 and WS08R2 SP1.xls.

    Here’s a matrix of the updates required, including download locations and file names.

    Hotfix Download Windows Server 2008 Windows Server 2008 R2 Windows 7 & Windows Vista
    A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application
    or Microsoft Connect
    Windows6.0-KB979744-x64.msu (CBS: Vista/Win2K8)
    Windows6.1-KB979744-x64.msu (CBS: Win7/Win2K8 R2)
    N. A.
    An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2
    Request from CSS
    N. A.
    AD RMS clients do not authenticate federated identity providers in Windows Server 2008 or in Windows Vista. Without this update, Active Directory Rights Management Services (AD RMS) features may stop working
    Request from CSS Select the download for Windows Vista for the x64 platform.
    Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode
    MSDN Windows6.0-KB979917-x64.msu (Vista)
    N. A.
    N. A.
    FIX: ArgumentNullException exception error message when a .NET Framework 2.0 SP2-based application tries to process a response with zero-length content to an asynchronous ASP.NET Web service request: “Value cannot be null”.

    Microsoft Connect

    N. A.
    RPC over HTTP clients cannot connect to the Windows Server 2008 RPC over HTTP servers that have RPC load balancing enabled.

    Request from CSS

    Select the download for Windows Vista (x64)
    N. A.

    An update is available to remove the application manifest expiry feature from AD RMS clients.

    Download Center
    N. A.
    N. A.
    WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1
    MSDN Windows6.0-KB982867-v2-x64.msu (Vista) Windows6.1-KB982867-v2-x64.msu (Win7) X86: Windows6.1-KB982867-v2-x86.msu (Win7)
    x64: Windows6.1-KB982867-v2-x64.msu (Win7)
    FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.
    Microsoft Connect
    N. A.

    x64: Windows6.1-KB977020-v2-x64.msu

    x64: Windows6.1-KB977020-v2-x64.msu

    X86: Windows6.1-KB977020-v2-x86.msu

    Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBAs. The administrator experience when initially downloading these hotfixes may be a little odd. However, once you download the hotfixes, and receive two of the hotfixes from CSS, you can use the same for subsequent installs on other servers. In due course, all these updates may become available on the Download Center, and also through Windows Update.

    These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

  3. Prerequisite download pages linked from SP1 Setup are unavailable

    When installing Exchange Server 2010 SP1 the prereq check may turn up some required hotfixes to install. The message will include a link to click for help. Clicking this link redirects you to a page saying that the content does not exist.

    We’re working to update the linked content.

    Meanwhile, please refer to the TechNet article Exchange 2010 Prerequisites to download and install the prerequisites required for your server version (the hotfixes are linked to in the above table, but you’ll still need to install the usual prerequisites such as .Net Framework 3.5 SP1, Windows Remote Management (WinRM) 2.0, and the required OS components).

  4. The Missing Exchange Management Shell Shortcut

    Some customers have reported that after upgrading an Exchange Server 2010 server to Exchange 2010 SP1, the Exchange Management Shell shortcut is missing from program options. Additionally, the .ps1 script files associated with the EMS may also be missing.

    We’re actively investigating this issue. Meanwhile, here’s a workaround:

    1. Verify that the following files are present in the %ExchangeInstallPath%\bindirectory:
      • – CommonConnectFunctions.ps1
      • – CommonConnectFunctions.strings.psd1
      • – Connect-ExchangeServer-help.xml
      • – ConnectFunctions.ps1
      • – ConnectFunctions.strings.psd1
      • – RemoteExchange.ps1
      • – RemoteExchange.strings.psd1

      NOTE: If these files are missing, you can copy the files from the Exchange Server 2010 Service Pack 1 installation media to the %ExchangeInstallPath%\bin directory. These files are present in the \setup\serverroles\common folder.

    2. Click Start -> AdmiinistrativeTools ->, right-click Windows PowerShell Modules, select Send to -> Desktop (as shortcut)
    3. Go to the Properties of the shortcut and on Target replace the path to C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command “. ‘C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1’; Connect-ExchangeServer -auto”

      Note: if the Exchange installation folder or drive name is different than the default, you need to change the path accordingly.

  5. Upgrading Edge Transport on Forefront Threat Management Gateway (TMG) and Forefront Protection for Exchange 2010

    If you upgrade a server with the Edge Transport server role running with ForeFront Threat Management Gateway (TMG) and ForeFront Protection for Exchange (FPE) enabled for SMTP protection, the ForeFront TMG Managed Control Service may fail to start and E-mail policy configuration settings cannot be applied.

    The TMG team is working on this issue. See Problems when installing Exchange 2010 Service Pack 1 on a TMG configured for Mail protection on the ForeFront TMG (ISA) Team Blog. Exchange 2010 SP1 Release Notes has been updated with the above information.

    The ForeFront TMG product team has released a software update to address this issue. See Software Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1 now available for download.

  6. Static Address Book Service Port Configuration Changes

    The location for setting the port the address book service should use has changed in SP1. In Exchange 2010 RTM you had to edit the to configure the service port. In SP1 you must use the following registry key:
    Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters
    Value name: RpcTcpPort
    Type: REG_SZ (String)

    When you apply SP1 to a machine where you had previously configured a static port by editing the file, the upgrade process will not carry forward your static port assignments. Following a restart, the Address Book Service will revert to using a dynamic port instead of a static port specified in the config file. This may cause interruptions in service.

    As with all upgrades where servers are in load balanced pools, we recommend you perform a rolling upgrade — removing servers from the pool, updating them and then moving the pool to the newly upgraded machines. Alternatively, we recommend that you upgrade an array of servers by draining connections from any one machine before you upgrade it.

    There are times when these approaches may not be possible. You can maintain your static port configuration, and have it take effect the moment the address book service starts for the first time following the application of the service pack, by creating the registry key BEFORE you apply SP1 to your server. The registry key has no impact pre SP1, and so by configuring it before you apply the Service Pack you can avoid the need to make changes to set the port post install, and avoid any service interruptions.

  7. iPhone, OWA Premium and POP3 & IMAP4 issues due to invalid accepted domain

    After applying E2010 SP1:

    1. iPhone users may not be able to view the content of incoming messages in their Inboxes, and when they try to open a message, they get an error saying:

      This message has not been downloaded from the server.

      Admins may see the following event logged in the Application Event Log on Exchange 2010 CAS Server:

      Watson report about to be sent for process id: 1234, with parameters: E12, c-RTL-AMD64, 14.01.0218.011, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.InboundConversionOptions.CheckImceaDomain, UnexpectedCondition:ArgumentException, 4321, 14.01.0218.015.

    2. OWA Premium users may not be able to reply or forward a message. They may see the following error in OWA:

      An unexpected error occurred and your request couldn’t be handled. Exception type: System.ArgumentException, Exception message: imceaDomain must be a valid domain name.

    3. POP3 & IMAP4 users may also not be able to retrieve incoming mail and Admins will see the following event logged in Event Log:

      ERR Server Unavailable. 21; RpcC=6; Excpt=imceaDomain must be a valid domain name.


    Please run the following command under Exchange Management Shell and verify that there is one domain marked as ‘Default’ and it’s DomainName & Name values are valid domain names. We were able to reproduce the issue by setting a domain name with a space in it, like “aa bb”

    Get-AcceptedDomain | fl

    If you also have an invalid domain name there (for example, a domain name with a space in it), then removing the space and restarting the server will fix the EAS (iPhone), OWA, POP3 & IMAP4 issues as mentioned above.

    Command to run under EMS would be:

    Set-AcceptedDomain –Identity -Name “ValidSMTPDomainName”

    Thes examples update the Name parameter of the “My Company” and “ABC Local” accepted domains (the space is removed from both):

    Set-AcceptedDomain –Identity “My Company” –Name “MyCompany.Com”
    Set-AcceptedDomain –Identity “ABC Local” –Name “ABC.Local”

  8. Error when adding or removing a mailbox database copy

    If a server running Exchange 2010 RTM (or Exchange 2010 SP1 Beta) is upgraded to Exchange 2010 SP1, administrators may experience an error when using the Add-MailboxdDatabaseCopy or Remove-MailboxDatabaseCopy cmdlets to add or remove DAG members.

    When you try to add a DAG member, you may see the following error:

    Add-MailboxDatabaseCopy DAG-DB0 -MailboxServer DAG-2

    The result:

    WARNING: An unexpected error has occurred and a Watson dump is being generated: Registry key has subkeys and recursive removes are not supported by this method.

    Registry key has subkeys and recursive removes are not supported by this method.
    + CategoryInfo : NotSpecified: (:) [Add-MailboxDatabaseCopy], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.SystemConfigurationTasks.

    The command is not successful in adding the copy or updating Active Directory to show the copy was added. This happens due to presence of the DumpsterInfo registry key.

    Workaround: Delete the DumpsterInfo key, as shown below.

    1. Identify the GUID of the database that is being added using this command:

      Get-MailboxDatabase DAG-DB0 | fl name,GUID

      The result:

      Name : DAG-DB0
      Guid : 8d3a9778-851c-40a4-91af-65a2c487b4cc

    2. On the server specified in the add command, using the database GUID identified, remove the following registry key:

      The GUID identified in this case is 8d3a9778-851c-40a4-91af-65a2c487b4cc. With this information you can now export and delete the DumpsterInfo key on the server where you are attempting to add the mailbox database copy. This can be easily done using the registry editor, but if you have more than a handful of DAG members, this is best automated using the Shell.

      This example removes the DumpsterInfo key from the 8d3a9778-851c-40a4-91af-65a2c487b4cc key:

      Remove-Item HKLM:\Software\Microsoft\ExchangeServer\V14\Replay\State\8d3a9778-851c-40a4-91af-65a2c487b4cc\DumpsterInfo

      To automate this across all servers in your organization, use the DeleteDumpsterRegKey.ps1 script.

      File: deletedumpsterregkey_ps1.txt
      Description: The DeleteDumpsterRegkey.ps1 script can be used to delete the offending DumpsterInfo registry keys that can cause this problem on all Exchange 2010 SP1 Mailbox servers in the organization. Rename the file to DeleteDumpsterRegkey.ps1 (remove the .txt extension).

      For more info, see Tim McMichael’s blog post Exchange 2010 SP1: Error when adding or removing a mailbox database copy.

Thanks to all the folks in CSS and Exchange teams who helped identify, validate and provide workarounds for some of the issues mentioned above, and to the Exchange community and MVPs for their feedback.

Bharat Suneja, Nino Bilic
M. Amir Haque, Greg Taylor,
& Tim McMichael


  • 9/7/2010: Updated list of files for the missing Exchange Management Shell shortcut issue
  • 9/15/2010: Udpated pre-reqs table:
    – 982867 required on Windows 2008 SP2
    – 983440 not required on Windows 2008 SP2
    – 977020 required on Windows 2008 R2
  • 9/21/2010: Added link to Software Update 1 for ForeFront Threat Management Gateway (TMG) 2010 Service Pack 1
    – Replaced “Request from CSS…” verbiage for KB 979917 with link to KB 979917 download on MSDN
  • 9/22/2010: Updated correct default Exchange install path (highlighted) in ‘The Missing Exchange Management Shell Shortcut” section: C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command “. ‘C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1′; Connect-ExchangeServer -auto”
Comments (178)
  1. nick says:


    Just a short question: Is it right that after installing SP1 it is no longer possible to manage Exchange 2010 forests with the EMC that don’t have SP1 installed?

    Thanks for your reply,


  2. adam says:

    This: also applies and the installer doesn’t appear to have any detection logic to avoid it, so it simply fails halfway through. If you’re doing an upgrade this can leave your server in an inconsistent state as it occurs just after all the old binaries are deleted.

  3. MS PFE says:

    FYI – The SP1 Prerequisites differ depending on role – per the SP1 upgrade Readiness Checks. I installed E2010 SP1 on my E2010 RTM/W2k8 R2 servers. CAS needed: 982867 979744 983440 977020 979099. HUB and MBX only needed: 979099 and Microsoft Office 2010 Filter Packs. UM only needed: Microsoft Unified Communications Managed API, Core Runtime 64-bit and Microsoft Server Speech Platform Runtime (x64).  I also had to make sure the Windows Firewall service was running.

  4. GoodThings2Life says:

    I’m having trouble installing the UC Managed API Core Runtime… it fails with an error 1603. Unfortunately it doesn’t seem to identify in the log which file path/registry entry it might be failing on. Any suggestions?

  5. Bharat Suneja [MSFT] says:

    @MS PFE: Thanks for the details on requirements per server role. Note, this post only covers hotfixes. As mentioned in the post, Exchange 2010 Prerequisites lists the OS pre-reqs such as Filter Pack, .Net Framework, etc.

  6. Dan_IT says:

    also noticed that in  addition to The Missing Exchange Management Shell Shortcut

    powershell reg settings for some snapins are missing as below



  7. Andy Snow says:

    @Exchange Team: Next time around please take another month or two and release products that install cleanly. Thanks for the post, surely helps (but should be done before release).

  8. Gilberto Verastegui says:

    I got an error when upgrading my MB/HT server, the Upgrade ran perfectly on CAS, but in MB/HT Server i’m getting an error on the Mailbox Role, it says this:

    [ERROR] This server role can’t be installed because the following roles aren’t current: AdminToolsRole

    Any idea?

  9. CypherMike says:

    Is it supported, recommended that for a new Exchange 2010 install the SP1 is copied to the Updates folder, to incorporate the service pack into the install server installation process?

  10. Tim Bauer says:


    As far as I know, the SP1 you downloaded – after unpacking – it’s a full Exchange 2010 Installation "Disc" with SP1 integrated.

    You don’t need your old "RTM" Disk.

    You can install your future exchange server with this new install files.

  11. Ramy says:

    Why Microsoft is no more considering quality of software?

    Why Exchange 2010 SP1 has all these bugs?

  12. Steven says:

    Just to be aware!

    Following my upgrade i could no longer open EMC, OWA etc on any of my CAS servers.

    I discovered that the default website was not started. New bindings had been added to a secondary website which i use for external owa on a additional IP address.

    As these bindings were to localhost on port 80 & 443 this obviously conflicted with the deafult website. Removing the newly created bindings and starting the default website solved my issues.

  13. Ali Salman Naqvi says:

    Better not to run SP1, exchange 2010 looks better with out it.

  14. MSEBlogger says:

    I am amazed…  in the history of all Exchange hotfixes, rollups and Service Pack releases, I don’t think I recall seeing so many possible variations of flaws in the process to either upgrade or deploy new.

    Can someone please explain why it was acceptable practice to release such an update with this many potential flaws, the majority of which seem to incur downtime and inconvenience to the end customer?  I’d really like to be able to see the positives with this release, but am struggling when the first hurdle to be jumped is so large.

    Many thanks in advance.

  15. Jon says:

    Another issue I have uncovered. Brand new install, SP1 with server r2.  Install is completed but cant intialize the EMC at all. More than one person is reporting this

    The following error occured when retrieving user information for Contosoadministrator

    The operation could not be performed because object ‘s-1-5-21-4280747840-81974243-757702645-500’ couldnt be found on It was running command Get-LogonUser

    CMDlet failed. Cmdlet Get-User, parameters {Identity=s-1-5-21-4280747840-81974243-757702645-500}

    MsExchange Management Event ID 6

  16. Flamingo says:

    I have the same issue as Jon, but in this case I installed sp1 on an existing Exchange 2010 server.

    Have tried to run the get-logonuser from Exchange Management Shell but it seems that the cmdlet can’t be found at all.

    [PS] C:UsersAdministratorDesktop>get-logonuser

    The term ‘get-logonuser’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check t

    he spelling of the name, or if a path was included, verify that the path is correct and try again.

    At line:1 char:14

    + get-logonuser <<<<

       + CategoryInfo          : ObjectNotFound: (get-logonuser:String) [], CommandNotFoundException

       + FullyQualifiedErrorId : CommandNotFoundException

  17. Bharat Suneja [MSFT] says:

    @CypherBit & Tim Bauer: Yes, the SP1 download is the full product. For new installs, you don’t need to install RTM and then upgrade to SP1, and you don’t need to slipstream SP1 bits into RTM bits.

  18. Ilantz says:

    Just a heads up for anyone wondering, to make sure the upgrade process will not have any issues with services start-up – when ForeFront for Exchange 2010 is installed disable the integration before upgrading, and enable it back after…

    "C:Program Files (x86)Microsoft Forefront Protection for Exchange ServerFSCUtility.exe" /disable & /enable


  19. jojobahian says:

    Thanks for the info…

  20. Jo says:


    I work with hosted Exchange version and i don’t have the "New-MailboxImportRequest" command… I search in the list with "Get-Command" but it does not appear.

    However, i have the "Get-MailboxImportRequest" command so it’s wired…

    Can anyone verify if this command is available please ?

    Thanks !

  21. Doug says:

    I love SP1, and have installed it on two servers, but I too am "scared" each time I install it, thinking it’s not going to work.  How I long for the service packs of, say, Exchange 2003, when it just worked.

  22. People who whine about Exchange 2010 SP1 not being "stable", "buggered" or whatever should conisder the complixty of the product, and the hundreds of thousands of lines of code this involves. Just upgraded different environments without any issue, including a test lab from SP1 Beta to SP1 RTM.

    The devteam *can not* test each SP/rollup on *all* possible environments; of course they’re testing them, but the core assumption is that the environment to upgrade is mastered and clean.

    Anyway, dear DevTeam, there’s no (public) mention on the move of the following settings:

    – Address Book throttling moved to the Throttling Framework (companies with BES will be interested in knowing ;))

    – OWA/IM integration: configuration during upgrade will be cleaned up (removed from the Web.config) and will have to be reconfigured with the Set-OwaVirtualDirectory cmdlet.

  23. Florent_B says:

    I confirm issue describe in number 7. However it occurs only when the CAS is on the same server than Mailbox.

  24. cengiz says:

    I have the same issue as Flemming,  I also installed sp1 on an existing Exchange 2010 server. And now EMC dont work!!

  25. tom says:

    If you’ve got this many bugs in a service pack, you’re really quite messed up in that someone did not do enough testing or that you tried to cram too much into one service pack.

    What you should do is withdraw this SP from the market, fix it so it works properly, and also bake in all the additional dependencies that you created with hotfixes and whatnot.

    Basically no one in their right mind should install this until you release Service Pack Two (2) to fix all the mistakes in SP1.

    Seems like E2k10 is becoming the Windows Vista of email servers.

    Only reason to buy it with all these bugs etc. is vendor lock-in.

  26. Milton Lopez says:

    As one of many customers moving from 2003 to 2010, the issues with SP1 leave us pondering whether we should wait for SP2 …

  27. Bobby says:

    I think a lot of people don’t get the big picture here.

    If SP1 was so bad, I am sure that someone could uncheck the checkbox somewhere and pull the download.

    Instead, the team is up front about issues that some people see. If you read this blog, you know its not the first time they do that.

    Thanks for being honest, Exchange team! Would like to see fewer gotchas and that hotfix list is just crazy. But I applied SP1 withno issues.

  28. Jeff Sullivan says:

    @ExchangeTeam: Thanks for a comprehensive and informative blog post on the known issues with SP1. We just upgraded to SP1 with no issues other than the initial time required to figure out and download the hotfixes. Yes, we have DAGs too.

    Keep up the great work!!

    @Tom and others: You may want to read the blog again and actually try installing SP1 – not all of these are bugs. :)

  29. Dmitri says:

    Followed instructions to fix the DAG issue in lab. Nice post!

  30. Mellachi says:

    Hi, first off thanks for al the hard work. The update went as expected. There is just one problem. Some users have an empty global address list in outlook 2007.  They can’t search it or anything. In OWA the addressbook seems fine. When I disable offline mode the addresslist is still empty. No static port was set prior to sp1. Someone seen this issue and was able to resolve it?

  31. Phil says:

    The EMC issue is fixed by following :

    If the WSMan module entry is missing from the global modules section of the C:WindowsSystem32InetsrvconfigApplicationHost.config file, as follows:


                  <add name="WSMan" image="C:Windowssystem32wsmsvc.dll" />

    For some reason SP1 installer stripped this line.  Adding it back in and restarting the Default Web Site in IIS Admin solved that issue for us.

    I’d also recommend a reboot after updating Mailbox servers, though a restart of the Windows Search (Exchange) service will suffice.  Otherwise you may get reports of "corrupt index" trying to switch  the Active node for DAG databases.

  32. CypherMike says:

    @Bharat Suneja [MSFT]: Thank you. Any idea when it will be available on VLSC? I only have the non SP1 version available.

  33. gavur says:

    I have WSMan module in C:WindowsSystem32InetsrvconfigApplicationHost.config file.

    And EMC is not working!

  34. Anthony Spiteri says:

    Just like to say that I am seeing this aswell…thought it was my setup, and I have been going crazy trying to work out whats going on…any ideas from the Exchange team?

    Mellachi said:

    Hi, first off thanks for al the hard work. The update went as expected. There is just one problem. Some users have an empty global address list in outlook 2007.  They can’t search it or anything. In OWA the addressbook seems fine. When I disable offline mode the addresslist is still empty. No static port was set prior to sp1. Someone seen this issue and was able to resolve it?

    September 3, 2010 2:57 AM

  35. Riz555 says:

    Hi, having a problem with SP1, get the following when installing on CAS:

    Organization Preparation Failed

    Error: The following error was generated when "$error.Clear();

    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions

    $RoleActiveDirectorySplitPermissions" was run:

    "The well-known object entry 32:45FA417B3574DC4E929BC4B059699792:CN=Public Folder ManagementADEL:5b5de428-8721-4900-ab3a-fcd4641d408f,

    CN=Deleted Objects,DC=sample,DC=com on the otherWellKnownObjects attribute in the container object

    CN=Microsoft Exchange,CN=Services,CN=Configuration,

    DC=sample,DC=com points to an invalid DN or a deleted object.  

    Remove the entry, and then rerun the task.".

  36. Raul says:

    I’m confused on the release notes, so when it says it doesnt support OCS2007 does that mean after I install SP1 that my users with communicator will not longer have their integration working? such as the calendar not syncing with there presence.

  37. John Jackson says:

    I noticed that sp1 includes the  x-originating-ip email header when sending out of orgainzation and the inclusion of the mapi version (with mapi id 14.01.0218.012exchange) on the received header.  Was under the impression that Exchange was trying not  to advertise the version running (the smtp banner was changed with exchange 2007 to be "nuetral").  I’ve removed the x-originating-ip email header  by creating a transport rule but was wondering why the change in information released in an email.

    Thanks for the great work

  38. John says:

    SP1 = iPad IMAP fail.    After the upgrade any IMAP connection gets a "This message has no content." error on about 50% of the emails that have HTML in them.    The listed iPhone tweak does not fix this.    Activesync seems fine, its IMAP that seems to be the problem.   Anyone know of a fix for this?    I have to wait 2 more months before I can have mutlipe activesyncs on the iPad, so I’m stuck using IMAP.     Its making me think about ditching the Exchange server at home and going gmail – just too many issues.

  39. Craig Batten says:

    I had a problem after upgrading to SP1 where my Receive connector no longer accepted connections, it was refusing even the server its installed from telnet access to port 25.

    Send connector was fine but I found I had to reapply the receive connector settings in either the powershell or EMC to make it work again.

    Anyone else experience this issue ?

    Unless it has been noted and I missed the comment before….

  40. Vicki says:

    I’m having an error (Some controls aren’t valid. – Setup previously failed while preforming the action "Install".  You can’t resume setup by performing the action "BuildToBuildUpgrade".) when trying to apply SP1 to Server 2008 R2 that has the Exchange 2010 Management Tools installed.  Can an installation of just the management tools be upgraded to SP1?

  41. Mellachi says:

    I’ve tested with multiple accounts, all the same problem. Now I’v stumbled on to an account that doesn’t have the problem on a laptop that’s not member of the domain. Anyone any ideas, I’m going insane with this problem.

    Anthony Spiteri said:

    Just like to say that I am seeing this aswell…thought it was my setup, and I have been going crazy trying to work out whats going on…any ideas from the Exchange team?

    Mellachi said:

    Hi, first off thanks for al the hard work. The update went as expected. There is just one problem. Some users have an empty global address list in outlook 2007.  They can’t search it or anything. In OWA the addressbook seems fine. When I disable offline mode the addresslist is still empty. No static port was set prior to sp1. Someone seen this issue and was able to resolve it?

    September 3, 2010 2:57 AM  

  42. Joerg says:

    this is just inacceptable. reminds me of the the first release of systems management server 2.0 many many years ago. please exchange team, pull the sp1 back and get some time for a better sp1. just a realistic opinion of someone who has been with exchange since 4.0.

  43. gavur says:

    Hi All,

    I still have problem with EMC after installing SP1! I check :

    and still got this problem please help.

  44. lbvo says:

    for people with EMC issues. check if .dotnet 4 is installed .

    remove from system restart the system and check EMC again.

  45. gavur says:

    IBVO i have  .NET Framework 4 Client profile and .NET Framework 4 Extended

    Installed should i remove them? Are you sure?

  46. lbvo says:

    I had the same issue. remove client first then framework4.

    Problem is that it worked in my situation. cannot be 100% sure it will work in any situation.

    You can check if more MC’s have the same issue. if so, then it will be DOTNET4.

  47. gavur says:

    yepp i have more and will check this now THX!

  48. gavur says:

    On my other MC i dont have .net 4 installed.

    .NET 4 is only installed on my exchange server with all of Exchange roles.

    Exchange server = Win 2008 r2, Exchange server 2010 SP1

    MC server = Win 2008 r2, EMC sp1

  49. lbvo says:

    CHECK for instance the server manager is opening or event viewer and many other MC’S on the system where exchange is installed.

  50. gavur says:

    I dont get any error or warning msg on event viewer on my servers?

  51. Mark Crossland says:

    As I am having very little success in getting hotfix 979917  by using the Hotfix Request Web Submission Form as requested, I did a google for the hotfix. Is this the correct one:

    The title says: "QFE for Sharepoint issues – Perf Counter fix & User Impersonation"

  52. M.Gamal says:

    I have also the same EMC issue , initialization failed with the message

    The following error occured when retrieving user information for Domainadministrator

    The operation could not be performed because object ‘s-1-5-21-4280747840-81974243-757702645-500’ couldnt be found on It was running command Get-LogonUser

    CMDlet failed. Cmdlet Get-User, parameters {Identity=s-1-5-21-4280747840-81974243-757702645-500}

  53. paul says:

    Just upgraded two servers, one RTM and one SP1 beta.

    No problems, both went smooth.


  54. Mark says:

    Vicki – One of our servers had this "build to build" error when installing sp1, I had to remove the Watermark reg key under one of the Exchange services, as described in this E2k7 posting :

    (scroll down)

  55. faq bay says:

    Is there any way I could install clamav GPL antivirus scanner for Exchange?

  56. Dawed says:

    Is the O2K3 shared calendar problem fixed on SP1?

  57. Jam365 says:

    I commented previously on help importing PST files in bulk. if anyone else is having similar difficuly I found the following article (the first in a set) useful:

  58. Bruce Johnson says:

    Yes, I think that Exchange 2010 looked more professional before SP1.. SP1 makes it look more like elementary students making a web page..

    But, the bigger issue is my http redirect no longer works.. no longer redirects to

    it gives a 403 error.

  59. Mickael says:

    I have also the issue with the EMC when initialize, failed to retrieve information about the domainAdministrator. Realy need to resolve that very quickly

  60. Dawed says:

    The Outlook2003 multiple shared calendar problem, describted in following link, isn’t fixed yet! Till there is no fix, a migration to 2010 isn’t practicable for me! sad!

  61. Mkris9 says:

    hI, Has anyone had any issues with mailbox assistants service not starting up? it just says the exe is locked when its not.

  62. Tilmann says:

    having trouble with the msexchangeservicehost:

    [09.08.2010 13:09:29.0596] [1] 0.  ErrorRecord: Service ‘Microsoft Exchange Service Host (MSExchangeServiceHost)’ cannot be started due to the following error: Cannot start service MSExchangeServiceHost on computer ‘.’.

    any idea why this is happening?

  63. Baltika says:

    I’m in the same boat as Adam (  thanks for finding this bug BTW) with my Powershell Execution Policy GPO breaking the install in a VERY inconvenient place. Some detection logic is definitely called for, especially since there’s already a KB mentioning the issue.  The whole fiasco ended last week with me reinstalling the OS and Exchange Server.  Because I like torturing myself, I’m about to give SP1 a go again.  Hoping for no new surprises this time.

  64. carl says:

    Does SP1 change the warning text from the organizational Checks when running "Setup /PrepareAD"  by adding "Exchange 2003 Servers" to the text?

    I am upgrading from Exchange 2003 to Exchange 2010 SP1.    I have already run /PrepareLegacyExchangePermissions and /PrepareSchema  from the SP1 media.  

    When running /PrepareAD with SP1 media we get this warning:  

    (Note the text about Exchange 2003 in Quotes below.)

    Setup is going to prepare the organization for Exchange 2010 by using ‘Setup /PrepareAD’. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any "Exchange 2003" or Exchange 2007 servers.

    If I run the same command on the same forest with the RTM media without SP1 it does not mention Exchange 2003 at all.

    Setup is going to prepare the organization for Exchange 2010 by using ‘Setup /PrepareAD’. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 server roles.

    Is this just a change in the warning text or is there something that I need to resolve before running /PrepareAD


  65. Justin.G11 says:

    New Bug not on this list:  when installing a fresh SP1 installation for a client to migrate to (have some clients specifically waiting on SP1 before considering an upgrade) I’ve notice a very annoying little bug:

    If you wait until SP1 is installed to upgrade your default policy  then it will be unable to do so, instead dumping out the same error you normally get form trying to edit it from the EMC.

    Exact Syntax:

    Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients

    Exact error Dump:

    The recipient policy "Default Policy" with mailbox manager settings cannot be managed by the current version of Exchange Management Console. Please use a management console with the same version as the object.

  66. nick says:

    I can no longer sync my Android phone.

    Moto Droid (original) v2.2, Build FRG22D.

    Connecting to Exchange 2010 SP1.

    I have GoDaddy SAN certs.

    I can access OWA from droid Browser.

    When I try to sync using activesync, I get "unable to open connection to server"

    My iPad, iPod, Mac (Snow Leopard) and PC (Outlook2010) work just fine.


  67. Speights says:

    I also have the issue with the EMC when initialize, failed to retrieve information about the domainAdministrator.

    It was running the command ‘Get-LogonUser’

    Surely someone must of found a work around by now?

  68. Chrismsummers says:

    I have been going round and round with CSS on 979917, the one where you have to submit the web request, and finally this morning they tell me it is unavailable.  I was lucky and a coworker had already deployed it at another customer so I was able to get a copy, but CSS should really be aware of something like this.  Pre-reqs for a major release really need to be publicly available.

  69. alan says:

    After reading this article I decide not to install exchange 2010  SP1. To Microsoft and Exchange Team what are you doing. If I did not read about the bugs maybe I cannot access my Exchange nowadays. Please make sure about your SP1 before releasing it. i understand that there is no perfect software. It is acceptable if it is minor bugs only but If we cannot access OWA after installation that is BS. What about the SSL certifcate we had installed maybe it be replace also.

    Is there anybody here that has a succesful upgrade of SP1.

  70. JD says:

    I also have the problem with initializing EMC. This was an existing Exchange 2010 install with RU4 upgraded to SP1. Server 2008 R2

    The following error occured when retrieving user information for Domainadministrator

    The operation could not be performed because object ‘s-1-5-21-4280747840-81974243-757702645-500’ couldnt be found on It was running command Get-LogonUser

    CMDlet failed. Cmdlet Get-UserLogon, parameters {Identity=s-1-5-21-4280747840-81974243-757702645-500}

    MsExchange Management Event ID 6

    I have been trying to find the Cmdlet Get-UserLogon but it is no where on the internet. Perhaps if MS could provide us with this Cmdlet it would fix the problem?

  71. KDD says:

    Whoever is having issue opening EMC or EMS

    Please create new user, with same rights as exchange was installed.

    Logoff and login with new user and try to open EMC or EMS.


  72. Daniel says:

    After installing SP1 i cannot login to OWA anymore.

    After login i just see a blank page.

    Does any of you guys know how to fix this?

    Thnx Daniël

  73. KeithL says:

    I have never seen a product take so many steps backward. 2000 and 2003 were rock solid, ever since 2007 Every Exchaneg SP or rollup seems to break things or create some sort of issues. 2010 SP1 breaks any OWA redirection and MS answer is not supported! Great work MS!! I miss 2003!

  74. JeffV says:

    This is a terrible Service Pack, like many other I am experiencing some very serious problems after installing SP1.

    Cannot open the EMC, big problem!

    Not even got to the other potential issues that others are experiencing.

    There is a lot of code to check, this is obvious, however to release a much anticipated Service pack which creates so many issues is quite unbelievable, doesn’t matter how many lines of code need checked, very very very bad…

    I have been trying bring a case to Management for us to upgrade from Exchange 2003 to 2010, this makes it practically impossible for anyone to make a case for upgrading.

    I am using virtual machines for my test lab, nice that I can just roll back.

    Can’t say how bad this is…

    Poor poor job…

  75. Tjeerd Posthumus says:

    I agree with all you guys, this service pack sux. I’ve been struggling with it for 4 days now and still the SP-installation won’t even complete.

    I read that this SP was released earlier then they’d anticipated, maybe that has a reason: They forgot to check a lot of shit!

    Please microsoft… fix it! That’s an order! :)

  76. tony says:

    If you have issue with OWA redirect after SP1 upgrade, go to IIS Manager on CAS, click on Default Web Site, and under SSL Settings, make sure "Require SSL" option is unchecked.

  77. Mihai says:

    To Bruce Johnson and KeithL:

    Your redirection problem is very easy to fix. Disable "Require SSL" on the Default Web Site on every CAS. The upgrade to SP1 turns that on by default. Only on the Default Web Site.

  78. KK says:

    I experience a lot of Event 1053 errors on my mailbox servers after upgrading to SP1 on Exchange 2010. I didn´t have that error prior to the upgrade.

    It´s a MSFTESQL-Exchange error, and the logs says:

    The system exception c0000005 was raised at 000007FEDFB6XXXX. Stack:

    I have searching around, and tried to recreate the Search DB but no succes. Maybe something you guys also have seen??

  79. Johan Sch says:

    Whew..this looks bad. I’ll wait until maybe this shows up on WindowsUpdate..I assume the prereqs will be published by then and the quirks slipstreamed over.

  80. sterod says:

    I upgraded from RTM to SP1 using the instructions provided on this blog and on the MSDN pages.  Now, the RpcClientAccess.Service.exe keeps crashing and throwing exceptions in the event viewer.  I think this error may be related to the BES Express 5.0.2 server on the same box. Can anyone offer a solution?

    System Log

    The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

    Application Log

    Application popup: Visual Studio Just-In-Time Debugger : An unhandled exception (‘CrashNowException’) occurred in Microsoft.Exchange.RpcClientAccess.Service.exe [11072].

    Watson Report

    <watson-report event-type="E12" issue-type="4" timestamp="2010-09-11 20:34:17Z" reporting-enabled="0" xml:space="preserve">

    <details>InvalidOperationException (Nullable object must have a value.) in Microsoft.Exchange.RpcClientAccess.Handler.RopHandler.Logon</details>

  81. Speights says:

    KDD said:

    Whoever is having issue opening EMC or EMS

    Please create new user, with same rights as exchange was installed.

    Logoff and login with new user and try to open EMC or EMS.


    I tried this wouldn’t even let me open EMC at all as a different user with god rights (domain admins, enterprise etc) Haven’t had any problems with EMS.

  82. Jeffv says:

    I have also tried creating a new account with the same permissions as the account I used to install Exchange, this doesn’t work.

    Out of curiosity I decided to build a new DC and another server for specifically installing Exchange 2010SP1, not upgrading from 2010RTM, this has also failed with the same, "The operation couldn’t be performed because object (Administrator SID displayed) couldn’t be found on servername.domain.  It was running the command ‘Get-LogonUser’.

    Come on Exchange team and Microsoft as a whole, is nobody going to issue a statement or workaround/fix for this?

  83. Speights says:

    Yes I could really do with an answer from MS re: the EMC issue. As I have a customer scheduled for 9 Exchange server install over 3 sites and some of the new features of SP1 are required for this project!

  84. Samago says:

    I am having this problem as well and don’t know where else to turn. I have looked all over the net and really don’t know where to start. My biggest worry is that this has affected the existing mail server with mail not filtering through. I would really appreciate some steer on this. I have even tried installing UR4 over sp1 but to no avail. HELP!!!

  85. Jeffv says:

    I changed the names and configuration of my servers and installation paths of Exchange 2010SP1 and I can now access the EMC.

    This is my configuration, all virtualised using WMware Workstation 7x:

    1x DC, Server 2008 Ent, Full Installation.

    2x Member Servers, 2008 Ent, Full Installation.

    Name of DC = DC, was called vDC1

    Name of 1x Member Server = Prime, was called Ex2k10Prime

    Name of 2nd Member Server – MBX, was called Ex2k10MBX01

    Prime is setup for the following Exchange Roles = Hub & CAS.

    MBX is setup for the Mailbox role.

    Originally I had also installed the Exchange app on a seperate HDD, this time round I left it in it’s default installation path.

    Not sure why this is working now but it is, if these settings are what has made the difference this would imply that I cannot use numbers is computer names as vDC1 is not too long a name, or the default installation path cannot be altered.

    None of my server names had a "." or space in them, all I have done is removed any and all numbers from the names, kept the default installation path.

  86. REDDY says:

    Hi Experts

    I have upgraded Exch 2010 to SP1, every thing works fine. But when I dismount/Mount the mailbox database I am seeing the following error.

    It is mounting mailbox fine…

    Failed to save admin audit log for this cmdlet invocation.


    Log content:

    Subject: : Mount-Database


    Cmdlet Name: Mount-Database

    Object Modified: mdb15-MountP

    Parameter: Identity = mdb15-MountP


    Succeeded: True

    Error: None

    Run Date: 2010-09-14T14:51:21

    OriginatingServer: hostname (14.01.0218.011)


    Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException: Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=hostname/cn=Microsoft System Attendant. —> Microsoft.Mapi.MapiExceptionLogonFailed: MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)

  87. Justin.G11 says:

    Amidst the clamoring I have successfully rolled this patch out to 2 clients without too much problem.  I did discover a bug I noted above, but for the most part if we recognize that SP1 is less a service pack and more a bundling of new features and options and thus effectively a new build and thus go through the proper testing all the upgrade issues are fairly predictable and not hard to work around.

    Once upgraded, I will say the EMC "feels" snappier in it’s response time to the little things like manipulating database copies and submitting changes to AD, and some of the new flags available in the prepare-moverequest.ps1 are a godsend for the ADMT first, ask questions later folk.

  88. Peter Stutzinger says:

    as Jo mentioned way above,

    i am also missing the "New-MailboxImprtRequest" cmdlet at our hosted exchange setup.

    I’ve installed the complete multiserver setup with the -hosting switch and it looks like it was not installed.

    So, do i miss something or is this cmdlet really missing ?

  89. El Kabong says:

    As someone who is just beginning their deployment, has anyone started off fresh installing 2010 using the SP1 code (as opposed to upgrading from RTM)?  That’s what I’d like to do to see if I can avoid the reported issues.  I’ve tried going through the wizard (w/o completing the install) and ended up having to re-run the ‘/prepareAD’ & ‘/prepareDomain’ again to get rid of errors that were being thrown by the setup wizard.

    Any feedback is appreciated.

  90. sterod says:

    Problem solved.  The solution was to add a Public Folders database using the EMC (Even though I don’t use or need Public Folders).

    It appears that BES Express 5.0.2 SP2 can no longer run without Public Folders in Exchange 2010 SP1, despite the fact that I had the "Ignore No PF" registry key DWORD set to 1 in HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindows Messaging Subsystem

    See this page.

    BES Express 5.0.2 SP2 was working just fine running without Public Folders so installing Exchange 2010 SP1 definately broke it.

    What tipped me off to finally resolved this was that the BES Utility IEMSTest was failing during the CDO Calendar test.  That made me take a closer look at this error in my RPC Client Access log file.

    "RopHandler: Logon: [RopExecutionException] A user doesn’t have an associated Public Folder database or it’s not connectable (Mailbox DB Guid = 254ff931-96f4-4aed-85e7-8968799a4311, PF DB Guid = 00000000-0000-0000-0000-000000000000). Error code = LogonFailed"

    The Guid with all zeroes was probably the cause of the "[InvalidOperationException] Nullable object must have a value." error that was also in the same log file.

    Anyhow, my total time wasted trying to resolve this : 8 Hours

    Thanks, Microsoft!

  91. Little Ghost says:

    I installed SP1 in 3 virtual environments. I got the "Get-LogonUser"-Error only in one installation. After a few hours of investigation i noticed that the Exchange Server and the DC of this installation have the same SID. Maybe I’ve forgotten to run sysprep to change the SID. I’ll try to shutdown the virtual server and reinstall a new one with same name and IP and run the Exchange 2010-Setup with /m:RecoverServer Parameter.

    Please check the SID of the servers with the PsGetSid-Utilitiy and post the results. Maybe this could be the "resolution" of the problem for many users.

  92. Eddie Wimberly says:

    @Mark Crossland

    Yes that is the correct hotfix.  It’s silly Microsoft makes you request it from the KB, but if you google it you can find it on their MSDN site at

    Remember 6.0 for Server 2008 SP2, 6.1 for Server 2008 R2.

  93. Cameron Brandon says:

    I get "The following error occurred when retrieving user information for domainuser: Unexpected error while executing command ‘Get-LogonUser’.

    For the life of me, I can’t seem to fix this. I read that the rollup 4 fixes the issue, but I didn’t have the issue until I installed SP1. I would have thought SP1 would have all the previous rollups, but now I’m not sure. And I can’t go back and apply the rollup because it checks for versions and sees I’ve already applied a newer update.

  94. Speights says:


    Thanks that is exactly what it was! Who would of thought duplicate sid would work fine on Exchange 2010 but not on SP1…. I could of sworn I had run sysprep on that VM but checked with psgetsid and sure enough it was the same.

    Just to clarify the work around for the EMC issue with Get-LogonUser I did was as follows:

    Rebuilt my VM, syspreped it to give it a new SID (You could use newsid) renamed the server with the same name joined it to the domain and ran /mode:recoverserver on the SP1 install.

    After it recovered and rebooted EMC was available however I have new issues to resolve now… ahhh I love SP1…

    Credit goes to littlehost for spotting the duplicate sids.

  95. Little Ghost says:

    I think now it’s official: The EMC-Error is caused by duplicated SIDs… :(

    The way I recoverd my Exchange-VM:

    – Shutdown Exchange-Services

    – Copy the entire Database-Folder to a temporary location (or use the virtual data-disk for the new VM)

    – Shutdown Exchange-VM

    – Install new VM or import a template and change the SID with sysprep (!!)

    – Remove old server account from AD

    – Rename the new VM with the old name and join the domain

    – Add the server account to the AD-group "Microsoft Exchange System Objects/Exchange Install Domain Servers" (to avoid MSEXCHANGEADTOPOLOGY-server startup error)

    – Copy the Exchange-database to the same driver/folder

    – Run "Setup /m:RecoverServer /InstallWindowsComponents" from Exchange 2010 SP1 Folder

  96. Samago says:

    Speights/ Little Ghost Thanks for the information and great catch there. With the VM rebuild process you have described, what happens to the Exchange configuration that has currently been set up? Will this server rebuild cause a loss of configuration or will this be rebuilt based on the backup of the database folder?

    I’m also assuming you run the system recovery after you install Exchange 2010 and SP1?



  97. gavur says:

    I have also the EMC problem I noticed that I had same SID’s on my DC and the Exchange server. I installed 2 new DC with new SID’s and removed the old DC  but I still have this problem?

  98. Speights says:


    The /m:RecoverServer mode installs Exchange 2010 and recovers all the original settings from the AD objects. You just need to backup your database as Little Ghost suggested.


    When you decommissioned the DC with the duplicated SID did it demote gracefully? There maybe still some references to it in AD try searching in ADSIedit and deleting any references to it.

  99. Travis says:

    If anyone has issues accessing OWA (Getting a 404 page) after installing SP1, I came across the issue last night and found that my issue was due to multiple IIS sites..the installer now adds a 80,443 binding to EVERY IIS Exchange site.

    More info @

    Like Mellachi and Anthony, I have empty GALs as well…I’ll post back if I figure it out. Are either of you doing split GALs or ‘GAL permissions’ by chance?

  100. Cameronk says:

    Great. I’m having the Get-LogonUser error as well, and just checked for duplicate SIDs, and my CAS/HT have the same SID, and two of my three mailbox servers have the same SID. Time for a rebuild, I guess. Thanks for the detailed instructions Little Ghost.

  101. El Muppo says:

    Exchange SP1 changed my x-originating-ip:  to IPv6, how do I change it back to ipv4?

  102. laura says:

    Do I need Rollup 4 installed before installing the pre-requisites and also SP1? We never upgraded from Rollup 3 due to the problems people have stated on the RU3 article comments, and additionally we never encountered any issues that were resolved by RU4.


  103. dawed says:

    anybody solved the outlook 2003 client multiple shared calendar issue?

  104. dahuhn says:

    Anyone also facing problems with MSExchangeMailSubmission service crashes every 24 hours? Got it since SP1 install.

  105. Little Ghost says:


    I agree with Speights. All Exchange 2010 Settings except SSL-Certificates were back after recovery


    Install all Windows-Patches, Office 2010 Filter Pack and additional required Windows Patches bevore starting setup…

  106. Cameronk says:


    If I could go back, I would definitely apply the rollup 4 before SP1, because the Get-LogonUser error is said to be fixed by the rollup. However, I didn’t apply it, thinking SP1 had the fix included, and now I can’t go back and install the rollup because it fails the version test, and won’t let you install. So, be safe and apply it before SP1.

  107. Little Ghost says:

    @Cameron & Laura

    I applied Rollup 4 a few weeks before installing SP1 and I got the "Get-LogonUser"-Error. The error was caused by duplicated SIDs.

  108. the exchnage guy says:

    I’ve done a new Exchange 2010 SP1 install today and was told that the bug in RTM where setting the OWA default language broke OWA and ECP was fixed in SP1. Is it heck. I used the cmdlets: Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -LogonAndErrorLanguage 2057    and: Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -DefaultClientLanguage 2057   and, guess what? OWA broke. Same old chestnut – go to open OWA options and it errors. try to use ECP and it wants to set language and then errors.

    Thankfully I still had a record of the workwaround – unset the language by running the same cmdlets but choosing 0 as the value instead of 2057. Come on guys, this has been broke for 10 months now….

  109. the exchnage guy says:

    Were you aware that EMC no longer displays a warning at the top of the work pane when an error is encountered? This used to be a tell-tale sign that some attributes such as illegal characters in the exchange alias existed or that the UPN suffix needed fixing. Great, EMC looks more clean – but you’re actually making more work for us. And when I do open the properties of a mailbox that has some problem with some value, I get a warning box stating that invalid data exists, but it doesn’t tell me where. I’m having to hunt down the issues. It’s not progress, it’s one step forward and two steps back.

    Thankfully when I apply the email address policy, the output includes more detail so I’m able to track back to fix the issues.

  110. davide says:


    has anyone an explanation to this weird psgetsid behavior ?

    i have 1 active directory domain (CONTOSO) with 1 domain controller DC01 and 1 Exchange server EX01:

    psgetsid "CONTOSODC01$"

    SID for CONTOSODC01$:


    psgetsid \DC01

    SID for \DC01:


    psgetsid "DC01"

    SID for DC01DC01:


    psgetsid "CONTOSOEX01$"

    SID for CONTOSOEX01$:


    psgetsid \EX01

    SID for \EX01:


    psgetsid "EX01"

    SID for EX01EX01:


    The only issue we are experiencing is that we cant  login to the EXCHANGE server with any domain user account + in its system event log I can see a NETLOGON 5516 Error stating that EX01 and CONTOSO have the same machine security identifier (SID).

    Any idea?


  111. krampit says:

    after applying sp1 to an edge transport server do you need to do a new Edge subscription?

  112. Little Ghost says:


    I had the same error on 1 DC, 1 Exchange-Server, 1 Oracle-Server with same SIDs.

    I couln’t login to the Exchange- and Oracle-Server with domain accounts.

    The solution was to reinstall the Exchange-Server (new SID!!) and recover the Exchange-Installation. After that the problem remains only on the Oracle-Server waiting reinstallation :)

  113. Brian says:

    Where are all these duplicate SIDs coming from?  Is everyone cloning VMs and not running sysprep prior to deploying these servers?  I’m about to install SP1 but am trying to get a handle on all of these reported issues prior to the attempt.  

  114. Carsten17 says:

    DING DING DING; Earth to MSExchangeteam!!!!!

    I am planning an SP1 upgrade for an environment with several thousand mail-users and I do NOT feel confident when so many questions from this blog goes on un-answered from the Exchange Team.

    With a large environment and narrow Change window I can simply not afford to start troubleshooting issues after this topology gets updated.

    Now, get working and get some updates here…..


  115. Kevin says:

    Anyone else receiving this?

    EVENT ID: 4999

    Source: MSExchange Common

    Watson report about to be sent for process id: 440, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailSubmission, M.Exchange.StoreProvider, M.M.MapiEventManager.SaveWatermarks, M.Mapi.MapiExceptionArgument, 69c9, 14.01.0218.011.

    ErrorReportingEnabled: False

  116. Kevin says:

    The Mail submission service restarts every hour since upgrading to SP1.  Any ideas?

    Log Name:      Application

    Source:        MSExchange Common

    Event ID:      4999


    Watson report about to be sent for process id: 440, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailSubmission, M.Exchange.StoreProvider, M.M.MapiEventManager.SaveWatermarks, M.Mapi.MapiExceptionArgument, 69c9, 14.01.0218.011.

    ErrorReportingEnabled: False

  117. Kevin says:

    Correction to above statement, every 24 hours the service restarts itself.

  118. Bharat Suneja [MSFT] says:

    @Carsten17: Blog comments are an important feedback mechanism that ties the Exchange community to the Exchange team. We review all comments, and a large number of comments and feedback are responsible for generating follow-up actions within the product
    team. Such actions may not be immediately visible to customers, and include follow-up blog posts, creation and release of hotfixes or interim updates, documentation changes, and new product features or changes to existing features.

    While we attempt to answer most questions posed in blog comments, we can’t respond to each comment or question individually.

    We recommend that you post questions related to your particular Exchange deployment in the Exchange forums on TechNet (,
    where many community experts, including MVPs and Microsoft employees, can answer them. For assisted support, please contact CSS (

  119. SD52 says:

    Hi folks,

    We feel your pain everyone. We applied SP1 around Sept 4th, weren’t many issues posted at that time. We were running an all in one CAS, MBX, and HT server. Long story short, SP1 appeared to upgrade properly via the gui, however it has never been the same since. We have since deployed a new CAS server, and a HT/MBX server and migrated everything off the old box. The old MBX database is now offline, and everything is going through the new servers. I’ll wait a couple more days before decommissioning.

    We worked with MS Tech Support, had a good experience with a guy named Anwar out of India. Very knowledgable and freindly, I love MS tech support.

    In the end though, I hope you are listening MS Exchange Team,,, this service pack did not get enough regression testing. I’m sure its too late to retract it, but please help these people! The incredible stress presented by a failed messaging and collaboration platform is off the charts. As customers, this is the kind of thing that makes us consider hosted alternatives, and MS does not always shine the brightest if you force us that way.

    We like our in-house mail servers, but this has gone too far.

  120. New install of Exchange 2010 SP1 in an Exchange 2003 Organization with Blackberry 5.0.2 installed. Moved mailboxes and BB-Mailbox to Exchange 2010 and suddenly some users are losing their calendar entries on BB-devices. We too late discovered, that RIM doesn’t support Exchange 2010 SP1 at the moment. Very funny….and NO IDEA!

  121. magic says:

    I am trying to upgrade to sp1 and  stuck in a reboot request during the readiness check any idea?

  122. Thorsten5 says:

    Hi, I found out that the web.config file (ClientAccessOWA)is "cleaned" after installing SP1. My customizations have been removed and the .bak file did not contain the "old" version.

    I think this is a critical issue, because configuration data is lost.

    Is team working on this?

  123. Albert Gotink says:

    Has anyone tested the Move-TransportDatabase.ps1 script?

    I does not work when not all arguments are given. The RTM script worked OK with 1 or 2 parameters.

    I think the "param" section in the script should not containt "[String]"

    Can anyone confirm this?

  124. John Weber says:

    @msft:  sp1, if directions are followed and prereqs met, goes right in,  no issues.  Thanks for the work, especially the archive mailbox change.

    @whiners:  stop.

  125. Jeff James says:

    If you have a Blackberry Enterprise Server in your environment I would hold off on applying SP1 for Exchange 2010 as it is not supported by RIM at this time…they only support up to rollup 4.

  126. SteenKirkby says:

    Great! – I got the get-userlogon error as well on my brand new test setup with 2xDC and 3xEXCH servers. Everything was running fine before applying Exchange 2010 Service Pack 1. Thank goodness this was just a test setup!

    I suspect that the Microsoft Exchange team in fixing the issue mentioned in KB981033 (Netbios names with dots in) just switched to using stoneage-technology (searching for SIDs in stead of servernames). In other words in order to fix a problem that less than 0.01 % of all their Exchange customers might experience they created an even bigger problem for lets say 5-10 % of all their Exchange customers.

  127. SteenKirkby says:

    Just did some more research on this issue and this is what I found out:

    It seems that EMC is searching for the machine SID (and not the DOMAIN SID for that computer) – probably as a bug fix to the KB981033 issue (customers who put dots in their computer Netbios names – who would ever do that?!#.)

    In my case the machine SID was the same on all virtual servers:


    (same result you get when running psgetsid without any parameters)

    All my virtual machines were of course cloned before they ever joined a domain. As my child wisdom told me a machine will get a unique domain SID when it’s joined to a domain – even when several machines with the same machine SID are joined to a domain they will always get a unique domain SID. Hence when I run:


    The results are all different:











    When I go through adsiedit and check the "objectSid" attribute of all the computer accounts they are indeed the same unique values that psgetsid DOMAINCOMPUTERNAME$ gave me from the command line.

    It clearly looks as this is a huge bug in the EMC. The search that it does in the background should have been based on a full ldap-path, objectSid (the domain one), objectGUID or something else than the local machine SID.

  128. Bharat Suneja [MSFT] says:

    @Steen Kirkby: Please take a look at KB 314828:
    The Microsoft policy for disk duplication of Windows installations

    When you deploy a duplicated or imaged Windows installation,
    it is required that the System Preparation (Sysprep) tool is used before the capture of the image.

  129. SteenKirkby says:

    @Bharat Suneja [MSFT]: Thanks I know that and I would also take the time to do sysprep if it was a production environment. This was just a quick test setup to do some tests on multiple site DAGs. Still it doesn’t change the fact that the SP1 EMC is now all of a sudden using SIDs for something that they were never designed to be used for.

  130. GT says:

    @Steen Kirkby: I don’t think it is up to you to decide what a SID is designed to be used for.  MS has always been clear on the requirement to Sysprep cloned machines.

  131. SteenKirkby says:

    Update: I have now reinstalled all three Exchange Servers by:

    Shut down exchange services -> copy database files -> shut down VMs -> reset computer accounts in AD -> install new VMs (sysprep’ed) -> join to domain with old servers names -> copy databases to new VMs (same locations) -> run Exchange 2010 SP1 setup with "Setup /m:RecoverServer /InstallWindowsComponents".

    Exchange Management Console and everything else now works again.

    Keep in mind that the only thing changed here is the local machine SIDs as I reused the old computer accounts in the domain and they still have the old domain SIDs in the objectSID attribute. No doubt in my mind that the new SP1 EMC is searching for a local machine SID and not the computer account SID in the domain.

    @Little Ghost: Thanks for uncovering the duplicate SID issue

    @Speights: Thanks for confirming and no you could not use NewSid in stead. It’s unsupported and corrupts Windows 7 + 2008r2. Sadly – because I used to love that little tool – but we will have to stick with the more heavy and timeconsuming sysprep tool.

    @GT: You’re right – sysprep is the only way to go. Sorry if I offended but I am still of the opinion that behind this is a programmers late night decision to solve one problem (the dot in Netbios names KB981033) and instead cause several others. He probably used the machine SID because it was easier than doing an LDAP search and his Netbios / DNS routine didn’t work in some scenarioes (so a dot in a Netbios name is probably supported – weird). Luckily he can just relax and say that the now failed scenarioes are officially unsupported by Microsoft. If he had done his job well he would at least have put in a check for duplicate SIDs in the prerequisites checker and let the wizard fail with a nice explanation.

  132. JoshFixTheExchange says:

    Other than taking almost 2 hours to complete, the only issue I ran into was it breaking McAfee Groupshield 7.0.2.   The Transport service would not start with the Groupshield service running.  Disabling the Groupshield service allowed the Transport service to start again. McAfee says they don’t support SP1 yet (shocking!).  I have a ticket in with them to supply a hotfix.  In the meantime, I am without virus scanning on my Exchange 2010 SP1 servers.

  133. MrBeck says:

    Anybody having issues with bad unicode handling in Exhchange 2010 after the SP2 install. All of a sudden we are having a ton of issues where email coming from a variety of sources, including hotmail.

    Below is an example:

    䠼TML dir=ltr>䠼EAD>㰊META content="text/html; charset=unicode" http-equiv=Content-Type>㰊META name=GENERATOR content="MSHTML 8.00.6001.18882"㰾/HEAD>㰊BODY> 䐼IV㰾FONT color=#000000 size=2 face=Arial>Here you go⼼FONT㰾/DIV> 䐼IV㰾FONT size=2 face=Arial>Linda Schlechte㱲/FONT>⼼DIV>⼼BODY㰾/HTML>

    Funny thing is, client sends the same email to gmail, and we pass it through back to exchange and it comes through clean.

    Anybody else come across this? We found something on experts exchange related to Exchange 2007 way back and his fix was to remove the RU he had installed. In this case, I am loathe to uninstall an Exchange SP.

  134. JoshFixTheExchange says:

    FYI HF616318 from McAfee takes care of the issue in my previous comment.  Currently you have to request this hotfix, as its not available from their website.  The Transport service works without issue after applying it.

  135. micra says:

    We are after fresh installation SP1 and migration from E2k3. Environment: 6 CAS/HUBS, 8 MBX in first DAG and 2 MBX in second DAG, 2 EDGE on TMG, 2 UM. Number of migrated mailboxes – between 20 and 30 thousands.

    What is better after SP1:

    – faster OWA – in Premium and Light version;

    – no problems during migration, before SP1 10% of migrated mailboxes weren’t disconnected from Ex2k3 databases;

    – no problems with replication of DAG mailboxes.

    What is worse or similar to RTM version:

    – very, very big sensitivity of DC accessibility; services (OWA, ECP) after problem with accessing to DC (overloaded) there is no access to OWA 15-30 minutes or longer, sometimes we should restart CAS/HUB;

    – impossibility to restart some service (IIS or from Exchange suite) to return good state of service – we must restart whole server.

  136. Derrick Baxter says:

    Exchange 2010 SP1 EMC Get-Userlogon error message

    After running into this and posting to the ranger alias, I had a private conversation which "possibly indicated" duplicate machine SIDs.

    I had deployed my Hyper-V lab with SCVMM library template all from the same syspreped image.

    It would happen that the person I spoke to said, "Did you make sure to select the "Generalize" checkbox?

    Typically up til now this same image worked just fine with 2010 RTM so I never bothered to click that.

    I went through and took that library image and deployed, started up and reran sysprep, chose Out Of Box Experience from the dropdown list and this time Chose the "Generalize" checkbox. and chose to shutdown.

    I then moved it back to the library and created all the servers in this lab over again.  AD, Hub/CAS, Ex Mailbox, and LoadGen servers, recreating the AD and installing Exchange on the hub/cas server w/mailbox so I can get the arbitration mailboxes on the hub/cas.

    This time when it completed and the EMC came up, it took a while but then the little hour glass on the tree went away, the details pain actually progressed and came up fine this time.

    I then installed 2010 SP1 onto the Mailbox only server and it also worked just fine.

    Long and short, if you deployed via sysprep and didn’t use the generalize option, or copied vhd or vmdk you may have had this problem.

  137. james says:

    Just deployed Exchange SP1 and I to am receiving a lot of event log errors.

    More specifically Event ID: 1053 Source: MSFTESQL-Exchange

    As mentioned above the content says "The system exception c0000005 was raised at 000007FEE7xxxxxx"

    Anyone had any joy fixing this error?

  138. james says:

    I think I have have found an answer, I had the Microsoft Filter Packs 2.0 (Beta) version installed from when I first deployed exchange 2010.

    The above link is to the newer 2.0 RTM Filter Packs, installing this updated the Beta version, and now the error has gone.

    I also followed a guide to recreate the exchange search database, and now I have an Event 4103 appear which says a master merge has completed.

    Hope this helps anyone with my issue.

  139. Gary Enticott says:

    Hi Guys,

    SP1 has its fair share of bugs (too many for a business critical core product for my liking), but, once you iron them out, its not bad.

    It would have been good if more testing was done, especially regarding Cross Site DAG, between two Subnets, as this doesnt seem to work (Case with MSFT ongoing).

  140. John Butler says:

    Have you guys collectively completely lost the plot? After spending the better part of an hour trying to track down the hot fixes required to even begin installing Service Pack 1 I am left completely amazed that you aren’t red-faced and embarrassed at putting us through this process of pain and misery.

    Since when did installing a service pack turn into a Sherlock Holmes style hunt for the correct hot fixes and forum trolling to try and figure out whether the correct patch is the Windows VISTA or WINDOWS 7 version..when I’m installing on Windows 2008 R2 server?

    You should be ashamed at yourselves for putting this service pack out there and requiring people to jump through the countless hoops (including having to request hot fixes ffs??) required to even get to the point when the service pack will install. What happened to the good old days of downloading a service pack…and … um… INSTALLING IT!!!!!!

    And then when it’s installed, all kinds of things break.

    I’m not a troll..just an extremely annoyed MS customer who is utterly dumbfounded at the collective madness behind this service pack release. Microsoft hang your heads in shame at the over-engineered, impossibly complex Borg you have become.

  141. Carsten17 says:

    @Bharat; I completely understand, but you also need to understand what powerful medium you have here and that "you started this"; You (Exch-team) posted very important updates like SP1 is available, and you gave some updates to the initial post with 4-5 updates and corrections. Then what? I am left to be searching high and low in order to plan a migration onto the "unknown"?

    In your table KB983440 is listed as required, in your footnote where you indicate changes, this one is not required (unless yes means no > See the table), then following the link to (pre reqs), this hotfix is still listed. This post was updated on 9/20, 5 days after this post tells us it’s not needed.

    Another example of an upgrade issue is that OWA custom work gets lost unless you manually protect it. Sure, for those of us that has done this before, many times over, we learn and we take the extra steps to land the project solidly.

    I want one single 10/6 “Exchange 2010 RTM Upgrade to SP1” step-by-step instructions like this one: but we need updates.

    The environment at hand has a planned maintenance window very soon and with 6 hours at hand the plan is to upgrade the environment to Exchange 2010 sp1 from 2010 RTM. We have no fall back options as soon as we start touching the MBX servers and it is pretty scary to see the many issues listed with no or little guidance from the source.

    I am on my way to bed now, probably dreaming about the empty GAL’s for the Outlook 2007 users I hear about, then I will wake up pondering about how to explain the to the Executive team that no-one is to be found in the GAL anymore and that the 120k users that was there yesterday just got scrubbed by SP1.

    Before “I go”, I will commend the Exchange team from the bottom of my heart; Exchange 2010 is the best communication product I have ever seen, and the way it behaves when configured properly is simply amazing. Performance totally rocks and the various features we are growing fond of include both CAS Arrays and DAG groups. What used to be heavy loads on Exchange servers now is handled with such ease I find myself logging on to the CAS array (any protocol) to see if it is really responsive with 20k active connections on a single box.

  142. Ibrahim Nore says:

    It is reported that after installing SP1 on Exchange Server 2010, the Calendar entries start disappearing after every BES Reboot.

    This issue is caused becaused of the changes in the Throttling Policy parameter EWSFindCountLimit from null to 1000 after installing SP1.

    RIM has released a fix to this issue two weeks back.

    Kindly visit the link

    Hope it helps.

  143. shawn says:


    I’ve heard that there has been some issues with the primary namespaces in within the exchange certificates…

    What are the best Practices from Microsoft regarding this ? Should the primary namespaces be listed on top of the exchange certificate or can they be at the bottom ?

    Thank you!



  144. Ibrahim Nore says:

    I believe the only guideline while issuing a SAN Certificate is that it should be Issued to the primary namespace with all other domain names added later. The Issued To: field should contain the primary domain FQDN. While the rest should be mentioned as additional domains while creating the certificate request and these domain names will be seen added below the primary domain name in the Subject Alternative Field in the Certificate Details.

  145. Gideon says:

    Installed SP1 without any problems. But there is a  problem/ bug in OWA

    When some users hit reply or new (email) the new email/reply page pops up. The next second internet explorer completely hangs. we have to kill internet explorer to fix the bug. Any ideas?

    Internet explorer 8 is used on windows xp(32) pc with amd processor(x2-64).

  146. Ibrahim Nore says:

    Just to post a note that Outlook Web App Pages do not get displayed correctly after upgrading to Service Pack 1 and when the OWA is published on UAG.

    Luckily Microsoft has documented a solution for this.

    Kindly go to the below link to modify the allowed URL Set in UAG:

    After doing the above steps, the display is back to normal.

  147. usftork says:

    I have one server that I had 2010 RTM installed and then upgraded to SP1.  2 of the 3 registered Powershell Snap-ins are missing.  I’ve installed 2 servers with SP1 (bypassing RTM) and all 3 of the registered PowerShell Snap-ins are loaded…

    This causes Symantec Mail Security for Microsoft Exchange to not install since it needs those PowerShell Snap-ins…Is there an easy way to add those?  I’ve seen references to re-install the Management Tools but it looks like the only way to do that is completely blow away Exchange…Any advice?

  148. usftork says:

    My issue is similar to what Dan said around Sept 1…Those same registry entries are missing on the server that had RTM and then SP1 applied.  Servers that started out as only SP1 have those registry entries correct…Any help on how to fix this?  Can I just insert the missing entries or is there something else more detailed that needs to be done?

  149. Martin says:

    Reading all these comments I don’t feel like installing SP1 at this point… Sounds like a big gamble to me… 50% chance to succeed… it’s just unprofessional to customers.

  150. Jim H says:

    Glad we’re still in the lab with Exchange 2010. Here’s hoping this stuff will be included in a Server 2008 "SP3" and 2008R2 SP1.  

    It just seems much more elegant to be able to take a box with a base OS and script the Exchange setup. Now we have to add all these pre-reqs and whatever reboots they take. We have hundreds of sites with bad network links and IT admins who are busy with with way more than just Exchange, so we need to package DVDs for them and keep it as simple and automated as possible.

  151. Ibrahim Nore says:

    We recently upgraded all our Exchange 2010 infrastructure to SP1 without a single hurdle.

    The Servers were upgraded in the order Cas-hub1, Cas-hub2, Dagnode1, Dagnode2.

    We had the hotfixes (64bit) for windows server 2008 R2 downloaded along with the latest FilterPack.

    I started by installing the FilterPack on each Server and then running the Setup wizard which checks for prerequisites. A restart was performed after every step just for my comfort. Finally the Setup allowed me to install the Exchange 2010 after all prereqs were met. I preferred this method rather than doing every step on my own, the Exchange 2010 SP1 setup is intelligent enough to tell you what it wants. I had configured HTTPS redirection on my default website so after the SP1 install I had to uncheck "Require SSL" on my Default Website. This brought my OWA back to life.

    We use thirdparty Certificates for Exchange, so I had no issues with my Certificate. No issues with EMC too.

    As we use UAG, the external OWA display was not functioning. So we had to add 4 new rules to UAG and the steps are outlined in Technet. I also recommend to install TMG SP1 + Update 1 for SP1 on UAG as it has support for Exchange 2010 SP1. If you use TMG for publishing do the upgrade on TMG.

    I also had to modify the RCA related parameter in the Default Throttling Policy to null so as to ensure that my BES server functions properly and no blackberry handheld was affected. The BES Server was restarted after the entire upgrade process was over.

    After the upgrade process was completed on all the Servers, I realised that Microsoft has released RollUp Update 1 for Exchange 2010 SP1 on Oct 8 which sorts out certain key issues, though I didn’t have any.

    But to be safe I installed that too on all the servers.

    I believe Exchange 2010 SP1 has major issues when installing or upgrading in a virtualised environment especially if the VMs are not as per MS best practices. Luckily we have not created a virtual environment for Exchange as yet. May be this saved us.

    Guys, SP1 Rocks…Microsoft has done a good job…Now its time to do some marketing for all these new features to our employees.

  152. Kyle says:

    That’s the fix for my issue.  Had to grab the registry entries from a working 2010 SP1 server.  Perhaps a rollup won’t break this?

    Again, I would bypass 2010 RTM and skip directly to installing SP1 fresh if you can.

  153. Tony I says:

    Stuck installing Rollup 1 for Exchange 2010 SP1 in my first CAS server. Install will not complete. Takes a long time and seems to hang at 90%. Any ideas? I haven’t started on the second CAS server or MB server yet. Very afraid to move forward at this point.

  154. randyR says:

    Running into some public folder replication issues (system folders – specifically not getting Free busy info to sync between legacy 2003 server and new 2010 servers). When examining replication info from the 2010 server boxes public folder tools snapin, I found that when double clicking on the "EX:/o=CompanyName/ou=First Administrative Group" and then clicking on the "Exchange General" tab, I get the error

    "The properties on this object have invalid data. If you click OK, default values will be used instead and will be saved if you do not change them before hitting Apply or OK on the property page. If you click cancel, the object will be displayed read-only and corrupted values will be retained."

    Click OK causes no changes to the fields shown. however, if I try to navigate away from the Exchange General tab, another error comes up stating "Some controls are not valid" and then continues to mention acceptable characters in the Alias field. The alias field is set to "Schedule+ Free Busy Information – First Administrative Group" The name contains no characters that are not listed as valid, so I’m confused and scared to click apply/ok. Anyone run into this? I should also mention that when the second error occurs, a red circle with an exclamation point appears next to the alias field.

    This is a production environment so I’m hesitant to make unknown changes, especially not being able to find the issue documented. I’ve found other issues related to the some controls are not valid, but don’t apply to this situation – mostly related to public folder size changes.

  155. martinp says:


    does anyone has also problem with installation of KB977020 hotfix on 2008 R2?

    The Windows6.1-KB977020-v2-x64.exe file says:

    "The version of this file is not compatible with the version of Windows you’re running. Check your computer’s system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."

    I tried to download also x86 and ia64 version just in case the links are messed up but none of them works.

    Why the hell should we install update for .NET 2 when there is already patched 3.5 SP1? And even if I have to why it doesn’t simply work? It was just a fresh installation, windows update, RTM installation and SP1 attempt (other prereqs intalled without problems)

    Seriously guys, I hope heads are already falling, this rushed process is too much even for Microsoft’s standards.

    It just seems to me that you adopted to the fact that many of your customers are waiting for SP1 of any of you product before even considering its deployment. Looks like you now release SP1s as RTMs – with fixed deadline so you can have a good cash-flow, right?

    Well tell those resposible execs we see through it and we don’t like it. If quality of SP1s sucks those people waiting for deployment will just wait for SP2s and then what – you adopt and plan SP2s with deadline?

  156. Joe says:


    just for feedback I upgraded our 2 internet facing servers over the weekend. I was expecting the worst but thankfully it all ran fine. The worst part was installing all the prerequisite patches from all over the place (I installed them all together and did one reboot before installing sp1).

    Anyone who needs to reduce downtime whilst these updates are done (which is everyone? right?) would appreciate the sp1 exe incorporating these new windows patches so there aren’t so many steps prior to installing and then testing the different clients (windows mobiles, iphones, outlook anywhere, free busy, autodiscover..)



  157. Rebeca says:

    Well I’m in the part of the process where you have to download de hotfixes; the ones that I have to request from CSS there’s no way to find them, the site seems to be down for several days now. How can I get those files?

  158. james says:

    the SP1 upgrade has more issue than the one without

    this SP1 is really screwed, man

  159. Roberto says:

    If you have Forefront installed, then disable it and stop all it’s services before you upgrade. Otherwise setup will try to restart it an waits indefinitely for completion. It’s also a good idea to do this when you install rollups.

    Toni said: Stuck installing Rollup 1 for Exchange 2010 SP1 in my first CAS server. Install will not complete. Takes a long time and seems to hang at 90%.

  160. laura says:

    Any reason why I should be putting off SP1? Also, should RU1 be applied right afterwards or should I install SP1 across all servers first then go back for RU1?

  161. mrflashy says:


    In response to the Server 2008 R2 Pre-Requisites I have a better link to download the working Patches for R2.

    Request the hotfix and you get an MSU back from Microsoft instead of the incorrect exe file as listed on the KB Article.


  162. shawn says:

    If you see SP1 for exchange, run fast and far.  At the end of the day exchange is a product people pay for and it simply does not work well.  Had many issues with sp1 install.  

  163. Keith_alabaster says:

    I have downloaded and installed the requested hotfixes except this one:

    Windows6.1-KB982867-v2-x64.msu (Win7)

    I can see it on MSDN but when clicking on download nothing appears to happen. Hopefully I am being incompetent but is there anything I might be doing wrong here?

  164. O. Spencer says:

    Attempting to install SP1 in Exchange 2010 test environment that does not have UM.  Is this required for SP1?  My production environment does use UM but I need to install it in a test area first.  Is the only solution to install the UM role?

  165. pslager says:

    Please check out my blog before running the upgrade part 1 is out now and part 2 should be finished shortly this may help those of you looking to perform the upgrade get an idea of some of the issues.

  166. Corbett says:

    Does the Windows 2008 R2 SP1 ease the prerequisites for this Exchange service pack and possibly increase the overall chances of success?

  167. Hans says:

    Buggiest upgrade I have ever done.

    If I knew, what I know now, I would hold of upgrading to SP1

  168. jamesc says:

    In regards to the Outlook 2003 and Shared calendars/accounts.  Recently ran into this problem and discovered that setting the 2003 Accounts to "Cached" mode on the client, allowing it to build the OST and then restarting the client (thats 2 restarts after setting the check box), I was able to access the folder.

    My testing included setting up a MAPI profile to access the shared account directly to verify permissions.  

    Once that was done, it was just trial and error till I found the right combo.  

    This is only a stop gap for our environment, as Cached mode is not something we want to do on our desktop systems so would appreciate a resolution.  However I dont think the problem is going to be on the exchange side, but more on the office client side.

    Our upgrade to Office 2010 is coming next fiscal year anyway, so it may be a moot point.  

  169. Lukas says:

    Great blog but maybe it would be appropriate to tell us too which services are required for successful installation because after I installed all hotfixes and prepared system w2k8r2 I’v got an error relating to disabled Microsoft .NET Framework NGEN v2.0.50727_X64 service. It was because Security Configuration Wizard gather it "not needed" and set the startup type to Disabled.



  170. Lin says:

    Does SP1 includes a fix which we can replicate free/busy information between Exchange 2003 organization and Exchange 2010 sp1 organization by using Inter-Org Replication tool?

    My understand is that we can replicate public folder but free/busy info is not.

    Appreciate for your response.

  171. Travis says:

    In case anyone is still having issues with the GAL being issue was due to the msExchQueryBase DN value that I set in ADSI for each user to restrict the GAL in OWA…this value isn’t used anymore in SP1 and causes Outlook to show an empty GAL..simply remove/clear the value

  172. Rune3 says:

    (comment edited, explicit words removed by blog team)

    Are u **** kidding me MS? I just installed hotfix rollup 4 and had a **** of issues, after uninstalling and FIXING it all I decided it might be time to update to SP1 – however after wasting a bunch of hours fixing the above mentioned ****  by MS I decided I might just google SP1 to see and then this comes up – AWESOME!!! well done MS you made my day easy – no need to update, means I don’t need to waste more time on your useless software. What happened to Exchange? It used to be better? At least I don’t recall wasting countless hours on fixing shit that should never have been released…. time to look for other email providers… I will run SP0 for the lifetime of 2010 and look for competitors offers.

  173. Gary D says:

    I bet the company that Rune is working for is so proud to have such a professional working for them. Though I agree MS missed the mark on this SP release, I do not belive showing ones ignorance with such unprofessional comments forced on all those who monitor this blog helps the situation one bit.

  174. Ru i ned says:

    Rune does indeed appear to be an Exchange knowledge powerhouse.  It sounds like a dark day for MS if he is going to " look for competitors offers"…MS could potentially lose TENS OF DOLLARS from this.  

  175. Ian Eiloart says:

    The x-originating-ip header is useful. I like to rate-limit users who are not on campus (because phishers are never on campus), but haven’t seen how to do this with Exchange users before.

    Unfortunately, you didn’t use "X-originating-ip" (note the capitalisation. Although "X-" has no special protection since rfc822 was obsoleted, it seems that there is some code out there that expects RFC5322 message headers to be either registered headers, or to begin "X-" (not "x-").

    Still, I’ll be able to rewrite (or strip) the offending headers before they leave campus.

  176. Dejan Foro says:

    And here is another serious SP1 problem to add to the list:

    Mailbox migration does not work from Exchange 2003 to Exchange 2001 SP1 where mailbox users have mailbox folder structure in an non/English language.

    The following error is reported:

    Error: MapiExceptionInvalidEntryId: Unable to SetSearchCriteria. (hr=0x80040107, ec=-2147221241)

    And accordin to this post it seems to affect quite a number of people

    In my case I am trying to move mailboxes from Exchange 2003 to Exchange 2010 SP1.

    Mailbox DB is clean, I can move the mailboxes to another Exchange 2003 database  as well as to Exchange 2010 RU4 machine.

    However move to Exchange 2010 SP1 does not work. Neither from Exchange 2003 or Exchange 2010 RU4.

    So it is clearly an SP1 bug.

    And I also have to concur with the frustrations that other colleagues are facing here.

    As someone dealing with Microsoft technologies for  17 years of which 12 years specialised on Exchange I have to say that I am highly dissapointed with the quality of both softwarea and partner support Microsoft is delivering lately, it really seems to be on its lowest ever. (Some smart manager probably had some creative ideas that money could be saved by outsourcing testing and support  to China ?)

    We as a MS partner company are taking heavy hits in the field because of this both in revenue and customer satisfaction.

    One recent example:

    I just got of a project where we failed to implmenet  Forefront TMG/Exchange Edge/Forefront Security 2010 for Exchange on a new server, because of numerous incompatibilities and bugs we encountered.  It is a bluntant example that Microsoft is not testing or capabale to ensure compatibiliy among its own products.

    Parnter Support also was a killer. They advised  that installing Exchange is not supported on TMG (althoguh TMG requries Exchange Edge as prerequisite). They were also unable to provide information in which order should SPs and updates for Exchange/TMG and Forefront to be installed and they refered me  to paid break/fix support where I shuld pay 500 USD for that information (and that was before install so noting broken to be fixed, just looking for general advice whcih falls under free partner support)

    End result: We had to fail back to an old ISA 2006 and 3rd party product. Customer wasted serious money for licencing,  we have lost 6 days of consulting which we can not charge meaning approx 10.000 USD direct damage for us in lost revenue plus travel and expenses .

    Now with the same customer we are having this problems with mailbox moves plus I just got informed by the customer that for some mailboxes iPhone syncronisation is failing on Exchange 2010 SP1 as well and that they are swamped with spam (Exchange 2010 SP1 plus Forefront security 2010 for Exchange)

    I could continue with similar examples for several other Microsoft products, but this is not place for it. I just wanted to give you a picture of pain we are getting in the field every time you guys at Microsoft mess up something with the sofware.  

    As a 6x Microsoft MVP I am stading embarrased in front of my customer and my emplyer and have to recommend things like failing back to old version and/or using products from other vendors.

    Bottom line: bad software kills business.

    The current testing process obviously has to be rediesigned to include at minimum testing with non English language settings and compatilbitiy with Microsoft s own products products that Exchange is supposed to integrate with namely ISA/TMG, Forefront Security For Exchange , Forefront DPM, OCS/LYNC.

    Otherwise you will have same as with Vista, people will simply back out, wait for next version or even switch to other vendors.  


    Dejan Foro

Comments are closed.