UC Unleashed

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

• Update Rollup 3 for Exchange Server 2007 SP3 (2492691)

If you’re running Exchange Server 2007 SP3, you need to apply Update Rollup 3 for Exchange 2007 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 3:

1. 2498066 “Insufficient system resources exist to complete the requested service” error message when you try to extend database files in an Exchange Server 2007 environment
2. 2497679 A meeting request may not open correctly after you disable the “Display sender’s name on messages” option in the EMC of Exchange Server 2007 SP2 or SP3
3. 2493529 Event ID 1160 is logged and the Microsoft Exchange Information Store service randomly stops responding on an Exchange Server 2007 server
4. 2492384 A meeting response status from an external attendee may be incorrect if you send the meeting request from an Exchange Server 2007 environment
5. 2490788 A calendar synchronization times out when you use ActiveSync to synchronize with an Exchange Server 2007 mailbox on a mobile device
6. 2489898 An item is removed unexpectedly from a public folder in an Exchange Server 2007 environment
7. 2480197 The “Require SSL” setting is unexpectedly unselected on the RPC virtual directory on an Exchange Server 2007 server
8. 2479939 The “ScheduleOnlyDuringWorkHours” property of a resource mailbox may not function as expected in an Exchange Server 2007 environment
9. 2477139 DTMF inputs are not accepted by a UM auto attendant while the greeting message is playing in an Exchange Server 2007 environment
10. 2470759 The “Test-Replicationhealth” cmdlet fails on a stretched cluster in an Exchange Server 2007 SP3 CCR environment
11. 2461537 The Microsoft.Exchange.Search.ExSearch.exe process consumes 100% CPU after you apply Update Rollup 1 or Update Rollup 2 for Exchange Server 2007 SP3 on the passive node of a SCC
12. 2457838 “554 5.6.0” NDR message when you send an email message to an Exchange Server 2007 mailbox from a Macintosh computer
13. 2450078 The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment
14. 2448291 “Object has been corrupted and it is in an inconsistent state” warning message when you view a transport rule on an Exchange Server 2007 SP3 server
15. 2445129 The W3WP.exe process may crash when a WebDAV client connects to an Exchange Server 2007 server
16. 2418993 The Edgetransport.exe process crashes when you close a Telnet session before you receive an SMTP banner in an Exchange Server 2007 environment
17. 2410330 The EdgeTransport.exe process crashes if the pipeline tracing feature is enabled together with a redirect transport rule in an Exchange Server 2007 environment
18. 2408435 “Computer account for ‘SMTPSVC/’ not found in Active Directory.” error message in an Exchange Server 2007 environment
19. 2394853 The returned URL is incorrect when you use the WebDAV “X-MS-ENUMATTS” method to enumerate an attachment in an Exchange Server 2007 environment
20. 2294143 Duplicate read receipts are sent when using a POP3 client or an IMAP4 client in an Exchange Server 2007 environment
21. 2267661 Some body parts of a message are displayed as attachments when an Exchange Server 2007 user sends the message by using a third-party mail client
22. 2032592 VSS backup fails on a passive node of an Exchange Server 2007 CCR cluster and Event ID 2034 is logged
23. 982714 The values of total items that are returned by running the “Export-ActiveSyncLog” cmdlet on an Exchange Server 2007 server are incorrect
24. 979338 Fax communication sessions are dropped by an Exchange Server 2007 Unified Messaging server
25. 955480 A meeting request is stamped as Busy instead of Tentative when it is sent from an external user to an Exchange Server 2007 user

Download the rollup here. Microsoft has announced that Update Rollup 4 for Exchange Server 2007 SP3 is scheduled for May 2011.

Microsoft also announced that there are no plans to release further updates for Exchange Server 2007 SP2. Customers are advised to upgrade to SP3.

Installation Notes:

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.

Note to Forefront users:

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

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

• Update Rollup 3 for Exchange Server 2010 SP1 (2492690)

If you’re running Exchange Server 2010 SP1, you need to apply Update Rollup 3 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 3:

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

Download the rollup here. The Update Rollup will be available via Microsoft Update on March 22nd 2011.

Microsoft has announced that Update Rollup 4 for Exchange Server 2010 SP1 is expected to be released in May 2011.

Installation Notes:

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.

Note to Forefront users:

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

Microsoft has released Service Pack 1 (SP1) for Exchange Server 2010. See the Release Notes for Exchange 2010 SP1 for more information, including a list of known issues.

The 522MB download is just like RTM – a full install package. Existing installations can be upgraded, as new installs can be completed with the Service Pack integrated.

What’s New in Exchange 2010 SP1 has a comprehensive list of the changes and enhancements, including:

New Deployment Functionality

1. During an Exchange 2010 SP1 installation, you can now select a new option to install the required Windows roles and features for each selected Exchange 2010 SP1 server role. For more information, see New Deployment Functionality in Exchange 2010 SP1.

Client Access Server Role Improvements

1. Federation Certificates
2. Exchange ActiveSync
3. SMS Sync
4. Server-Side Information Rights Management Support
5. Outlook Web App Improvements
6. Reset Virtual Directory
7. Client Throttling Policies

Improvements in Transport Functionality

1. MailTips access control over organizational relationships
2. Enhanced monitoring and troubleshooting features for MailTips
3. Enhanced monitoring and troubleshooting features for message tracking
4. Message throttling enhancements
5. Shadow redundancy promotion
6. SMTP failover and load balancing improvements
7. Support for extended protection on SMTP connections
8. Send connector changes to reduce NDRs over well-defined connections

Permissions Functionality

1. Database scope support
2. Active Directory split permissions
3. Improved user interface

Exchange Store and Mailbox Database Functionality

1. With the New-MailboxRepairRequest cmdlet, you can detect and repair mailbox and database corruption issues.
2. Store limits were increased for administrative access.
3. The Database Log Growth Troubleshooter (Troubleshoot-DatabaseSpace.ps1) is a new script that allows you to control excessive log growth of mailbox databases.
4. Public Folders client permissions support was added to the Exchange Management Console (EMC).

Mailbox and Recipients Functionality

1. Calendar Repair Assistant supports more scenarios than were available in Exchange 2010 RTM.
2. Mailbox Assistants are now all throttle-based (changed from time-based in Exchange 2010 RTM).
3. Internet calendar publishing allows users in your Exchange organization to share their Outlook calendars with a broad Internet audience.
4. Importing and exporting .pst files now uses the Mailbox Replication service and doesn’t require Outlook.
5. Hierarchical address book support allows you to create and configure your address lists and offline address books in a hierarchical view.
6. Distribution group naming policies allow you to configure string text that will be appended or prepended to a distribution group’s name when it’s created.
7. Soft-delete of mailboxes after move completion.

High Availability and Site Resilience Functionality

1. Continuous replication – block mode
2. Active mailbox database redistribution
3. Enhanced datacenter activation coordination mode support
4. New and enhanced management and monitoring scripts
5. Exchange Management Console user interface enhancements
6. Improvements in failover performance

Messaging Policy and Compliance Functionality

1. Provision personal archive on a different mailbox database
2. Import historical mailbox data to personal archive
3. Delegate access to personal archive
4. New retention policy user interface
5. Support for creating retention policy tags for Calendar and Tasks default folders
6. Opt-in personal tags
7. Multi-Mailbox Search preview
8. Annotations in Multi-Mailbox Search
9. Multi-Mailbox Search data de-duplication
10. WebReady Document Viewing of IRM-protected messages in Outlook Web App
11. IRM in Exchange ActiveSync for protocol-level IRM
12. IRM logging
13. Mailbox audit logging

Unified Messaging Server Role Improvements

1. UM reporting
2. UM management in the Exchange Control Panel
3. Cross-Forest UM-enabled mailbox migration
4. Outlook Voice Access improvements
5. Caller Name Display support
6. Test-ExchangeUMCallFlow cmdlet
7. New UM Dial Plan wizard
8. Office Communications Server “14” Support
9. Secondary UM dial plan support
10. UM language packs added
11. Call answering rules improvements
12. Unified Communications Managed API/speech platform improvements
13. UM auto attendant update

Audit Logging Improvements

1. Improvements in administrator audit logging
2. New mailbox audit logging

Support for Coexistence with Exchange Online

1. Migration of UM-enabled mailboxes
2. IRM support for coexistence
3. Remote Mailboxes
4. Transport

Support for Multi-Tenancy

Upgrade from Exchange 2010 RTM to Exchange 2010 SP1 includes details you should know before upgrading, as well as how to upgrade including upgrading DAG members.

Equally important is Exchange 2010 Prerequisites, which details which hotfixes you need to install before doing a clean install of Exchange 2010 SP1, or when upgrading an RTM installation. Be prepared, as several of the 2008 R2 hotfixes require a reboot.

Download the Service Pack here.

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

• Update Rollup 10 for Exchange Server 2007 SP1 (981407)

If you’re running Exchange Server 2007 SP1, you need to apply Update Rollup 10 for Exchange 2007 SP1 to address the issues listed below. If you’re running Exchange Server 2007 SP2 or later, this update does not apply to you.

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 10:

1. 981832 MS10-024: Vulnerabilities in Microsoft Exchange and Windows SMTP Service could allow denial of service

Download the rollup here.

Installation Notes:

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.

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

• Update Rollup 3 for Exchange Server 2010 (981401)

If you’re running Exchange Server 2010, you need to apply Update Rollup 3 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 3:

1. 981832 MS10-024: Vulnerabilities in Microsoft Exchange and Windows SMTP Service could allow denial of service
2. 981664 RPC clients or MAPI on the Middle Tier clients may not receive responses from the mailbox server role on an Exchange 2010 server

Download the rollup here.

Installation Notes:

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.

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

• Update Rollup 4 for Exchange Server 2007 SP2 (981383)

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

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

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

1. 981832 MS10-024: Vulnerabilities in Microsoft Exchange and Windows SMTP Service could allow denial of service
2. 981706 Exchange 2007 SP2 Update Rollup 1 or Exchange 2007 SP2 Update Rollup 2 does not install on a Spanish version of Exchange Server 2007 SP2
3. 980639 A user can only set the time zone to Bucharest in OWA after you update Exchange Server 2007 Service Pack 1 to Exchange Server 2007 Service Pack 2

Download the rollup here.

Installation Notes:

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.

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

• Update Rollup 5 for Exchange Server 2007 SP1 (953467)

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

Remember, you only need to download the latest update for the version of Exchange that you’re running. RTM updates can’t be installed on SP1 and vice versa.

Rollup 4 for Exchange Server 2007 SP1 supersedes the following:

1. 945684 Update Rollup 1 for Exchange Server 2007 Service Pack 1
2. 948016 Update Rollup 2 for Exchange Server 2007 Service Pack 1
3. 949870 Update Rollup 3 for Exchange Server 2007 Service Pack 1
4. 952580 Update Rollup 4 for Exchange Server 2007 Service Pack 1

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

1. 925371 Domino users cannot find meeting request attachments that are sent from Exchange 2007 users
2. 939037 By default, managed content settings apply to the root folder and all subfolders in an Exchange 2007 environment
3. 949722 Event ID 800 does not include the user name of users who ran the Get-MessageTrackingLog command in an Exchange 2007 environment
4. 949893 You cannot create a new mailbox or enable a mailbox in an Exchange Server 2007 environment on February 29, 2008
5. 949895 Exchange Management Shell crashes (stops responding), and Event ID 1000 is logged when you perform a cross-forest migration from Exchange Server 2003 to Exchange Server 2007
6. 949901 Exchange 2007 users cannot send e-mail messages to a mail-enabled public folder in a mixed Exchange 2003 and Exchange 2007 environment
7. 949968 Unified Messaging does not handle the diversion header correctly in Exchange Server 2007 Service Pack 1
8. 950272 The formatting of a plain text message is incorrect when you print the plain text message by using Outlook Web Access in an Exchange Server 2007 environment
9. 951267 An exception occurs in Exchange Management Console when you preview AddressList in an Exchange Server 2007 environment
10. 951273 The received date and the received time of IMAP messages are changed to the time of migration after you migrate mailboxes to an Exchange 2007 Service Pack 1-based server
11. 951505 You may receive an error message when you run the Update-SafeList cmdlet in an Exchange 2003 and Exchange 2007 mixed environment
12. 951564 Exchange 2007 Update Rollup 5 supports the addition of new items to context menus in Outlook Web Access 2007
13. 951710 You receive error messages or warnings when you change an Active Directory schema so that the Company property supports more than 64 characters
14. 952097 Update Rollup 5 for Exchange 2007 Service Pack 1 introduces events 12003 which can be used to clarify ambiguous Event messages
15. 952583 Japanese DBCS characters are corrupt when you reply to a message or forward a message in an Exchange Server 2007 environment
16. 953619 A public folder conflict message cannot be delivered, and event error 1016 is logged, when the public folder name contains DBCS characters in an Exchange Server 2007 Service Pack 1 environment
17. 953787 You receive an error message when you try to move Exchange 2000 mailboxes or Exchange 2003 mailboxes from one forest to an Exchange 2007 server that is located in another forest by using the Move-Mailbox command
18. 953840 Event ID 5000 occurs, and the IMAP4 service may crash, on a server that is running Exchange Server 2007 with Service Pack 1 when you use a third-party application to migrate POP3 and IMAP4 users
19. 954036 Hidden folders or files are listed when you view a UNC file server by using OWA in an Exchange 2007 environment
20. 954195 The task originator is not notified of task changes and task progress in an Exchange Server 2007 environment
21. 954197 Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters
22. 954270 Message class changes during conversion when a digitally signed Message Disposition Notification is received by a server that is running Exchange Server 2007 Service Pack 1
23. 954451 An appointment item cannot be opened by a CDOEX-based application if the item is saved by Exchange Web Service together with the Culture property in Exchange Server 2007
24. 954684 You cannot use an Outlook 2007 client to display or download an attachment when you access a message that includes an inline attachment from Exchange Server 2007
25. 954810 An Exchange 2007 room mailbox stops processing requests after the resource booking assistant receives a delegated meeting request from an Exchange 2003 user
26. 954887 You cannot add a Mail User or a Mail Contact to the Safe Senders list in Exchange 2007 by using OWA Client
27. 955001 Error message when you use the IMAP protocol to send a SEARCH command that has the CHARSET argument on an Exchange 2007 server: “BAD Command Argument Error”
28. 955196 Log files are not copied to the target server in a standby continuous replication environment in Exchange Server 2007
29. 955429 VSS backup application causes the Information Store service to crash repeatedly on an Exchange 2007 Service Pack 1-based server
30. 955460 The start time and the end time of a meeting request are incorrect when a delegate uses Exchange Web Service to send the request in an Exchange 2007 environment
31. 955480 Meeting requests from external senders are displayed as Busy instead of Tentative in an Exchange 2007 environment
32. 955599 Event ID 10 messages fill up the Application log on an Exchange 2007 CAS server if an Exchange Server 2003 mailbox owner makes an Exchange Web Service call
33. 955619 A user cannot access the mailbox by using a POP client or an IMAP client through Client Access Server in an Exchange 2007 environment
34. 955741 A message stays in the Outbox, and the message is resent until it is deleted manually on Windows Mobile 6.1-based devices in an Exchange 2007 Service Pack 1 CAS proxying scenario
35. 955946 If a private message is submitted by a SMTP sender, the sender receives an NDR message from the Exchange 2007 server
36. 955989 The SPN registration of a cluster fails, and Error event IDs 1119 and 1034 are logged in an Exchange Server 2007 Service Pack 1 environment
37. 956199 The last character of a user’s Chinese display name is truncated in the Offline Address Book on an Exchange 2007 server
38. 956319 The W3wp.exe process may crash on an Exchange 2007 CAS server after you use Entourage to send a message that is larger than 48 KB
39. 956573 Event ID 1032 is not logged in the Application log when users send e-mail messages while they are logged on to Outlook Web Access as another user in Exchange 2007
40. 956582 Exchange Server 2007 Update Rollup 3 does not update the Outlook Web Access Logon.aspx file after you modify the file
41. 956613 The W3wp.exe process intermittently stops responding and Event ID 1000 is logged in Exchange Server 2007 Service Pack 1
42. 956709 Some recurring meetings may be missing when you view the meetings using Outlook Web Access in Exchange Server 2007
43. 957002 The Edgetransport.exe process may crash intermittently on a server that is running Exchange Server 2007 Service Pack 1
44. 957137 The reseed process is unsuccessful on the CCR passive node after you restore one full backup and two or more differential backups to the CCR active node
45. 957813 A Non-Delivery Report is generated when you try to send a high priority message that is larger than 250 KB in an Exchange Server 2007 Service Pack 1 environment
46. 957978 The OAB generation is unsuccessful and Event IDs 9328 and 9373 are logged in the Application log in a Windows Server 2008-based Exchange 2007 Single-Copy cluster environment
47. 958855 The Edge Transport service crashes repeatedly, and an event error 1000 is logged repeatedly on a server that is running Exchange Server 2007 Service Pack 1
48. 958856 Event ID: 7012 occurs when you search message tracking logs on an Exchange Server 2007-based server

Download the rollup here. It is scheduled to be available via Windows Update on December 9th.

Installation Notes:

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.

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

• Update Rollup 4 for Exchange Server 2007 SP1 (952580)

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

Remember, you only need to download the latest update for the version of Exchange that you’re running. RTM updates can’t be installed on SP1 and vice versa.

Rollup 4 for Exchange Server 2007 SP1 supersedes the following:

1. 945684 Update Rollup 1 for Exchange Server 2007 Service Pack 1
2. 948016 Update Rollup 2 for Exchange Server 2007 Service Pack 1
3. 949870 Update Rollup 3 for Exchange Server 2007 Service Pack 1

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

1. 942649 Description of the commands that support the UseRusServer option that is imported in Update Rollup 4 for Exchange Server 2007 Service Pack 1
2. 944831 You cannot configure Exchange Server 2007 so that the simple display name appears in outgoing messages
3. 945854 A meeting reminder is still active when you configure Outlook to send no reminders to an Exchange Server 2007 user
4. 945870 TAB symbols may be converted incorrectly to spaces in Exchange Server 2007
5. 948896 Certificates that contain wildcard characters may not work correctly on an Exchange 2007 Service Pack 1-based server
6. 948897 An attachment incorrectly appears as the body of the e-mail message in an Exchange Server 2007 environment
7. 948923 Users do not receive information in DSN messages in Exchange Server 2007 with Service Pack 1
8. 949512 An embedded message is removed from the attachment list on Exchange Server 2007 if the embedded message subject ends with .com, .exe, or any other blocked extension
9. 949782 An In-Policy request that is forwarded to delegate appears as an Out-Of-Policy request if a user submits an In-Policy meeting request against a room mailbox of Exchange Server 2007
10. 949858 The provisioning process is unsuccessful when you use Identity Lifecycle Manager (ILM) 2007 to provision user objects to an Exchange Server 2007 resource forest
11. 949926 Error when you use an IMAP4 client or a POP3 client to log on to a delegate mailbox of Exchange Server 2007: “800cccd1”
12. 950076 After you move a mailbox from Exchange Server 2003 to Exchange Server 2007 Service Pack 1, you cannot edit rules in Outlook Web Access
13. 950081 Error message when users use an SMTP client to send e-mail messages in Exchange Server 2007 Service Pack 1: “454 4.7.0 Temporary authentication failure”
14. 950138 You are prompted for your credentials three times and you receive an error message when you use the Outlook Anywhere feature to connect to an Exchange Server 2007 Service Pack 1-based server that is running Windows Server 2008
15. 950198 You can enable AfterConversion snapshot for all messages if pipeline tracing and Content Conversion Tracing are enabled
16. 950235 The IMAP4 or POP3 worker process may stop responding on an Exchange 2007 CAS role when you use an IMAP4 client or a POP3 client to connect the Exchange 2007 CAS role to your mailbox
17. 950409 The reminder is triggered earlier than expected when an Exchange Server 2007 server receives an iCalendar meeting request message over an SMTP server
18. 950622 Messages are converted to a very small font size in Outlook Web Access and in Outlook 2003 when you use Exchange Server 2007
19. 950976 Event ID 115 may be logged intermittently on a computer that is running Exchange Server 2007 with Service Pack 1
20. 951067 Event ID 7034 may be logged in the Application log in Exchange Server 2007 when an MAPI application tries to access a mailbox in a certain way
21. 951156 The message body of appointments is garbled after you use a mobile device to synchronize appointments that were created in Outlook Web Access on Exchange 2007
22. 951251 A MAPI application does not work correctly if Exchange 2007 is installed on a Windows Server 2008 server
23. 951594 The W3svc log reports the incorrect number of attachments on an Exchange Server 2007 server that has deployed Exchange ActiveSync Service (EAS)
24. 951747 An error occurs when you use the Export-mailbox or Restore-mailbox command to migrate certain mailboxes on Exchange Server 2007: “error code -1056749164”
25. 951864 Some users must enter their credentials when they access rights-protected messages even though you have deployed the Rights Management Services (RMS) prelicensing agent on an Exchange Server 2007 Service Pack 1-based server
26. 952152 The Autodiscover service for ActiveSync in an Exchange 2007 environment does not work for users in sites that do not have the ExternalURL property set
27. 952250 You encounter a long delay for each mailbox when you run the “Move-Mailbox” or “Set-Mailbox” command on an Exchange Server 2007 computer
28. 952682 Log file drives on the SCR target may eventually fill up and cause replication failure in Exchange Server 2007 Service Pack 1
29. 952924 Error message when Exchange users try to access public folders that are hosted on Exchange Server 2003 by using Outlook Web Access for Exchange Server 2007: “Outlook Web Access is unable to open public folders”
30. 953312 The “Open Message In Conflict” button is not available in the conflict notification message for Exchange Server 2007 users
31. 954058 You can change the method for transfer encoding after you apply Update Rollup 5 for Exchange Server 2007 Service Pack 1
32. 954205 Event ID 1113 is logged in the Application log on a Unified Messaging (UM) server when users contact the UM server by using secured connections
33. 954237 The IMAP service crashes intermittently on Exchange 2007, and Event ID 5000 is logged
34. 955208 Event ID 5000 occurs when the Exchange IMAP4 worker process crashes intermittently in Exchange Server 2007
35. 956775 CopyItem and MoveItem Operations in Exchange Web Services can return the Item ID after you install Update Rollup 4 for Exchange Server 2007 Service Pack 1
36. 957133 Description of improvements in functionality that occur in Exchange Web Services operations after you install Update Rollup 4 for Exchange Server 2007 Service Pack 1

Download the rollup here.

Installation Notes:

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.