Blog Post

Exchange Team Blog
3 MIN READ

Exchange 14 Video

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Jan 14, 2009

We've been hard at work on Exchange 14 (E14) for a few years now, and although we've shared a lot of details and code with customers on our TAP & Live@edu programs, we haven't been too chatty publicly. That's going to be changing over the coming months, starting with this first introductory video[1] with myself and Jim Lucey, the product manager for Exchange Labs, to talk a little bit about some of the work we've been doing. One of the biggest things that's different in E14 is that we started from day 1 two years ago with the goal of building a product on a single codebase that could be deployed in the way Exchange has been for over a decade in on-premise environments, as well as also be deployed in a service environment and scale to (eventually) hundreds of millions of users. I say 'eventually' because we're not quite there yet. We have only 3.5 million users right now :) I know, chump change, right? The service thinking really got traction at the company when Ozzie wrote his software plus services memo, and that has been our mindset from the beginning of the E14 development cycle, affecting everything we do - what features we should build, how we architect them, how we test the code, how we get customer feedback, etc. Although Exchange has always been a group that's very reliant on dogfooding, even with Microsoft's ~100,000 mailboxes, that wasn't enough for us to validate our high scale. So that's why we started using Exchange 14 in Exchange Labs back in October 2007 as part of the live@edu program. Today, more than 3.5 million people (students, faculty, staff, alumni) in more than 1,500 schools are using E14 through Exchange Labs, and we are adding more every day. Some of the schools involved include: St John's University, The Wharton School of Business at the University of Pennsylvania, Hinds Community College, Coos Bay Public Schools, Colorado Community College System, and many more. We haven't lost the focus on the on-premise product, however - more to the point, deploying the service helps us understand at a very intimate level what exactly the pain points are in Exchange deployment & administration & more[2] that we need to be improving for on-premise Exchange admins. So at the same time, we're also working with our TAP customers to test and deploy E14 in on-premise and heterogeneous IT environments. Having that first-hand experience running the service is what's letting us build the most scalable version of Exchange yet. Ferris Research just did a survey of several enterprise customers, and they found that the cost of running Exchange 2007 was roughly half that of running Exchange 2003. E14 will bring that cost down by a similar margin yet again. At any rate, so here's the introductory video. I realize it's not much to start with, but it's what I've got for now. E14's coming, get ready to learn more & give us feedback on it over the coming months. We'll post more videos and blogs in the next couple of months with some more details. The video is also available on TechNet in a number of different formats.

[1] Don’t lean back against the wall when doing a video, as you will look like you’re slouching. I hope my mother doesn’t see this video as I’ll never hear the end about my bad posture. I got about 20 seconds in and had to stop, I look like a dork.

 

[2] And compliance, and self-service administration, and mailbox search, and browser matrixes, and hardware costs, and power consumption in the datacenter, and and and… I could go on forever J

- KC Lemson
Updated Jul 01, 2019
Version 2.0

60 Comments

  • Will some level of SLA database management be implemented?

    For many reasons Exchange admins need to control the maximum DB size (backup, restore, online maintenance etc.). But with E2K3E2k7 there's no option to configure the maximum number of mailboxes a database can contain and/or the maximum DB size. Also there's no option to force DB quotas so that exceptions can't be made by admins.

    Martijn
  • It's been mentioned but I want to second the cross-browser / cross platform experience request. In a university environment this is key. We can't dictate what clients our faculty use, let alone our students. Supporting these sub par client experiences is a nightmare for IT in universities.
  • I agree with Kevin on the administration perspective. Too many applications to manage users with mail attributes. I'd like to understand from E14 how the Exchange Management Console has been evolved for delegated administration and the hosted model.



    Oh yes, and everything else of course considering this is the first exposure I've had to this new version.... :)

  • How about decreasing the number of email records?

    For instance, I send an email out to two friends and both reply to my email.  I rather see 1 email with 2 responses, rather than have 2 separate email to the same email subject.

    I get countless emails especially when a big group is responding to the same email.  
  • Kevin - WOW! Thanks for the detailed feedback. We are definitely working on some of the things you raised.

    Everyone - We'll have more to talk about on these issues over the coming months.

    (still snickering about 'lambda, lambda, lambda')
  • What about any changes to the LDAP properties. I'm sure we aren't alone in accessing user and mailbox properties via LDAP. With Exchange 2007 all that seemed to go away. Now we can't see that data. Any change?
  • Thanks for the video. I would love to see more of E14.

    You asked for some feedback so here are a few requests for future presentations:

    - please improve the image capture. When showing screen shots or demos please don't use a camera that can barely see the screen.

    - explain if the proliferation of required servers has changed. E2K3 was a front end and a back end. E2K7 was Edge, Hub, transport, mailbox, etc. what is the situation with E14?

    - clustering and HA changes?

    - Security delegation ...

    [In a University it is more likely to have devolved admin structures, but not the one Microsoft assumes. We have 6 different groups who are responsible for their area's staff/user accounts/mailboxes/etc. The Infrastructure group delivers Exchange but doesn't manage the users.

    E2K3 was simple; The admins had ADUC and rights over their users. All properties and management including Exchange was visible in the ADUC GUI. With E2K7 they need ADUC plus the Exchange console but the delegation model is all about splitting user management from mailbox management. I would think the more normal split model should be around "this group manages these users (all features) and this group manages these users (all features)"]

    - backup and restores. I know this isn't strictly an Exchange issue but it is a day to day issue for most admins.

    [One reason I'm asking is that I followed the "how does Microsoft IT do Exchange" Technet and video trail all the way to the Data Protection Manager 2007 and how to restore a single mailbox. Technet says the following "To recover a mailbox, DPM must copy the entire database because this is the recommended method that Exchange supports". Many 3rd party products allow the quick recovery of mailboxes or even single mail items, but apparently this is not supported. "Microsoft support policy for third-party products that modify or extract Exchange database contents" (http://go.microsoft.com/fwlink/?LinkId=96542).

    So, what are the restore options supported with E14? a whole separate blog on this topic would be great.

    Another issue with restores .. moving mailboxes around seem to be the norm for many Microsoft how-to's etc. This really messes with the restore process, as in "OK, we need to restore this mailbox from 12 months ago .. what store was it on back then?". Any changes in thoughts on that?]

    - Performance improvements.

    - OWA improvement for non-IE users

    Thanks. Sorry for the long post. Love the products and this blog!

    Cheers
    Kevin
  • I'd like to hear more about E14 programmability.  EWS is a good step forward in E2k7 but it only exposed a subset.  I'd welcome any info about new Managed API that was previewed at PDC and how it applies to this version.  Are Mapi or ADSI not needed entirely?
  • I really enjoyed that you start publish some public info about E14!
    I would love to see what you have done to high availability and transport in E14!
  • 2 things:

    Is any part of the OWA experience going to leverage Silverlight?
    What about a distro called "Lambda, Lambda, Lambda"?  

    NERDS RULE!