Active Director - Open Source Administration Toolkit
Active Director's Home

What is the "Active Director"

The "Active Director" is an Open-Source Directory Administration Toolkit. It is based on Microsoft's ADSI and WMI components and provides a great set of automation tasks for NT Systems and LDAP Directory Services like Active Directory, OperLDAP or Novell Directory Services.

Some interesting features are

  • LoginSession & Password Management
  • Simplified Property Access and AutoConversion into readable formats
  • Change-Management and -RollOut abilities (TemplateSets and RequestSets)
  • Data Import/Export Plugins
  • Automated logging of each applied change
  • Mailbox Inegration (Exchange 5.5 / 2000 / 2003 and POP3)
  • FileSystem Integration (Management and Reporting for Files, Directories and ACLs)
  • WMI Integration (Remote Workstation and Server Management Tasks)
  • Job/Task System
  • "Scripted" extention standard

Development and Releases

This project started as a simple ADSI automation Tool but it was extended to support more than only attribute changes. So it is quite difficult to define a development status. Current releases are published in alpha-state, because not all planned features are available or working, but the core functionality is still stable and tested in more than thousand change requests. So don't be confused that a "part" of the Director (the DAF) is already in beta state, but the whole project is published as alpha-software.

Available releases:

  • Alpha (Keryx-series):
    DAF Core is beta software, DAF extensions are under development (alpha) and may be changed in later releases, the "elementar" parts of the GUI are beta software too, but some features are still missing or will be changed to grant a better performance and usability.

  • Beta / Productive (Trismegistos-series):
    • Beta releases: Most parts of the Director are ready for productive use, but some are untested or still not complete. The whole project must be binary compatible to later releases (so all later releases have to be binary compatible with earlier [beta or productive] releases too).
    • Productive releases: are tested and ready for productive usage in each environment (starting with single workstations up to enterprises with thousands of systems). It is not allowed to alter existing interfaces (only new ones can be added). The primary development focus remains on optimizing and debugging existing code.

© 2007 - cNx