Here are a few of the headlines we deemed worthy this week:
The functionality in Exchange Hybrid has matured, enabling organizations to mix mailboxes on-premises and in the cloud and retain much of the normal sharing capabilities people rely on for day-to-day collaboration.
In this post, Steve Goodman delves into the types of sharing available in Exchange hybrid and improvements to sharing in Exchange 2013 CU10.
The following blog post is a trimmed-down excerpt from the eBook "Exchange Server Troubleshooting Companion":
Mailbox corruption is not a new problem for Exchange Administrators, Support Engineers, and Consultants. Causes of corruption can vary and include:
Here's your weekly dose of popular Exchange and Office 365 insights:
Over the past two weeks, Microsoft has made a range of announcements around updates and new releases of Office, Office 365 and Exchange. The fact that Microsoft announces updates is hardly surprising. By now you should be used to the never-ending cascade of new features that are constantly dropped onto the market. A good way to keep track of what’s to come is the Office 365 Roadmap website.
A few days ago, Microsoft released the public preview of Exchange 2016 to the world. For many messaging professionals, this is usually an exciting time. But is it really? I remember when Exchange 2007 'hit the market.' I spent quite a few long days and nights discovering the new features and dramatically changed architecture. Pretty much the same happened when Microsoft unleashed Exchange 2010. The newly minted Database Availability Group kept many people – including myself – fascinated and busy for a long time. One of my fondest memories about that time was a hefty, yet in hindsight very funny, discussion that followed a technical presentation at my former employer.
With Exchange 2016 fever in the air, many admins are left with looming questions about what changes this new iteration will bring.
ENow’s Microsoft Exchange Server MVP Michael Van Horenbeeck recently partnered with MSExchange.org to host a webinar that would clear up some lingering questions surrounding Exchange 2016 and beyond.
When designing for a migration to Exchange Server 2013, chances are you’ll have to deal with public folders. Given that Exchange 2013 has been around for a while, you might think such a task would be a proverbial walk in the park. Of course, if you are looking at a cookie-cutter environment, you might be right. However, in every design there are elements specific to the customer that require a different approach.
More specifically, consider the scenario in which you have public folders — possibly lots of them. For the sake of this article, let’s assume you have about 500GB worth in public folders spread over several thousand public folders across one or more replicas. For some customers, these numbers are much more than they have. For other customers, 500GB in public folders might just be a fraction of what they have to deal with. Regardless of your situation, public folders raise a rather interesting question: How do you plan for (a migration of) public folders to Exchange 2013?
Michael Van Horenbeeck
Topping 1,100 sessions and drawing in more than 23,000 attendees, Microsoft Ignite was a whirlwind of a week. Among the hundreds of sessions related to Azure, Office 365, Exchange, Windows, and many other Microsoft products, you might have some difficulty keeping all the information straight.
To recap the most memorable Exchange moments, experts Tony Redmond, Michael Van Hybrid, and Jeff Guillet gathered for The Ignite Debrief (Exchange Version) Podcast that’s now available to view. In this 25-minute podcast, the experts zero in on Exchange to provide their takes on several significant Exchange-related announcements from the conference.
On March 17th, Microsoft released Cumulative Update 8 for Exchange Server 2013. By now, we're all used to the idea that cumulative updates and not only Service Packs have also become a vehicle to introduce new features into Exchange. Hence, it is no surprise that CU8 comes with a bunch of new features and improvements alongside a myriad of bug fixes.
It has been since Cumulative Update 5 that Microsoft introduced new "hybrid" features. So you can imagine how pleased I was to learn that CU8 contained a rather important improvement with regards to hybrid deployments.
Before we dive into the feature itself, let me give some background information on the problem the feature will help to solve. A hybrid deployment is often deployed to allow the so-called "hybrid mailbox moves", sometimes you'll also see them referenced as "MRS moves" or "remote mailbox moves". Regardless of what name you use, in my opinion these mailbox moves offer significant value over other migration methods. The simple reason being that hybrid mailbox moves are more resilient, more flexible and almost transparent to the end user. In a staged- or cutover migration, once a mailbox is moved, Outlook's offline cache (.OST file) has to be recreated. While you might think this is not really a problem, try and imagine how that would feel like for an organization that has limited bandwidth but has several hundred gigabyte worth of mailbox data. In such scenario, if you can avoid having to download the data which you just have 'uploaded' to Office 365, then that is something you would want to look into.