Microsoft has released Service Pack 3 (SP3) for Exchange Server 2007.
The 800+MB download is just like SP1 – a full install package that incorporates the Service Pack. Existing installations can be upgraded, as new installs can be completed with the Service Pack integrated.
Service Pack 3 also includes support for running Exchange on Windows Server 2008 R2 – a much sought after feature, and for running the Management tools on Windows 7.
Update: I guess it would help if I included a download link.
Microsoft has released the following update rollup for Exchange Server 2010:
- Update Rollup 4 for Exchange Server 2010 (981401)
If you’re running Exchange Server 2010, you need to apply Update Rollup 4 for Exchange 2010 to address the issues listed below.
Remember, you only need to download the latest update for the version of Exchange that you’re running.
Here is a list of the fixes included in update rollup 4:
- 979342 An attachment is not visible when an Exchange Server 2010 user opens a signed mail message by using Outlook 2003
- 979517 You cannot send a message to a Dynamic Distribution Group in a mixed Exchange Server 2007 and Exchange Server 2010 environment
- 979790Â An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox
- 979801 An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
- 979810 You cannot connect an Exchange Server 2010 mailbox by using a MAPI client
- 979848 Event ID 1066 is logged and you cannot move a mailbox from an Exchange Server 2003 server to an Exchange Server 2010 server
- 979862 Event ID 4999 and Event ID 7031 are logged when you move a mailbox to an Exchange Server 2010 server
- 979921 You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server
- 980149Â The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
- 980353 A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
- 980354 “MAPI_E_INVALID_PARAMETER” error message when you copy email messages from an Exchange Server 2010 mailbox
- 980364 Microsoft Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
- 980701 An Exchange Server 2010 mailbox user receives a NDR error message when the user sends an email message to multiple internal users
- 980852Â The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
- 981033 Error message when you expand the Microsoft Exchange On-Premises node in the EMC of Exchange Server 2010
- 981961 Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
- 982209 Some embedded messages are corrupted when they are contained in a message that is sent from an Exchange Server 2010 mailbox address
- 982378Â A delegate receives only one meeting request when someone sends a meeting request to several principalsÂ in an Exchange Server 2010 RU1 or later environment
- 982944Â The msExchVersionÂ attribute value of a user is stamped incorrectly after you run the Enable-MailUser cmdlet to mail-enable the user
- 983200 The .xls file as an attachment is empty when you access an Exchange Server 2010 mailbox by using OWA
- 983631 “redirect it to people or distribution list” rule does not work on an Exchange Server 2010 mailbox address
- 2084061 A user intermittently fails to access an Exchange Server 2010 mailbox after the mailbox is moved
Download the rollup here.
If you havenâ€™t installed Exchange Server yet, you can use the info at Quicker Exchange installs complete with service packs and rollups to save you some time.
Microsoft Update can’t detect rollups for Exchange 2010 servers that are members of a Database Availability Group (DAG). See the post Installing Exchange 2010 Rollups on DAG Servers for info, and a script, for installing update rollups.
Update Rollups should be applied to Internet facing Client Access Servers before being installed on non-Internet facing Client Access Servers.
If youâ€™re installing the update rollup on Exchange servers that donâ€™t have Internet access, see â€œInstalling Exchange 2007 & 2010 rollups on servers that donâ€™t have Internet accessâ€ for some additional steps.
Also, the installer and Add/Remove Programs text is only in English – even when being installed on non-English systems.
Categories: Exchange Server Database Availability Group (DAG), Exchange Management Console (EMC), Exchange Management Shell (EMS), Exchange Server 2007, Exchange Server 2010, IMAP4, MAPI, Outlook, Outlook Web Access/App (OWA), Public Folders, Update Rollups