Installing Novell Account Management 2.1 on Windows 2000 with eDirectory

(Last modified: 25Mar2003)

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

goal

Installing Novell Account Management 2.1 on Windows 2000 with eDirectory 8.6.2

Installing Novell Account Management 2.1 on Windows 2000 with eDirectory 8.7

fact

Novell eDirectory 8.6.2 for Windows 2000

Novell eDirectory 8.7 for Windows 2000

Novell Account Management 2.1 for Windows 2000

symptom

Install Novell Account Management 2.1

Errors installing Novell Account Management

fix

To install Novell Account Management 2.1 on a Windows 2000 server running eDirectory 8.6.2 or greater use the following steps.

Important: Verify that Client version 4.83 is running on the Windows 2000 server.
Verify that WINS is properly configured and functional on the Windows 2000 server.
Verify that the Windows 2000 server is obtaining time from an NTP time source.

1. Download and install eDirectory 8.6.2 or greater from http://download.novell.com (Click "Category" | Choose "eDirectory" | Click "Submit Search")

2. During install of eDirectory, install Console One with all the Snap-in's

3. Download NICI 1.57 for Windows 2000 from http://download.novell.com. (Click "Category" | Choose "Novell International Cryptographic Infrastructure" | Click "Submit Search")
       A. Stop the NDS Server Service (Start | Programs | Administrative tools | Services | Double Click NDS Server | Press Stop)
       B. Run WCNICIU0.EXE
       C. Reboot the server.

NOTE: Installing NICI 1.57 is critical for this product to work properly with eDirectory 8.6.2 or greater. If NICI 1.57 is not installed, Account Management 2.1 for Windows 2000 will not work. The DIRXML.DLM service will not start and the driver will not start.

4. If you are running eDirectory 8.7, you already have the latest NICI. Proceed to step 5. If you are running eDirectory 8.6.2, download NICI 2.4.x for Windows 2000 from http://download.novell.com. (Click "Category" | Choose "Novell International Cryptographic Infrastructure" | Click "Submit Search")
       A. Stop the NDS Server Service (Start | Programs | Administrative tools | Services | Double Click NDS Server | Press Stop)
       B. Run WCNICIU0.EXE
       C. Reboot the server.

5. Download the DirXML 1.0 schema patch (DXNTP1.EXE) and extract it to its own folder on the Windows 2000 server.
       A. Start | Control Panel | NDS Services | Highlight the INSTALL.DLM | Click Start
       B.   Choose "Install additional schema files." | Click Next | Authenticate as Admin, or one having rights to extend schema.
       C.   Browse to the file VRSCHEMA.SCH, which is in the DIRXML\SCHEMA folder of the extracted dxntp1.exe patch | Click Finish.

6. Install Account Management 2.1 for 2000/NT using the Account Management sp1 overlay patch (AMW2KSP1.EXE).
       A. Take the original Account Management for Windows 2000 CD and copy it to a harddrive.
       B. Extract or Unzip NAMUPD.ZIP to the root where the Account Management CD was copied too. When prompted, choose to overwrite existing files.
       C. Execute Setup.exe to begin the patched Novell Account Management 2.1 install.

7. During the install of Account Management, Console One will detect that there is a newer version stating "A newer version of ConsoleOne has been installed. To install snapins, continue the install.  To install this version of ConsoleOne, uninstall ConsoleOne before continuing." Click OK | Deselect All and then choose ONLY the following 3 Snapins:
       DirXML Snapins
       NT Directory Integration Snapins
       Account Management for Windows 2000 Snapins

8. Reboot the server after the install of Account Management 2.1 for Windows 2000 has completed.

9. Once the server comes back up and authenticate to NDS has occurred, a final note that the Password Sync Services have finished installing will be displayed. Note that the filter is running.

10. To verify that the DirXML driver has started properly, Launch ConsoleOne, Browse to the DirXML Driver Set | Right Click | Properties | On DirXML tab choose Drivers from the drop down list. Verify that the driver is "Running".  If it is not running, highlight the driver and Click Start.

11. As a final note, make sure that the Windows 2000 server holds at least a Read/Write replica of all partitions of user objects you plan to incorporate into Active Directory using the AM 2.1 product. The DirXML piece will not work unless the local Active Directory box holds at least a R/W replica.

NOTE: In a couple of cases, the following has occurred. To check for this special case, after the reboot of the server launch the NDS Services applet from Control Panel and make sure that dirxml.dlm is in the list. If it is not, browse to the directory where NDS is installed (usually C:\Novell\NDS). The dirxml.dlm and dirxmllib.dll files will be in the directory but the file names will be in all UPPERCASE. Rename both files to the identical names but in lowercase. Shutdown the NDS Server from the NDS Services applet and then Startup the NDS Server again. dirxml.dlm should now show up in the list and should be "Running".

NOTE: When reinstalling Account Management on a server, run the install on the Win2k server from the Win2k directory on the NAM overlay to get all components installed (DirXML components)

For additional information on eDirectory 8.6 on the WindowsNT/2000 platform, please see the following solution. TID #10066903 - eDirectory 8.6.1 Readme Addendum - Windows NT/2000

For additional information on eDirectory 8.6, please see the following solution. TID #10066455 - eDirectory 8.6.1 Readme Addendum

For additional information on eDirectory 8.7, please see the following solution. NOVL81742 - eDirectory 8.7 Readme Addendum [no longer available]

document

Document Title:	Installing Novell Account Management 2.1 on Windows 2000 with eDirectory
Document ID:	10069401
Solution ID:	NOVL75001
Creation Date:	22Mar2002
Modified Date:	25Mar2003
Novell Product Class:	NetWare Novell eDirectory

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.