InformationWeek. com News, analysis and research for business technology professionals, plus peertopeer knowledge sharing. Engage with our community. Microsoft has released Service Pack 3 for Exchange Server 2010. This is a significant release that delivers some key functionality to customers such as support for. I posted a while back about Exchange 2007 SP3 being released. This weekend I finally got the time to do the upgrade myself. It went through seamlessly. IMPORTANT This article was published before the release of Exchange 2010 SP3 Update Rollup 3 Exchange 2007 SP3 Update Rollup 12 These update rollups fix the problem. Exchange 2. 01. 0 SP1 FAQ and Known Issues You Had Me At EHLOLast week we released Exchange Server 2. Service Pack 1. It has received some great feedback and reviews from customers, experts, analysts, and the Exchange community. The starting point for SP1 setupupgrade should be the Whats 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 were posting these here along with some workarounds so youre aware of them as you test and deploy SP1. Upgrade order. The order of upgrade from Exchange 2. RTM to SP1 hasnt changed from what was done in Exchange 2. Upgrade server roles in the following order Client Access server. Hub Transport server. Unified Messaging server. 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 2. RTM to Exchange 2. TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/91/09/metablogapi/image_thumb_7D0BD958.png' alt='Upgrade Microsoft Exchange 2007 Sp1 To Sp3 For Windows' title='Upgrade Microsoft Exchange 2007 Sp1 To Sp3 For Windows' />SP1 in the documenation. Exchange 2. 01. 0 SP1 Prerequisites. Exchange 2. 01. 0 SP1 requires the installation of 4 5 hotfixes, depending on the operating system Windows Server 2. Windows Server 2. R2. To install the Exchange 2. Upgrade Microsoft Exchange 2007 Sp1 To Sp3 For Windows' title='Upgrade Microsoft Exchange 2007 Sp1 To Sp3 For Windows' />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 2. Windows Vista share the same updates. Similarly, Windows Server 2. R2 and Windows 7 share the same updates. Make sure you select the x. Latest Windows 10 Redstone 4 PC test build adds more feature refinements. Microsoft is continuing to deliver lots of fixes and a few minor feature updates to. Exchange 2. 01. 0 servers. Update 21. 12. 01. Windows 2. 00. 8 R2 SP1 includes all the required hotfixes listed in this table 9. If youre installing Exchange 2. SP1 on a server running Windows 2. R2 SP1, you dont need to install these hotfixes separately. For a complete list of all updates included in Windows 2. R2 SP1, see Updates in Win. WS0. 8R2 SP1. xls. Heres a matrix of the updates required, including download locations and file names. Hotfix. Download. Windows Server 2. Windows Server 2. R2. Windows 7 Windows Vista. A. NET Framework 2. Multi App. Domain application stops responding when you run the application. MSDNor Microsoft Connect. Windows. 6. 0 KB9. CBS VistaWin. 2K8Windows. KB9. 79. 74. 4 x. CBS Win. 7Win. 2K8 R2N. A. 9. 83. 44. 0An ASP. NET 2. 0 hotfix rollup package is available for Windows 7 and for Windows Server 2. R2. Request from CSSN. A. Yes. N. A. 9. 77. AD RMS clients do not authenticate federated identity providers in Windows Server 2. Windows Vista. Without this update, Active Directory Rights Management Services AD RMS features may stop working. Request from CSSSelect the download for Windows Vista for the x. N. A. N. A. 9. 79. Two issues occur when you deploy an ASP. NET 2. 0 based application on a server that is running IIS 7. IIS 7. 5 in Integrated mode. MSDNWindows. 6. 0 KB9. VistaN. A. N. A. FIX Argument. Null. Exception 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. Windows. 6. 0 KB9. N. A. N. A. 9. 77. RPC over HTTP clients cannot connect to the Windows Server 2. RPC over HTTP servers that have RPC load balancing enabled. Request from CSSSelect the download for Windows Vista x. N. A. N. A. 9. 79. An update is available to remove the application manifest expiry feature from AD RMS clients. Download Center. N. A. Windows. 6. 1 KB9. N. A. 9. 82. 86. 7WCF services that are hosted by computers together with a NLB fail in. NET Framework 3. 5 SP1. MSDNWindows. 6. 0 KB9. VistaWindows. 6. KB9. Win. 7X8. 6 Windows. KB9. 82. 86. 7 v. Win. 7 x. 64 Windows. KB9. 82. 86. 7 v. Win. 79. 77. 02. 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. x. 64 Windows. KB9. 77. 02. 0 v. Windows. 6. 1 KB9. X8. 6 Windows. 6. KB9. 77. 02. 0 v. 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 MSDNConnect, 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 2. SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft. Prerequisite download pages linked from SP1 Setup are unavailable. When installing Exchange Server 2. 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. Were working to update the linked content. Meanwhile, please refer to the Tech. Net article Exchange 2. Prerequisites to download and install the prerequisites required for your server version the hotfixes are linked to in the above table, but youll still need to install the usual prerequisites such as. Net Framework 3. 5 SP1, Windows Remote Management Win. RM 2. 0, and the required OS components. The Missing Exchange Management Shell Shortcut. Some customers have reported that after upgrading an Exchange Server 2. Exchange 2. 01. 0 SP1, the Exchange Management Shell shortcut is missing from program options. Additionally, the. EMS may also be missing. Were actively investigating this issue. Meanwhile, heres a workaround Verify that the following files are present in the Exchange. Install. Pathbindirectory. Common. Connect. Functions. Common. Connect. Functions. Connect Exchange. Server help. xml Connect. Windows Server 2008 Activation Keygen Idm. Functions. ps. 1 Connect. Functions. strings. Remote. Exchange. Remote. Exchange. NOTE If these files are missing, you can copy the files from the Exchange Server 2. Service Pack 1 installation media to the Exchange. Install. Pathbin directory. These files are present in the setupserverrolescommon folder. Click Start Admiinistrative. Tools, right click Windows Power. Shell Modules, select Send to Desktop as shortcutGo to the Properties of the shortcut and on Target replace the path to C WINDOWSsystem. Windows. Power. Shellv. C Program FilesMicrosoftExchange ServerV1. Remote. Exchange. Connect Exchange. Server autoNote if the Exchange installation folder or drive name is different than the default, you need to change the path accordingly. Upgrading Edge Transport on Forefront Threat Management Gateway TMG and Forefront Protection for Exchange 2. If you upgrade a server with the Edge Transport server role running with Fore. Front Threat Management Gateway TMG and Fore. Front Protection for Exchange FPE enabled for SMTP protection, the Fore.