Just a few things to take care about.
It should be a good idea to use the same NT Account for all Exchange
Services including the Event Service. However, this can be a potential
security problem. Please read the Exchange 5.5 Release Notes about that
Also you may create a separate mailbox and assign it the NT Account
which is used for the Event Service. Add your NT Account with user
permissions and use only this mailbox to create or modify Scripting
Agent scripts, because each scripting session is logged in with the
Microsoft Exchange Server identity of the last person who saved the
script. This behavior is described in the Exchange 5.5 Release Notes
Have you tried to logon on the local Exchange Server machine with the
account which has been used to install the Exchange Scripting Agent
script (the NT Account and mailbox of the last editor)?
Hope that helps
EcoNet Network Consulting
Subject: Script de* and exchange server
has anyone out there been able to use the script de* to step
exchange server event scripts? I've gotten sort of a runaround from
microsoft's tech support, and am looking for confirmation that this will
indeed work. the exchange documentation says something like 'you can
debug folder event scripts with the script de*. install IIS4 or
to install the de*. consult these products' documentation for
further info.' -- and of course the documentation for either says
about exchange server. putting a 'stop' command in the folder event
script launches the de* on the exchange server machine as it
but it doesn't come up with the script in it, and it doesn't stop the
script. the de* works fine with ASPs in IIS and with Outlook
form scripts, but not with server-based event scripts.
any comments would be greatly appreciated!