Novell Home

My Favorites

Close

Please to see your favorites.

Forcing NDS Edirectory 8.5 off of Solaris/Linux

(Last modified: 10Sep2003)

This document (10057888) is provided subject to the disclaimer at the end of this document.

goal

Forcing NDS Edirectory 8.5 off of Solaris/Linux

How to force the removal of NDS eDirectory 8.5 / Account Management on Solaris/Linux

fact

NDS eDirectory 8.5

NDS Account Management 2.1

Solaris 2.6

Solaris 7

Solaris 8 sparc

RedHat Linux

symptom

NDS is corrupt or needs to be removed off a Linux/Solaris server

fix

NOTE********:  THESE DIRECTIONS ARE NOT APPLICABLE FOR NDS eDIRECTORY / CORPORATE EDITION.  SEE TID #10052680 - Forcing NDS Edirectory off of Solaris FOR HELP WITH THESE PRODUCTS.********

The primary method for removing eDirectory 8.5 or Account Management 2.1 is to run the "nds-uninstall" script which can be found either on the product CD or in the /usr/sbin directory.  This script file will check for all installed products and will help you remove them.  The script should remove products that have corrupted or that were not completely installed as well.  If the nds-uninstall shell script fails to remove the product completely, call Novell Technical Support for further assistance.

Once the product has been removed, make sure that all applicable objects have been removed from NDS as well.  This includes LDAP, Security, Server, Workstation, and UNIX  Config objects.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10057888
  • Solution ID: NOVL30408
  • Creation Date: 24Oct2000
  • Modified Date: 10Sep2003
    • NovellNetWare

      eDirectory

Did this document solve your problem? Provide Feedback