• Sign In
 
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...

  • Advanced search options...
  • Blog Home
  • About
  • Email Blog Author
  • Share this
  • RSS for posts
  • Atom
  • RSS for comments
  • CDO (20)
  • Code Snippet (42)
  • Custom Providers (15)
  • Debugging (7)
  • DevMsgTeam (268)
  • Documentation (96)
  • DST (8)
  • EWS (7)
  • Exchange (98)
  • Gotchas (89)
  • Hotfix (26)
  • MAPI (212)
  • MAPI Download (47)
  • MFCMAPI (87)
  • MSDN (49)
  • Non Dev (11)
  • OOM (17)
  • Outlook (154)
  • Outlook 2007 Auxiliary Reference (44)
  • Outlook Integration API (11)
  • Protocol Docs (20)
  • PST/OST (21)
  • Public Folders (3)
  • Vista (12)
  • WrapPST (14)
Links:
  • Download MFCMAPI
  • MFCMAPI on Facebook
  • Troubleshooting Outlook Crashes
  • Office Update Center
  • Developer Messaging Team Blog
This site is provided "AS IS" with no warranties, and confers no rights. Use of included code samples are subject to the terms specified in the Terms of Use.
Archives
  • January 2012 (1)
  • December 2011 (3)
  • November 2011 (1)
  • October 2011 (3)
  • September 2011 (1)
  • August 2011 (1)
  • July 2011 (4)
  • June 2011 (3)
  • May 2011 (3)
  • April 2011 (3)
  • March 2011 (5)
  • February 2011 (1)
  • January 2011 (2)
  • December 2010 (1)
  • November 2010 (4)
  • October 2010 (1)
  • September 2010 (3)
  • August 2010 (5)
  • July 2010 (3)
  • June 2010 (3)
  • May 2010 (1)
  • April 2010 (3)
  • March 2010 (3)
  • February 2010 (3)
  • January 2010 (2)
  • December 2009 (3)
  • November 2009 (5)
  • October 2009 (4)
  • September 2009 (5)
  • August 2009 (5)
  • July 2009 (11)
  • June 2009 (6)
  • May 2009 (5)
  • April 2009 (3)
  • March 2009 (18)
  • February 2009 (10)
  • January 2009 (3)
  • December 2008 (2)
  • November 2008 (2)
  • October 2008 (5)
  • September 2008 (4)
  • August 2008 (10)
  • July 2008 (6)
  • June 2008 (8)
  • May 2008 (2)
  • April 2008 (4)
  • March 2008 (2)
  • February 2008 (2)
  • January 2008 (5)
  • December 2007 (3)
  • November 2007 (2)
  • October 2007 (3)
  • September 2007 (1)
  • August 2007 (4)
  • July 2007 (5)
  • June 2007 (3)
  • May 2007 (4)
  • April 2007 (1)
  • March 2007 (6)
  • February 2007 (3)
  • January 2007 (2)
  • December 2006 (4)
  • November 2006 (3)
  • October 2006 (1)
  • August 2006 (1)
  • June 2006 (5)
  • May 2006 (5)
  • December 2005 (1)
  • November 2005 (4)
  • October 2005 (2)
  • September 2005 (1)
  • April 2005 (3)
  • December 2004 (2)
  • September 2004 (2)
  • August 2004 (3)
  • July 2004 (3)

Exchange System Manager for Vista

MSDN Blogs > SGriffin's MAPI Internals > Exchange System Manager for Vista

Exchange System Manager for Vista

Stephen Griffin - MSFT
25 Aug 2008 12:04 PM
  • Comments 13

We recently released a downloadable Exchange System Manager (ESM) for Exchange 2003 which can be installed on Vista machines. Part of what made this possible was the changes we did recently to allow Exchange's implementation of the MAPI client binaries to run on Vista.

Some interesting tidbits from the Release Notes:

  • The downloadable ESM depends on the MAPI Download, which must be installed first.
  • Therefore - the ESM and Outlook cannot be installed on the same machine. Of course, this is old news - we've never supported the ESM and Outlook on the same machine.
  • This download is for Vista only. It does not support Windows Server 2008.

Enjoy!

  • 13 Comments
Exchange, MAPI, MAPI Download, DevMsgTeam, Vista
Comments
  • JP
    26 Aug 2008 10:08 AM

    Hi,

    Does this imply that the MAPI/CDO web download, apparently for Exchange 2007, is fully and officially supported for use with Exchange 2003 in other versions of Windows?

    That is, there is no reason now to install the Exchange 2003 ESM and its updates on a (server) machine if all that is needed is MAPI/CDO?

    Thanks.

  • Stephen Griffin - MSFT
    26 Aug 2008 10:43 AM

    I'm not aware that we've ever said the download isn't supported connecting to Exchange 2003. Of course, you can't install the download on an Exchange 2003 box - but that's simply because MAPI's already on the box. Do you have any references indicating the download shouldn't be used to connect to Exchange 2003?

  • JP
    26 Aug 2008 12:18 PM

    No, not a explicit "shouldn't".  But neither is there an explicit "should" ;)

    For example, the MAPI/CDO web download page does not explicitly state that this version fully supports Exchange 2003 or earlier.

    Every Exchange server comes with its own flavor of MAPI/CDO and the practice I am aware of has always been to match the versions of MAPI/CDO and Exchange.

    There have been enough differences, such as the no public folder flag issue, and the vista change, where the Exchange version of MAPI/CDO did matter.

    So, the question is, for functionality and MS support calls, is the web MAPI/CDO download equivalent to the latest Exchange 2003 MAPI/CDO version?

  • Stephen Griffin - MSFT
    26 Aug 2008 2:22 PM

    The MAPI download is built out of an Exchange 2003 branch. So it *is* Exchange 2003's MAPI, with an installer wrapped around it.

  • Mike
    17 Sep 2008 1:59 PM

    I was able to trick the installer into installing the ESM along with Outlook.

    <Steve here> I've excised the rest of this comment. It doesn't matter if you *can* force the ESM to install alongside Outlook. What matters is that if you do it, there *are* conflicts and there *will* be problems. I've debugged too many issues that turned out to be caused by this to condone helping people shoot themselves in the foot.

  • Bill Fry
    8 Oct 2008 10:07 AM

    I'd never heard of problems running ESM along with outlook on an XP box, and never had any myself, though some tasks with public folders didn't work that well.

    Is there any work around for those of us using a Vista station to manage a 2003 Exchange system more directly than remote desktop?

  • Stephen Griffin - MSFT
    8 Oct 2008 10:35 AM

    So you've never heard of problems - except the problems you actually experienced. Interesting. :)

    We've never supported ESM on a machine with Outlook, so no, there are no Vista specific workarounds to offer.

  • Bill Fry
    8 Oct 2008 3:08 PM

    The issues we had were minor.  Nothing to indicate the "shoot yourself in the foot" kind of issues inferred above.  

    As to my question, it was less of "how to make esm work with outlook", but more is there any alternative. Point being, many of us admins are reluctantly switching over to Vista, and losing access to things we use regularly from our desktops.

  • Stephen Griffin - MSFT
    8 Oct 2008 3:24 PM

    You can put the ESM on another machine and remote to it, or put the ESM in a virtual machine and use the VM to manage Exchange.

  • Mike D
    15 Nov 2008 7:47 AM

    Will there be a version of this that can be installed on Windows 2008 server?  

    I would like to be able to manage the Exchange 2003 that is running in a virtual machine without having to fire up the Hyper-V console every time.  

    So I guess that would be Server 2008 x64 to be specific.

  • Georgestark
    14 Jul 2009 4:44 AM

    What is the point, most admins want to run ESM on there Vista workstaion the very reason for this is they are running exchange and therfore Outlook.it seem kind of pointless to create a VM without outlook so you can run Vista ESM.

    may aswell logon to the exchange server via RDP.

  • Ryan
    28 Sep 2010 6:29 AM

    I understand that there are issues with installing ESM along side Outlook, but what are the options available to software developers?

    Specifically, I my team is writing a .Net application that needs to create email accounts and Mailboxes.  This task requires the CDOEXM.dll, which is a part of ESM.  I am at a crossroads, because I can't ask the development team to uninstall their Outlook (nor do I want to ask them to do any hacks that could potentially screw up their workstations).

  • Stephen Griffin - MSFT
    28 Sep 2010 6:34 AM

    I personally keep my Outlook/tools machine seperate from my development machine.

Page 1 of 1 (13 items)
Leave a Comment
  • Please add 4 and 6 and type the answer here:
  • Post
  • © 2012 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy Statement
  • Report Abuse
  • 5.6.131.143