Here are a couple of interesting KBs that have come out or been updated recently:
KB.884863 (http://support.microsoft.com/kb/884863) – “Update to Exchange 2000 Server adds application event logging for deletion of public folders”
An additional feature that is related to public folder diagnostics logging is now available for Microsoft Exchange 2000 Server. When you use this new functionality, an event is generated in the Event Viewer Application log when a user deletes an Exchange 2000 public folder. If the Public Folders General category is set to Medium logging or higher, an event that similar to the following will be logged when a user deletes a public folder in Microsoft Exchange 2000 Server:
Can I ask you one question regarding Exchange clustering and event sinks?
We have two node active/passive Exchange 2003 cluster.
COM+ applications which holds the event sink dll installed on both nodes.
Then we register event sink globally on mailbox and public folders stores on active node.
Now everything works fine - event sink process messages.
Then we failover to second node, so it become active.
After that the event sink is not triggered at all.
The event sink registration records is present (I can check this through Exchange Explorer).
If we re-register (remove this records and create again) then the event sink will start receive events and function properly.
Thus, to make event sink failover compatible we need to create cluster resource that depends on Information store resource and re-register event sinks on failover.
Question: Is this a normal behaviour or I miss something? And what is the reason of fact that we need to re-register event sink?
The only bad thing is that sink re-registration is not very fast process and some messages may pass through before it completes after failover.
Thanks in advance.
I forgot to leave my e-mail: shlibanov(at)mapilab.com