Maqsood Bhatti - iDENTITY

Sometimes there is a need for us (Consultants) to see a snapshot of all the changes that happened on the Active directory side while the Novell AD IDM driver was stopped or was not running, before we decide to start the AD driver. Since Novell Identity Manager currently allows us to see all the events which happened in the Identity vault only, but not on the AD side, I decided to write such a tool myself, and of course wanted to share this tool with the consultants/community out there. It's a .NET 2.0 WinForm application, written in C# programming language. To run this tool you should have at minimum: .NET 2.0 framework installed, ( Not supported on the Linux platforms yet) This application must be run under the same user which is configured on the AD driver. Short Tutorial (How To): When you run the application (ADCView.exe), the application automatically discovers the current domain, a domain controller, and default domain naming context in the user logged in domain automatically...

Usually when you want to purge the event cache on the IdM driver, you usually put the driver state to disabled first and hitting it back to enabled state will work out. but that kills only the events which were waiting on the Subscriber ends... What about the purgeing events on the publiser end ???? My Scenario: I was running a IDM 3.5.1 MAD driver between IDVault and Microsoft Active Directory, loading driver shim with Remote Loader on the other end. I wanted to purge events waiting on the publisher end. the solution came out something like this: a) on the dirver object there is an attribute called DirXML-DriverStorage. Delete it. b) On the other end (where your remote loader is up and running). Delete the driver state file _DriverObjectDNAndDriverName>.xml. c) Now start the Driver Engine and Remote Loader..