Blog Post

Exchange Team Blog
3 MIN READ

We want criticism!

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Feb 04, 2008

I recently (hopefully recently, my last post took two years to get published so I'm not sure when this one will go out, LOL) posted one of my typical light-hearted looks into life at Microsoft (it was about how office space is allocated, read it here).  Although it was irrelevant to virtually everything, it elicited many interesting responses, including people complaining (I think) about us having it too good here.  No argument there.  Actually, I was intentionally portraying the situation in a negative light so as not to upset everyone too much.  In reality, we all have 1000 square foot corner window offices (our office buildings were designed by MC Escher) that overlook a lake or mountains (our choice), with a private bathroom, a fold out bed for nap time,  and a full service kitchen.  But never mind that.  There were also many comments on the feature set of Exchange 2007 (rather irrelevant to the pointless topic, but important nevertheless).  They were mostly not liking certain feature take-backs in the release, particularly around the administrative GUI.  I just want everyone to know that despite the light tone here, we do take these comments seriously.  Let me assure you that the discussion that my post prompted generated many a transaction log on our corporate Exchange servers!! Some of you that have been reading our blog for a long time may have noticed that we have taken a very open position regarding the comments that we get on our blog posts. I believe that there were only 2 or 3 cases when we deleted a comment and that was because of some really inappropriate language. We want to keep your comments there, both positive and negative. We read every single one of them and respond to many. We do want to encourage you to post your opinions and ideas, but we do have ask something: if there is an area that is very upsetting to you or where you think we made a mistake, we ask that you would offer criticism about the product, and not the people who work on it. Also, since we actively look to these comments as evidence to make potential changes in our products, we again ask that you would provide specific, actionable feedback on our product. In other words, please explain what it is that bothers you and why it bothers you. What are you trying to accomplish that you can't? Sometimes the comments are obvious (we totally and completely get it that you need more GUI and it's unfortunate we weren't able to get as much of it in to E2K7 RTM as we'd hoped, but we hope that SP1 works better for you there), but sometimes they are not, so the more you explain your user scenario, the better a chance we'll be able to eventually do something about it. In closing, I'd just like to point out the obvious that every product that has ever shipped anywhere has had to make trade-offs between shipping on time, shipping with quality, and shipping with the right features.  For Exchange 2007, we debated long and hard about features that we would ship. We had to balance investments that we wanted to make into the Exchange code base to allow for future innovation (would people be interested in a description of those architectural bets? Or if we posted it, would we just get more "you should have done <my feature foo>" instead? :), feature cuts we felt we had to make to get the quality we wanted to ship with and the timeline we felt it needed to ship in.  We knew some of the cuts would be painful, and we have addressed many of the larger issues in SP1 (some posts on this coming your way, by the way!).   Judging from the early success of Exchange 2007 sales, the many positive reviews we've garnered, and most customer feedback, we seem to have made some pretty good choices here. But obviously - not perfect. We always need to try to do better. I look forward to the responses this post may receive, and rest assured there are lots of people in Exchange who will be paying attention to them, as with all our posts on this blog.  Thank you for coming back and caring enough to comment! - Jon Avner, Nino Bilic

Updated Jul 01, 2019
Version 2.0

60 Comments

  • I do like it better than before overall, but here are a couple.

    *  Add the ability to manage Exchange functions back into ADUC.  It's hard to tell support that they have to go back to two utilities to do their jobs.

    *  The ability to see mailbox sizes in the GUI view of recipients, or store database sizes would be good too.  Anything to help me balance several CCR clusters is helpful.

    *  An easier to learn message tracking system.  Oh how I long for Ex2k3 message tracking.  I know, I'm just not use to it yet.

    Lee
  • Great product, CCR and 64 bit has definately saved us money!

    Hard as it is to find fault ;-) here's what we have...

    * S/MIME needs IE, fair enough. But if it's a signed message on OWA light can't there be an option to allow the user to download the attachments anyway? Our customers treat this as a bug, not a feature.
    * Why isn't iCal an OWA/WebDev server feature. Our Mac users would love direct iCal integration - Entourage 2008 hasn't been a big improvement (we won't be rushing to roll it out).
    * Why can't a user make their calender truly public (Anonymous users).
    * Pine / Alpine users complain that Ex IMAP still isn't truly RFC compliant, the author says he wrote IMAP and won't make allowances for servers that don't meet the client's standards.
    * Can we make OWA premium work with Firefox and Safari. Many of our customers just assume OWA light is what OWA is, as they never use IE.
    * A powershell commandlet to set a user's Out of office would be useful
  • Great product, CCR and 64 bit has definately saved us money!

    Hard as it is to find fault ;-) here's what we have...

    * S/MIME needs IE, fair enough. But if it's a signed message on OWA light can't there be an option to allow the user to download the attachments anyway? Our customers treat this as a bug, not a feature.
    * Why isn't iCal an OWA/WebDev server feature. Our Mac users would love direct iCal integration - Entourage 2008 hasn't been a big improvement (we won't be rushing to roll it out).
    * Why can't a user make their calender truly public (Anonymous users).
    * Pine / Alpine users complain that Ex IMAP still isn't truly RFC compliant, the author says he wrote IMAP and won't make allowances for servers that don't meet the client's standards.
    * Can we make OWA premium work with Firefox and Safari. Many of our customers just assume OWA light is what OWA is, as they never use IE.
    * A powershell commandlet to set a user's Out of office would be useful
  • I find it *VERY* annoying that I can no longer specify different delivery times for oversized messages like we could do in Exchange 2003. When users send large attachments to multiple recipients it kills our office DSL bandwidth. In Exchange 2003 we used to be able to specify that oversized attachments should be sent at, say, 3AM when bandwitdh isn't so critical.

    Also, it would be nice to be able to specify custom actions (like scripts) in transport rules.

    Other than that, we absolutely love Exchange 2007, especially with the release of SP1.
  • I have been running Exchange 2007 since Feb 07 and just upgraded all of our servers to Exchange SP1.  Love the new features and the extra GUI management.

    My problem is that we set address lists via the msexchquerybaseDN attribute on every managed user in our AD.  We have been doing this since March 2007.  Since the upgrade to SP1, any user who has the attribute set cannot recieve autodiscover settings.  When I remove the attribute and do an Outlook 2007 Autoconfiguration test, it works fine. So essentially, we have no free/busy, oof or autodiscover for any managed user running Outlook 2007.  If I run a test-outlookwebservices on a cas server, everything comes back as a success regardless of the msexchangequerybaseDN attibute being set or not.

    Have you heard of this before? Is there a planned hotfix for this issue and if so, when is the expected release?  If you are interested in error messages in Outlook, please let me know.
  • Mike,

    Can't comment on forums, sorry... different people run those two. I DO know that every comment to this blog gets read though.

    If you have ideas for blog posts, you can go here: http://msexchangeteam.com/archive/2004/12/10/279655.aspx

    Comments to our blog posts are always welcome!
  • You mentioned that you read every comment posted to this blog.  Is this also true of the technet forums?  I am very involved there, and wonder if I'm more likley to be heard here or there.  (when I have a comment or something, not a technical question)
  • So did you choose the lake or mountain?
  • I really like what I have seen with most of the features of Exchange 2007, but the feature change that bothers me most:
    No longer readily use LDAP queries for dynamic distribution groups or address books.  With Exchange Server 2007: Opath does not seem to take into account the extensibility of Active Directory or all of the attributes that are already there.  Example of the issue: with Exchange Server 2003 we have many address books and distribution lists that are based on what the division attribute of a recipient starts with.
    Additionally in the UI, could you add other operators like "starts with"?  i.e. company starts with, instead of just having company equals.
  • I think the last remaining piece that needs to be fixed for Exchange is Certificate request and Certificate management. Isn't there a way to request a certificate without having to go through the CLI? It was so much easier using the IIS Certificate Request Wizard. Also, how about bind certificates to services? It's easy to mess up using the CLI, but I never made a mistake bind certificates to the SMTP, POP3, IMAP4 and Web services using the IIS console in previous versions. Can you do something to make it as easy (or even easier) than it used to be?
    Thanks!
    Tom