OK – so its not just a busy day in the land of Exchange updates, it's a crazy busy day! Not only do we have Exchange 2007 SP3 RU10, Exchange 2010 SP2 RU6 now Exchange 2010 SP3 is released to the download centre.
Just like Exchange 2010 SP2 which had four main features
Exchange 2010 SP3 builds on them and adds support for
If you do want to have Exchange 2010 and 2013 installed into the same forest then SP3 is a hard requirement for the Exchange 2010 servers. This will be required on all Exchange 2010 servers in the org. And for the Exchange 2013 servers they must have CU1 installed. As you may have seen on the blog, the servicing model has changed in Exchange 2013 and Rollup Updates (RUs) are to be replace with Cumulative Updates (CUs).
Please enjoy the service pack responsibly!
What do I mean by that? Well, you need to ensure that you are fully informed about the caveats with the service pack and are aware of all of the changes that it will make within your environment. Additionally you will need to test the service pack in your lab which is representative of your production environment. Third party software vendors must also be consulted to ensure that they are in a position to support Exchange 2010 SP3 as you do not want to rush out and install SP3, run into an issue, and then discover that vendor X does not currently support their product when running with Exchange 2010 SP3. That would be called a RGE (Resume Generating Event).
What's New in Exchange 2010 SP3
http://technet.microsoft.com/en-us/library/jj965775(v=exchg.141).aspx
Release Notes
http://technet.microsoft.com/en-us/library/jj965774%28v=exchg.141%29.aspx
Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
Updated MAPI & CDO bundle.
Additional Fixes
In addition to the customer reported issues resolved in previous rollups, this service pack also resolves the issues that are described in the following articles:
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
Cheers,
Rhoderick
Update 1-3-2013: You may also want to reference the Hyper-V 2012 and Cluster update wiki pages as linked & discussed here.
After building up a nice new Windows Server 2012 Hyper-V cluster with SCVMM 2012 SP1, it was a bit strange to get the world’s longest error when opening up the Failover Cluster MMC. The error started with:
A weak event was created and it lives on the wrong object, there is a very high chance that this will fail
Well, fail it did in spectacular style
What’s the issue and solution you may ask? Well this was caused by a recent .NET update (2750149) and there is now a fix available in KB 2803748.
So if you have installed 2750149 then you will likely want to download and install this update 2803748.
It’s a busy day in the land of Exchange today, with updates for both Exchange 2007 and Exchange 2010. Exchange 2010 SP2 RU6 is now available as update 2746164.
Exchange 2010 SP2 RU6 is also released as part of Patch Tuesday to resolve the security issues that are addressed in Exchange 2007 SP3 RU10. For reference they are CVE-2013-0393 and CVE-2013-0418 as discussed in the Oracle Critical Patch Update Advisory - January 2013. Microsoft has classified one of these issues as critical and the other as important
In addition to addressing the vulnerabilities that are described in Microsoft Security Bulletin MS13-012 this update also resolves other non-security issues. A list of the individual fixes is at the end of this post, but there are a couple to highlight
Email message delivery is delayed on a Blackberry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2
You cannot move or delete an email message that is larger than the maximum receive or send size in an Exchange Server 2010 environment
Msftefd.exe process crashes if an email attachment has an unexpected file name extension or no file name extension in an Exchange Server 2010 environment
2489941 The "legacyExchangeDN" value is shown in the "From" field instead of the "Simple Display Name" in an email message in an Exchange Server 2010 environment
2717453 You cannot move or delete a folder by using Outlook in online mode in an Exchange Server 2010 environment
2733608 Corrupted Japanese DBCS characters when you send a meeting request or post a reply to a posted item in a public folder in an Exchange Server 2010 environment
2734635 Folder-associated information (FAI) items are deleted when you run the New-InboxRule cmdlet or change Inbox rules in an Exchange Server 2010 environment
2737046 AutoPreview feature does not work when you use Outlook in online mode in an Exchange Server 2010 environment
2741117 High CPU utilization by Microsoft Exchange Replication service on Client Access servers in an Exchange Server 2010 environment
2746030 Incorrect ExternalURL value for EWS is returned by an Exchange Server 2010 Client Access server
2750188 Exchange Service Host service crashes when you start the service on an Exchange 2010 server
2751417 Synchronization fails if you sync an external device to a mailbox through EAS in an Exchange Server 2010 environment
2751581 OAB generation fails with event IDs 9126, 9330, and either 9338 or 9339 in an Exchange Server 2010 environment
2760999 "The signup domain 'org' derived from '<TenantDomainName>.org' is not a valid domain" error message when you use the Hybrid Configuration wizard in an Exchange Server
2776259 Msftefd.exe process crashes if an email attachment has an unexpected file name extension or no file name extension 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
2783586 Name order of a contact is displayed incorrectly after you edit the contact in an Exchange Server 2010 environment
2783631 User-Agent field is empty when you run the Get-ActiveSyncDeviceStatistics cmdlet in an Exchange Server 2010 SP2 environment
2783633 You cannot move or delete an email message that is larger than the maximum receive or send size in an Exchange Server 2010 environment
2783649 Private appointment is visible to a delegate in an Exchange Server 2010 environment
2783771 Mailbox on a mobile device is not updated when EAS is configured in an Exchange Server 2010 environment
2783772 Edgetransport.exe process crashes after a journal recipient receives an NDR message in an Exchange Server 2010 environment
2783776 You cannot perform a cross-premises search in a mailbox in an Exchange Server 2010 hybrid environment
2783782 Error message when you use Scanpst.exe on a .pst file in an Exchange Server 2010 environment
2784081 Store.exe process crashes if you add certain registry keys to an Exchange Server 2010 Mailbox server
2784083 Week numbers in the Outlook Web App and Outlook calendars are mismatched in an Exchange Server 2010 environment
2784093 SCOM alerts and event ID 4 in an Exchange Server 2010 SP2 organization that has Update Rollup 1 or later
2784566 Exchange RPC Client Access service crashes on an Exchange Server 2010 Mailbox server
2787023Exchange Mailbox Assistants service crashes when you try to change a recurring calendar item or publish free/busy data in an Exchange Server 2010 environment
2793274 A new option is available that disables the PermanentlyDelete retention action in an Exchange Server 2010 organization
2793278 You cannot use the search function to search for mailbox items in an Exchange Server 2010 environment
2793279 Exchange Server 2010 does not restart when the Microsoft Exchange Replication service freezes
2793488 Internet Explorer freezes when you connect to the OWA several times in an Exchange Server 2010 environment
2810616 Email message delivery is delayed on a Blackberry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2
There is an additional item listed here:
2788151 Empty delegates list for a cloud-based resource mailbox when you use EMC in an on-premises Exchange Server 2010 SP2 environment
And as always, please test and validate this update in a lab before placing into production. Though I just know that I’m going to see people in the forums tonight with production issues
The updated version of Windows 2012’s Hyper-V Architecture component poster is now available for download which is pretty neat!
As an added bonus, there are companion references for Hyper-V Replica, Hyper-V Storage, VM Mobility and Networking.
The Windows Server 2008 R2 SP1 Hyper-V poster is available here if you want to round out your collection
Here I was truffling through the TechNet forums, and saw this thread. I thought I’d share a little bit more detail around it, as the error text that is added to the event log entry is a little confusing.
While Exchange 2007 did have some throttling mechanisms, it was Exchange 2010 that really introduced a fully featured throttling framework. This is implemented by configuring client throttling policies and assigning them to mailboxes. When a client exceeds it’s defined throttle policy, an event may be written to the application event log. In the example that is in the forum thread it is for one of the OWA components. An event ID 2915 was logged stating the following:
Process w3wp.exe () (PID=6252). User 'Sid~contosa\abcd~OWA~false' has gone over budget '14' times for component 'OWA' within a one minute period. Info: 'Policy:DefaultThrottlingPolicy_d7d68d93-9249-4fa7-cfoe-901ac837ae2f, Parts:AD:13;'. Threshold value: '10'.
What could possible be confusing with the above? In this case it was the last portion of the message:
“ Threshold value: '10'. ”
Most people assume that the threshold value, as shown in blue above, is an actual value as configured in the throttling policy. So when the cmdlet Get-ThrottlingPolicy is executed, and since 10 does not show up in the OWA section output head scratching ensues!
What is this mythical 10? Is it in binary - no. Is it in Hexadecimal – no. The threshold value actually tells Exchange after how many occurrences should it write the 2915 event to the application log. In other words, if the number of times a user exceeds the budget is higher than 10 in the last minute then we should create an Event 2915.
In this case the user had gone over budget 14 times in the last minute. Since 14 exceeds the event writing threshold count of 10, then the 2915 event was created.
I should do some coverage on throttling policies in general, as there have been some issues with them recently and also historically.
Please do add a comment if there is something that you would like to see posted here. If you don’t want to add a public comment there is always the “Email Blog Author” button to the right of every page.
Just in case anyone is still procrastinating about moving over from Mesh to SkyDrive, please note that Mesh will be retired next week on Wednesday February the 13th 2013.
Believe it or not, but it was back in 2008 when Mesh was released. Time certainly flies, and the capabilities and expectations people now have for cloud services have changed.
SkyDrive is now the central component for integrating Windows Phone, Xbox and all other Windows devices, and thus Mesh will be retired. Since SkyDrive does not have the option to connect to a remote PC, there is a suggestion below to use an alternative service. This is covered in the email that was sent out to mesh customers, and this is pasted below.
Steps required for Mesh customers to move to Skydrive are here.
And for a blast from the past, here’s a glimpse back in time.
So long Mesh it was great knowing you!!
Dear Mesh customer, Recently we released the latest version of SkyDrive, which you can use to:
Currently 40% of Mesh customers are actively using SkyDrive and based on the positive response and our increasing focus on improving personal cloud storage, it makes sense to merge SkyDrive and Mesh into a single product for anytime and anywhere access for files. As a result, we will retire Mesh on February 13, 2013. After this date, some Mesh functions, such as remote desktop and peer to peer sync, will no longer be available and any data on the Mesh cloud, called Mesh synced storage or SkyDrive synced storage, will be removed. The folders you synced with Mesh will stop syncing, and you will not be able to connect to your PCs remotely using Mesh. We encourage you to try out the new SkyDrive to see how it can meet your needs. During the transition period, we suggest that, in addition to using Mesh, you sync your Mesh files using SkyDrive. This way, you can try out SkyDrive without changing your existing Mesh setup. For tips on transitioning to SkyDrive, see SkyDrive for Mesh users on the Windows website. If you have questions, you can post them in the SkyDrive forums. Mesh customers have been influential and your feedback has helped shape our strategy for Mesh and SkyDrive. We would not be here without your support and hope you continue to give us feedback as you use SkyDrive.
Sincerely,
The Windows Live Mesh and SkyDrive teams
Frequently Asked Questions
Why is this happening?
Over the years, customers have asked us to bring many of the benefits of SkyDrive – including mobile access and online collaboration – to Windows Live Mesh. We've also received requests for some of the features of Mesh – such as syncing and remote access—to SkyDrive. Bringing together key features of both products into SkyDrive allows us to maintain a single product and deliver all of these benefits to customers. Moving forward, a single product also allows us to quickly deliver more new features to everyone.
What features are available on SkyDrive?
What can I expect between now and the date when Windows Live Mesh is retired?
For now, Mesh will continue to work the same as always. We'll send you reminder emails as the retirement date for Mesh gets closer.
Where can I learn more?
For more information, see SkyDrive for Mesh users. You'll find details about how to make the switch to SkyDrive, as well as updates about the changes to Mesh.
Can I use SkyDrive to connect to a PC remotely and run apps on it?
No, with SkyDrive you can fetch files on a remote PC, but you can't connect to it remotely to work as if you were sitting in front of it. If you want to connect to a work PC, try Remote Desktop Connection in Windows. With Remote Desktop Connection, you can connect to PCs that are running these editions of Windows:
To remotely connect to a Mac or other Windows operating systems not listed above, we recommend creating a LogMeIn account. LogMeIn Pro gives you fast, easy remote computer access from your devices over the web in HD. Transfer files, print remotely, or keep machines up to date from any computer or your mobile device.
Exchange sustained engineering has released Exchange 2007 SP3 RU10 to the Microsoft download centre as update 2788321.
For the astute of you out there, you will notice that this is on the second Tuesday of February which makes it Patch Tuesday. It also happens to be Shrove Tuesday as well by happy coincidence so I’m having pancakes for dinner, but I think I’m digressing…..
Since it is Patch Tuesday, does that mean that there are security issues that are resolved in this update? Yup! In terms of the security vulnerabilities resolved, they are CVE-2013-0393 and CVE-2013-0418 as discussed in the Oracle Critical Patch Update Advisory - January 2013. Microsoft has classified one of these issues as critical and the other as important
In short, Exchange 2007 SP3 RU10 will update these three areas:
As always please ensure that you test and validate the update in a lab prior to placing into production.
Just in case you may be wondering why this update is for Exchange 2007 SP3, and not SP1 or SP2 it is because those versions are no longer supported.