I installed NNLS on a Dell 2650 dual 2.6-GHz Xeon running Red Hat AS 2.1. Installation was painless, and services were ready for configuration within half an hour. NNLS configuration can be accomplished remotely using a browser: Internet Explorer 5.5 or higher, or Netscape 7.02 or higher.
Included with NNLS are preactivated DirXML drivers for Active Directory, eDirectory and NT Domains. I chose to configure NNLS as a primary tree for NWC Inc., rather than designate it as a secondary tree under our Active Directory server. This let me toy with NNLS' DirXML and, later, identity services to integrate with Active Directory. (Alternatively, you could integrate NNLS with existing directory implementations during installation.)
The iManager 2.0.1 component lets you manage every aspect of NNLS from a tree-based, object hierarchy. Supporting HP-UX, Linux, NetWare, Solaris and Windows, iManager installs as a collection of Java servlets running on Apache/ Tomcat, which is included with the base product. I easily created objects, including users, groups and other familiar eDirectory-based objects, from within the interface.
NNLS provides a big time-saver: an import/export wizard. Instead of re-creating users, I simply imported them from the NWC Inc. Active Directory server. If you're familiar with LDAP, you'll find the integration with directories a breeze.
The inclusion of Nsure Audit gives administrators notification and logging capabilities. I configured NNLS to notify me regarding events related to eDirectory (objects created/ deleted/modified, login/logout), the file system (directories and individual files) and NetWare instrumentation (server down, volumes mounted/ dismounted, protocols bound).