Exchange Unwashed Digest for October 2012

October 2012 was quite a busy month for my “Exchange Unwashed” blog on with 11 articles appearing. Here’s the regular monthly digest:

Exchange 2013 reduces number of mounted databases to 50 (October 30). I wonder how many companies run an Exchange 2010 Database Availability Group (DAG) with more than 50 mounted databases on any individual member node? If there are any companies in this situation, they are going to have to do some work to prepare for Exchange 2013 as the limit for mounted databases has been trimmed back from 100 to 50. Apparently it’s all to do with the extra workload of the mailbox server in Exchange 2013. Or something like that.

The Emerging Need for More Supervision Over ActiveSync Implementations (October 25). ActiveSync is great because it’s become the de facto standard for mobile devices to connect to Exchange. The downside of the success is the free rein that ActiveSync licensees have in the way that they use the protocol within their email clients. The upshot, as seen in Apple iOS 6.0, is symptoms such as “meeting hijacks” where ActiveSync allows a client to update the organizer of a meeting. Not good, and something that Microsoft really needs to be a tad stronger over.

Exchange 2013 and Office 2013 Professional Plus available for download (October 24). One of my public service announcements to let MSDN and TechNet subscribers that they can now get the RTM code for Exchange 2013 and Office 2013. Nothing more exciting that that… let the testing begin!

The road to economic competitiveness – ten years of I/O reduction for Exchange (October 23). I thought that I’d get more reaction to this commentary, which reflects on the sorry state that Exchange 2003 really was (using hindsight as a lens) and all the work that Microsoft has done over the last ten years to restore competitiveness with Google and Gmail. I thought I was making a good point. Maybe others believe that Microsoft really did all the work to reduce I/O for the good of humanity.

Coping with Swelling Mailboxes: Why Outlook 2013 Changes Caching (October 18). In thinking about why Outlook 2013 would even want to mess with the model for cached Exchange mode established and working successfully since Outlook 2003, there’s really only one reason: we are all email slobs with little or no interest in cleaning up our mailbox. So Outlook has to be better at storing all our rubbish, which it is in Outlook 2013, so that’s good…

Exchange 2013 counts data within databases better–may affect user mailbox quotas (October 16). With the zeal of a banker who suddenly realizes that they’ve been calculating interest wrongly, the Exchange Store has discovered that it’s not been charging user mailboxes for all the overhead that databases incur to handle mailboxes. So Exchange 2013 cleans everything up and charges the right amount, with the net effect that you might need to up mailbox quotas by some 30%. Is this a problem? Probably not…

Exchange 2013: the real journey starts now (October 12): The Exchange development group surprised me when they declared success on October 11 and allowed Exchange 2013 to meet the Release to Manufacturing (RTM) bar. I think the core of the product is fine but some loose ends exist around the rest of the product, like the small matter of public folder migration. Never mind, the party started in Redmond on October 11 and should just be about finished now. The next thing to do is to get Exchange 2010 SP3 out the door so that companies can actually deploy Exchange 2013 and the issue of the first service pack or whatever the first batch of fixes for Exchange 2013 will be named. Coming soon. Or so we are told.

Expiring digital signatures and rereleased updates (October 11): All software products released by Microsoft are digitally signed. Sometimes the digital signatures aren’t quite right and the products have to be rereleased. And so the latest roll-up updates for Exchange 2010 SP2, Exchange 2010 SP1, and Exchange 2007 SP3 have reappeared, brighter and better than ever before.

ActiveSync problems with iOS6 (October 9). A new operating system for the iP-devices is released by Apple, another batch of problems with their email clients when connected via ActiveSync to Exchange is discovered. It’s become boring but predictable. iOS6 came out, everyone was hyper-excited, and then we had meeting hijacking all round that’s apparently been a problem since iOS4. Still, it’s Apple, and they’re good, and they’ll fix the problem because they’re good, and it’s only meetings, and no one was harmed, and what do you really care about meetings, and Apple’s good…

Outlook 2013 introduces hybrid cached mode (October 4). Outlook 2013 is really quite smart when it connects to servers and finds out that a lot of new data is waiting there that isn’t present in its cache. Where older clients would fetch and wait, Outlook 2013 fetches and shows. Read all about it!

Exchange 2010 SP3 prepares the way for Exchange 2013 (October 2). You need Exchange 2010 SP3 to be able to co-exist with Exchange 2013. Rather strangely, Microsoft took the pre-emptive step of telling people that Exchange 2010 SP3 is on its way, even though it won’t be available until sometime in early 2013. I guess it was just to reassure companies who are contemplating early Exchange 2013 deployments that they’ll be able to connect to their old servers too!

November is already starting well, so please join me at Exchange Unwashed!

Follow Tony @12Knocksinna

About Tony Redmond

Lead author for the Office 365 for IT Pros eBook and writer about all aspects of the Office 365 ecosystem.
This entry was posted in Cloud, Email, Exchange, Exchange 2010, Exchange 2013, Office 365, Outlook and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.