In my previous article, The Future of Exchange, I speculated on what are the next steps for Exchange which essentially is what’s next in its development as the workforce and the workplace evolve. Part of that speculation included a tighter integration with the complimentary products for Exchange; SharePoint and Lync.
A couple of weeks ago we attended the Microsoft Exchange Conference in Orlando- you can read an abstract of the previous post here. All in all it was a great conference and had me thinking about the product’s early beginnings and where it may be going in the future. A lot has changed since Exchange 4.0 was released in early 1996 but at the core Exchange is first and foremost a tool for internet mail delivery.
All right, day one at the MEC has wrapped up and the “un-conference” thus far has been a success. Seeking to distance itself from the typical technical conference MEC has certainly provided a welcome departure from what we’ve all become accustomed to recently. Most notable among the differences is the atmosphere at the keynotes, each thus far has provided a hefty dose interesting content, witty humor, and shots at a whole host of targets.
In anticipation of the returning Microsoft Exchange Conference next week I thought I’d take the opportunity to provide an overview of some of the new features that will be part of the next release of Microsoft’s Exchange Server. Up front the thing that stands out the most is the server roles that are available in Exchange 2013, Client Access and Mailbox. Yes all other roles are eliminated (Edge role will be available in a later service pack, 2013 will be compatible with 2010 Edge). The Client Access Server role has absorbed internet facing SMTP transport while the Mailbox role has absorbed internal SMTP transport. Outwardly that’s the largest difference in the new version; however there are a number of internal architectural differences as well as new features.
In a few weeks we’ll be attending the revived Microsoft Exchange Conference in Orlando. I have to say I’m quite excited about the prospect as this conference has been absent for the last 10 years. At Tech-Ed in June there was quite a bit of buzz around the return of the conference divided largely by those who have attended the MEC before its disappearance and those who haven’t. I sadly must admit I am one of the many who have not attended a previous MEC, and based on the discussions by those who have, very excited to see its return.
In Exchange 2010 a number of improvements were made in regards to message transport. The introduction of Database Availability Groups required a different approach to ensure that message loss would not occur in the event of a failure of a mailbox server. In this article I’m going to highlight some of those improvements as well as provide an overview of the transport process.
The evolution of Exchange has brought with it numerous changes, improvements and features throughout the years. One thing that has always remained a challenge is high availability and site resiliency. In the most recent versions of Exchange a great deal more attention has be afforded these topics and the results have certainly been welcome. In Exchange 2010 Microsoft has delivered a nearly autonomous solution for ensuring the availability and performance of your Exchange servers.
With the introduction of Exchange 2010 DAS has become a truly viable option for Exchange mailbox storage. Specifically, Exchange high availability improvements make DAS a viable option. In Exchange 2010 Microsoft introduced Database Availability Groups (DAG) as an improvement over Local Continuous Replication (LCR) Continuous Cluster Replication (CCR) and Standby Continuous Replication (SCR). This improvement meant that each individual mailbox database could have up to sixteen copies. As a result the need for protection against disk failure takes on less importance, hence the viability of DAS as a storage option for Exchange 2010.
If there’s one thing that’s certain in SharePoint it’s growth. And as you SharePoint environment grows performance can become quite an issue. Obviously there are quite a few things that go into performance, however in this post I’d like to discuss three best practices or considerations.
As more and more companies are adopting BYOD supporting a broad set of end user devices security and device management take on greater importance. As we are left wonder where the BlackBerry Enterprise Server will fit into the current and future state of enterprise messaging other vendors and technologies are left to fill the gaps. Anyone who has been working with Exchange for some time knows that ActiveSync has been around for a while; its recent evolution brings us to the current version which is part of Exchange 2010.