I work for a school district in North Texas and I am thinking about moving away from eDirectory to active directory. I have been thinking about this for almost a year now. Is this the best thing to do, the pros and cons.

Reason I am thinking of moving is cause of instructional software. Almost all the instructional software that is coming out and the administrators want to use is built for microsoft servers and active directory. I mean it is getting harder and harder to find an instructional app that is not built soley for microsoft.

It just seems like the logical choice. I mean we only use novell servers for directory services, storage and printing…..I mean I can do the same things with microsoft servers and can allow the instructional folks to purchase what they need and want.

Another thing is there is no ( or i just havn’t found it yet ) support groups for novell in north texas. Funny, I know of 4 very large north texas school districts and one of which is one of the fastest growing cites & school districts in the nation that use only Novell and have a combined computer count of over 250,000 and I can’t seem to find a support group.

some one help me choose please!!!

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

Leave a Comment

  • srbeckett says:

    You may want to contact your reseller or Novell directly about implementing Domain Services for Windows in OES2sp1. Or at least the beta of the product. It should allow you to present all the users as an AD Forest / Tree so that the applications will read the users natively.

  • 6014670 says:

    Everyone’s facing that decision lately, but one of the things you’ll need to ask yourself and really look into is how much hardware is AD going to take. How spread out are your schools, locations, etc.. that will need to authenticate. More than likely, you’ll need more hardware. And do you have the staff to help support the move to Exchange and AD? Sounds like you need to try to bring in a non-biased consultant (hard to find these days) to help you figure out the approximately “true” cost to move to AD from eDir.

    We won’t be getting rid of eDir for AD at our college, but at some point we’ll have to integrate AD with eDir. We have IDM in place, but our LDAP store is our master, not eDir. We’ve got a very mixed environment though with Linux, Unix, MS, and Novell products.

    Good luck! And you might want to try to join a group “virtually” if you don’t have one locally. WMNUG welcomes virtual users and we have lots of out of state folks as virtual members.

  • mjb247 says:

    I am curious, it seems that their are three choices here. Novell (Legacy installed equipment), Full bore MS ($$) or an integrated approach of Active Directory,eDirectory, LDAP and Linux. You may be able to save a lot of Money implementing a Linux application services. Their are many great portals and Knowledge learning tools that are GNU.

    Linux can be integrated with AD and authenticate via LDAP. Why does it always seem like MS is the only way to go. Microsoft sure would like you to believe that, they are the only way to go.

    Comments from a former MCNI, MCT & CIW trainer.

Jan 8, 2008
7:24 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow