Microsoft earlier in the day released twelve security bulletins addressing 57 vulnerabilities in Microsoft Windows, Office, Internet Explorer, Exchange and .NET Framework.
In the, Exchange releated update security bulletin MS13-012 (KB 2809279) rolls out:
Update Rollup 6 for Exchange Server 2010 Service Pack 2, contains a number of customer reported and internally found issues:
- "2489941 "legacyExchangeDN" value is shown in the "From" field instead of the "Simple Display Name" in an email message in an Exchange Server 2010 environment
- 2779387 Duplicated email messages are displayed in the Sent Items folder in a EWS-based application that accesses an Exchange Server 2010 Mailbox server
- 2751581 OAB generation fails with event IDs 9126, 9330, and either 9338 or 9339 in an Exchange Server 2010 environment
- 2784081 Store.exe process crashes if you add certain registry keys to an Exchange Server 2010 Mailbox server," the exchange team informs.
And, the Update Rollup 10 for Exchange Server 2007 Service Pack 3 released today contains kb2783779 -- "a hidden user is still displayed in the Organization information of Address Book in OWA in an Exchange Server 2007 environment."
For DST changes, check at http://www.microsoft.com/time.
Additionally, the company has also released Exchange Server 2010 Service Pack 3, a fully slipstreamed version of Exchange 2010. Below is a list of new features and capabilities:
- "Coexistence with Exchange 2013:Customers who want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.
- Support for Windows Server 2012: With SP3, you can install and deploy Exchange Server 2010 on computers that are running Windows Server 2012.
- Support for Internet Explorer 10: With SP3, you can use IE10 to connect to Exchange 2010.
- Customer Requested Fixes: All fixes contained within update rollups released before SP3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing" informs Exchange team.
The SP3 in addition to above also resolves follings issues:
- "2552121 You cannot synchronize a mailbox by using an Exchange ActiveSync device in an Exchange Server 2010 environment
- 2729444 Mailboxes are quarantined after you install the Exchange Server 2010 SP2 version of the Exchange Server 2010 Management Pack
- 2778100 Long delay in receiving email messages by using Outlook in an Exchange Server 2010 environment
- 2779351 SCOM alert when the Test-PowerShellConnectivity cmdlet is executed in an Exchange Server 2010 organization
- 2784569 Slow performance when you search a GAL by using an EAS device in an Exchange Server 2010 environment
- 2796950 Microsoft.Exchange.Monitoring.exe process consumes excessive CPU resources when a SCOM server monitors Exchange Server 2010 Client Access servers
- 2800133 W3wp.exe process consumes excessive CPU and memory resources on an Exchange Client Access server after you apply Update Rollup 5 version 2 for Exchange Server 2010 SP2
- 2800346 Outlook freezes and high network load occurs when you apply retention policies to a mailbox in a mixed Exchange Server 2010 SP2 environment
- 2810617 Can't install Exchange Server 2010 SP3 when you define a Windows PowerShell script execution policy in Group Policy
- 2787500 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010
- 2797529 Email message delivery is delayed on a Blackberry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2
- 2800080 ErrorServerBusy response code when you synchronize an EWS-based application to a mailbox in an Exchange Server 2010 environment."
- Exchange Server 2010 Service Pack 2 Update Rollup 6
- Exchange Server 2007 Service Pack 3 Update Rollup 10
- Exchange Server 2010 Service Pack 3
Update: Microsoft has now published an official support document to detail workarounds for iOS 6.1 Exchange bug including blocking & throttling iOS users stating that it's working with Apple to resolve the issue and recommended customers "open an Enterprise Support case with Apple."
Microsoft explains in knowledge base article that "When a user syncs a mailbox by using an iOS 6.1-based device, Microsoft Exchange Server 2010 Client Access server (CAS) and Mailbox (MBX) server resources are consumed, log growth becomes excessive, memory and CPU use may increase significantly, and server performance is affected. Additionally, Office 365 Exchange Online users receive an error message that resembles the following on an iOS 6.1-based device: Cannot Get Mail, The connection to the server failed."
Check out KB2814847 for more details.
Update 02/23: A new version 2.0 of the free PST Capture tool that allows you to hunt down PST files on client computers across your network is now available.
"After the tool finds PST files on users' computers, the tool consolidates the PST files to a central location, and then easily injects PST data to primary or archive mailboxes on your on-premises Exchange Servers or Exchange Online," Microsoft explains.
Improvements in PST Capture 2.0 includes:
- "Support for Microsoft Exchange Server 2013
- Updated profile generation code to use Outlook Anywhere (RPC over HTTP)
- Fixed Exchange Online import failure issue when PST Capture is not installed on an Exchange server
- Removed User Interface limit of 1,000 users when performing an import to Exchange Online
- General performance improvements, informs Microsoft
Download PST Capture 2.0 from the Download Center.