We have received several support calls in the past months relating to migrating Exchange Event Service Scripts from Exchange 5.5 to Exchange 2003. Because it isn’t straightforward or documented (to my knowledge), I came up with this information to help you get your scripts working in Ex 2000. This should only be migration step and I don’t encourage new development to utilize this technology. ...

Summary Using PR_URL_COMPNAME to bind to an item in WebDAV from CDO/MAPI involves understanding the encoding rules for the Exchange version where the item is homed. These rules are different and incompatiable between Exchange 2000, Exchange 2000...

...Don't know if many people try to use this anymore but it is worth noting... SYMPTOM Receive MAPI_E_FAILONEPROVIDER when attempting to log on anonymously to Exchange 200x using CDO 1.21. ...OR... After anonymous log on to Exchange...

The Exchange Team has a great new post on the future of Public Folders in Exchange 12 and understanding how they are implemented.  Be sure to read this post if you are thinking about moving to Exchange 12 and/or Outlook 2007, this article will provide...

For those of use who have fought with Exchange account permissions, here is a concise description of the minimum requirements for service account setup to access mailboxes... http://blogs.technet.com/exchange/archive/2006/01/25/418099.aspx To...

Coming from Exchange 5.5 Event Service Scripts to Exchange Store Event Sinks involves more than just understanding the new events available and the registration process. Exchange 5.5 event scripts are written in VBScript with CDO 1.21 as the API to interact...

This is the first part of a two part series on getting started with and understanding Exchange Store Event Sinks.  This is especially important for all of those people moving from Exchange 5.5 to Exchange 2003, there is a lot to learn with store...

Well all good things must come to an end, on December 31, 2005 Exchange 5.5 reached the end of its lifecycle.  For me it is the server that started it all, I started my career in Messaging Development against Exchange 5.5 in the consulting world...

The following article details some of the limitations of Exchange Server Event Scripting (available in Exchange 5.5).  With the availability of Exchange Event Sinks in Exchange 2000/2003 it is really hard to rationalize continued use of this technology...

...I added a new category for this post called "KB" which is for noting KB articles that are new or important... The Outlook Object Model does not provide full access to all the features of the application. The following KB article details some of...

FYI IMO there a lot of TLA's out there these days. Some acronyms get pronounced phonetically like ISAPI ("eye-sap-ee") and MAPI ("map-ee") while others are enunciated simply by reading the letters like ESM ("E-S-M") and NTFS ("N-T-F-S"). Usually the presence...

A couple days ago I posted a link to upcoming Outlook Object Model changes and new features, I wanted to go back and note that the Exchange team posted about their developer roadmap as well. This post mentions three new ways of interfacing with Exchange...

The Exchange Team's Blog has a great post on how certain time zones with variable daylight time shifting affect Outlook... ... Time zones are an important thing to keep in mind when working with appointments. We get cases sometimes related to preceived...

WebDAV can be a little cumbersome to work with. To be honest I'm never thrilled to use it, but that is only because of the way you interface with Exchange using WebDAV. WebDAV is a protocol, not an API. It is an extension of HTTP and provides more request methods to allow us to get information out of Exchange and change information within it. We have a lot of technologies at our disposal for Messaging developments so it is always important to be reminded of when to use what technology. Here...

...I added a new category to the blog, you will see it is called OUTBOX. As a support engineer I send out a lot of mail that could be useful to everyone. You shouldn't have to open a support case just to get this information. So here I'll provide some...

It's late so I'm going to keep this brief but since we don't have any public content I wanted to get the word out. Exchange's CDO 1.21 was never tested and will not work with Kerberos authentication. While Outlook's version of CDO 1.21 does have Kerberos...

Ryan Gregg, an Outlook 12 PM, gives an enticing preview of the enhancements and new features of the Outlook Object Model to be available in O12. ...At first glance this is very exciting. I look forward to these changes, improvements, and additions...

While we are on the topic of System.Web.Mail , it is important to note a new namespace in version 2.0 of the .NET Framework. There is a brand new namespace for sending mail via managed code, it is called System.Net.Mail . Have no fear, System.Web.Mail...

One of the principles of the Information Age is that anybody with a blog like mine or a Code Project account can write an article viewable to millions of people around the world. As a support engineer, I love and hate this at the same time. Take the following Code Project article for example......

There is a new strain of the Sober virus roaming inboxes lately. Yahoo has more . The virus arrives in an email with an attachment. Many of the messages will proclaim they are from the CIA or FBI asking you to open the attachment to answer some questions...

I had a customer email me today saying they resolved their CDO problem by installing SP 2 on their Exchange server and installing Outlook 2003. Big mistake! It's unfortunate and common but so many people put their Exchange implementations at risk by installing...

As more and more developers move to managed code (.NET), especially with the release of Visual Studio 2005, it is important to be reminded of what current API's are supported for use in managed code and which are not. The following KB article is a must...

I don't get any kickbacks I swear. Check out MaxiVista it is truly a great product a number of people here use everyday. It is a simple client/server application that provides software based multi-monitor and KVM functionality. ...Really, I don't have...

The Exchange Team has a great post clarifying that Exchange 2003 IS supported on x64 hardware, just not on a 64 bit OS. ...There was some confusion as to whether Exchange 2003 would run on x64 hardware. Customers were understandably frustrated because...

...It was just too easy to steal from the Exchange Team's blog but I couldn't help myself Welcome to my new blog, it goes well with my new job! My name is Matt Stehle and I'm a developer support engineer at Microsoft at the Charlotte campus. I work...