KB: Suitable Applications for Exchange Server Event Scripting

  • Comments 2

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.  Especially for mission critical applications...

181036 INFO: Suitable Applications for Exchange Server Event Scripting
http://support.microsoft.com/default.aspx?scid=kb;EN-US;181036

Most notable from this article are the following...

"There is no guarantee that a script will see every message."

"The Event Service is single-threaded. No matter how many scripts are registered, only one can run at a time."

"The Scripting Agent is not a safe, general purpose replacement for the Inbox Assistant rules because it allows new code to be installed and run on your servers."

One major consideration between Event Scripts and Event Sinks is that Scripts use CDO 1.21 as their API while Sinks use CDOEX.  It is often suprising have minor the code changes can be for simple script migration.  CDOEX is a better performing and more robust API, adding to the list of reasons to make the switch.

...NOTE: This is what I refer to as Event Scripts in this article...

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnexch55/html/msdn_eventscr.asp

...You can create Exchange Event Sinks using VBScript, these scripts wouldn't have the limitations listed above.  The KB article below provides a sample event sink script...

http://support.microsoft.com/?kbid=324021

Updated 1/22/2009 – Noted a broken link.

  • 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
  • This is the first part of a two part series on getting started with and understanding Exchange Store

Page 1 of 1 (2 items)