Novell Home

AD Synchronization with the DirXML Starter Pack

Novell Cool Solutions: Tip
By Troy Griese

Digg This - Slashdot This

Posted: 21 Apr 2005
 

Introduction

This guide helps you set up Microsoft Active Directory synchronization, including passwords, with the DirXML starter pack. It begins with a NetWare 5.1 environment and upgrades to the NetWare 6.5 SP1b overlay.

Environment

This setup was tested in the following environment:

  • NetWare 5.1 sp5, with eDirectory 8.7.0.3
  • Windows NT 4.0 domain
  • Windows 2000 DNS

Resources

The following resources were used:

  • NetWare 6.5 sp1b overlay
  • DirXML iso CD from 6.5 install
  • Windows 2003
  • DirXML 1.1a Plug-in for iManager 2.0.x download (DirXML_Plugins.npm.zip)
  • dradcu1 update
  • dradpt3 update
  • PATTLNK_712003_225-w3k.zip

Assumptions

This guide assumes that a flat, bi-directional sync of AD (2003) and eDirectory is used. It also assumes that the driver was set up to sync users created in AD to an OU named ADUsers, in the eDir Tree.

Setup Tasks

Here are the basic setup tasks explained in the guide:

  1. Do a NAM reverse migration.
  2. Perform a Windows 2003 upgrade if necessary.
  3. Install Active Directory.
  4. Upgrade to NetWare 6.5 if necessary.
  5. Install the DirXML Engine.
  6. Install the iManager Plug-ins.
  7. Prepare the eDirectory certificate for SSL.
  8. Create the AD structure.
  9. Create the DirXML Admin user in AD and assign rights.
  10. Determine the AD GUID.
  11. Install the Remote Loader on DC.
  12. Install files from the DRADCUL update.
  13. Set up RemoteLoader.
  14. Set up the AD Driver.
  15. Do miscellaneous setup tasks.
  16. Customize the driver.
  17. Test the setup and synchronization.
  18. Migrate existing AD users.

Task 1: NAM Reverse Migration (on BDCs first)

  1. Go to Add/Remove Programs and remove the NDS for NT files.
  2. Reboot as necessary.
  3. Make sure SAM gets synced after rebooting.
  4. Remove (power off) one BDC from the network for disaster recovery purposes.
  5. Repeat all of the above steps for any other BDCs first, then for the PDC.

Task 2: 2003 UPGRADE on PDC

Insert the Windows 2003 CD and perform the upgrade. Upon successful 2003 upgrade and boot, the AD Installation Wizard will start.

Task 3: Install Active Directory

  1. Select Domain in a new forest.
  2. Supply the Full DNS name for new domain (such as ABC.net).
  3. Select the Forest Functional level (use Windows Server 2003 interim; i.e., no Windows 2000 domain controllers).
  4. Use defaults for the database and log folders.
  5. Use the default Shared System Volume.
  6. In the DNS Registration Diagnostics, look for "The operation completed successfully."
  7. Set Permissions compatible with pre-Windows 2000 server operating systems.
  8. Set the Directory Services Restore Mode Administrator Password.
  9. Review the Summary data.
  10. Complete the Active Directory Installation Wizard.
  11. Restart the server.
  12. After reboot, choose Log in to Workstation Only and install the 4.9 client (if you're using a 4.83 client, and it fails to start).

Task 4. NetWare 6.5 Upgrade (Master replica holder of Root)

  1. Install sp6 on the NetWare 5.1 server if necessary.
  2. To prepare for the new eDirectory version, run NWDEPLOY from 6.5 CD. This extends the schema - make sure it synced properly with the other servers.
  3. Run the Server Health Utility with NWDEPLOY from 6.5 CD.
  4. Check the following NetWare 6.5 Upgrade Requirements before continuing:


  5. *NetWare 5.1 sp6 installed
    *2GB of available SYS vol space
    *200MB of available DOS partition space
    *512MB of RAM
    *Pentium II or better
    *You may need to set FILES=50 BUFFERS=30 in config.sys.

  6. After all of the checks, put the upgrade CD in the NetWare server.
  7. Start the GUI (startx), select the install option and browse to the CD. I chose to back up boot files, not to automatically reboot, not to allow unsupported drivers. I also chose to use a manual upgrade type, overwrite newer files, and select all NMAS methods. Then I installed apache2, iprint, Refresh NFA methods, and iManager.
  8. Reboot until everything comes up OK.

Task 5: Install the DirXML Engine

    With the DirXML iso CD install from the NetWare GUI (nw\product.ni), install everything but the Novell iManager Plug-ins for DirXML.

    Remove any unnecessary pre-configured drivers. I did not overwrite statuslg.nlm when prompted.

Task 6: Install iManager Plug-ins

  1. Install the updated DirXML 1.1a Plug-in for iManager 2.0.x (DirXML_Plugins.npm.zip) according to TID 10088503.
  2. Open a browser from a workstation and go to http://server/nps/iManager.html
  3. Click Configure.
  4. In the left pane under Module Configuration, choose Install Module Package.
  5. Browse to the Plugins for iManager 2.0.x\packages directory on the CD.
  6. Select the .npm file and click Install.
  7. Continue until all of the .npm files have been installed.
  8. Stop (tc4stop) and start (tomcat4) the tomcat web services.

Task 7: Prepare the eDirectory Certificate for SSL

Note: For details, see TID 10083691.

  1. From the DC, start ConsoleOne from the 6.5 NDS server.
  2. Select the context where the server exists.
  3. Select File | New | Object and choose NDSPKI:Key Material.
  4. Select the appropriate server, name the certificate "DirXML-Cert" and leave it on Standard.
  5. Export the Trusted Root Certificate.
  6. View the properties of the certificate.
  7. Select the Trusted Root Certificate from the Certificates dropdown.
  8. Click the Export button, check "No" on the Private key, and use the Base64 format (note the location).

Task 8: Create the AD Structure

  1. Open Active Directory Users and Computers.
  2. Right-click the Domain Object (ABC.net), select New, and choose Organizational Unit.
  3. Name it appropriately (I used the tree name) and click OK.

Task 9: Create the DirXML Admin User in AD and Assign Rights

  1. Open Active Directory Users and Computers.
  2. Right-click the OU for the user, select New, and choose User.
  3. Name it "dirxml-admin", give it a password, and select Password Never Expires.
  4. Open Active Directory Users and Computers again.
  5. Select Built-in, choose Administrators, add dirxml-admin, click OK and close the app.
  6. Open the Domain Controller Security Policy from Administrative Tools.
  7. Add dirxml-admin to Log on as a Service, under User Rights Assignment, under Local Policies.
  8. Reboot the server to apply the policies.

Task 10: Determine the AD GUID

  1. From the PC, configure the AD driver (via iManager).
  2. Run the ADShimDiscoveryTool.exe utility from the DirXML ISO CD (utilities\ad_disc\ADShimDisco?veryTool.exe).
  3. Choose the Paste the File option after the information has been obtained.

Install the Remote Loader on DC

  1. Let the DirXML ISO CD auto-run on the DC.
  2. Select DirXML Remote Loader and Drivers.
  3. Select the DirXML Remote Loader Service and PasswordSync Agent.
  4. Choose the Remote Loader and DirXML Driver 2.1.1 for Active Directory options.

Task 11: Update Files from DRADCUL

Note: For details on the DRADCUL update see TID 2964748.

  1. From the DRADCUL update, copy AD-Driver*.xl* to:
    sys:tomcat\4\webapps\nps\dirxm?l.drivers
    sys:public\mgmt\consoleone\1.2?\snapins\dirxml
  2. Run the dvr_ext.sch schema extension from the DRADCUL update (use the NWConfig - directory options).
  3. Copy addriver.dll from dradpt3 and update to c:\novell\remoteloader

Task 12: RemoteLoader Setup

  1. Start the DirXML RemoteLoader Configuration Wizard from the desktop of the DC. Accept the defaults until it prompts for the SSL Trusted root file.
  2. Copy the file you exported for the Trusted root to the c:\novell\remoteloader directory.
  3. Select that file for this option.
  4. Change the Trace level to 3.
  5. Create a directory named c:\novell\remoteloader\log_fil?es
  6. Supply the Trace file name of c:\novell\remoteloader\log_files\8000trace.log Provide passwords.
  7. Start the service when prompted.

Task 13: AD Driver Setup

  1. Open iManager and expand the DirXML Management option in the left pane
  2. Select Import Drivers and then "In a new driver set"
  3. Supply a name (DirXML-TREENAME), context MRMC, server name and leave new partition selected
  4. Select AD Driver Configuration
  5. Supply the following names for the configuration:

    AD-Driver-TREENAME
    authoritative id: dirxml-ad...@ABC.net
    authentication server: (leave blank)
    domaind GUID: (from the ADShimDiscoveryTool file on the desktop)
    data-flow: bidirectional
    AD base container: OU=TREENAME,DC=ABC,DC=net
    eDir base container: .TREENAME. (browse to this)
    publisher placement: flat
    subscriber placement: flat
    driver polling: 1 min
    secure authentication: yes
    enable passwordsync: yes
    driver: remote
    remote host: servername.abc.net 8090
    passwords:
    exchange 2000: no


  6. Add appropriate security equivalences and exclude admin roles.
  7. Finish with the overview.

Task 14: PasswordSync Setup

  1. Open the Password Synchronization option from the DC Control Panel.
  2. Supply the Tree name.
  3. Select the Domain and the DirXML-Driver.
  4. Accept defaults for the Password Sync Object.
  5. Select the top of the tree for the container rights screen.
  6. Install the filter on the domain controller(s).
  7. Select the domain controller from the list and click the add button.
  8. Reboot the domain controller.

Important: After rebooting, edit the Novell Password Synchronization Service to "Interact with Desktop"

Task 15: Miscellaneous Setup Tasks

First, you need to assign rights for the AD-Driver object. To do this, add supervisor object and property rights for the AD-Driver-TREENAME object to [Root].

Then add the key parameters for SSL:

  1. In ConsoleOne (or iManager), edit the properties of the AD-Driver-TREENAME object.
  2. Remove the Auth ID (dirxml-ad...@acme.net)
  3. Add kmo="DirXML-Cert - servername" to the end of the Remote Loader.

Next, set up the Connection Parameters:

  1. Provide the passwords.
  2. Select the Secure Authentication and SSL option from the Driver Parameters tab.
  3. Click OK.

Task 16: Customizing the Driver

  1. Change the AD subscriber channel to put new users in the OULEVEL1\ADUsers context. It should read:
    <placement>\TREENAME\OULEVEL1\?ADUsers\<copy-name/>
  2. Add AD-Win2003-OutputTransformSS (see TID 10084602).
  3. Open ConsoleOne from MIDFS08.
  4. Select Create a New Application Driver under Wizards.
  5. Choose the existing Driver Set.
  6. Select the AD-Win2003-OTS.xml file.
  7. Provide the CN of the AD Driver (should be AD-Driver-Treename) and the Domain name (acme.net).

After importing chain the StyleSheet,

  1. In ConsoleOne, open the properties of OutputTransformSS.
  2. From the Other tab, click Add and choose DirXML-NextTransformation.
  3. Browse to find the AD-Win2003-OutputTransformSS object.
  4. Click OK.

Task 17: Testing

Start it up! The DC Remote Loader should be waiting for the SSL connection.

  1. Start the driver from iManager.
  2. Verify from DC that it started correctly.

To test the synchronization,

  1. Create a User in eDirectory and AD.
  2. Verify that the user copied over correctly.
  3. Modify the user in eDirectory and AD. Verify that the changes are reflected properly.
  4. Change the password and verify that it synchs correctly.

Task 18: Migrate Existing Users

First, update the userPrincipalName attribute on AD DC (because NT to AD migration left it blank). See the Microsoft Knowledge Base Article 237677 for details on ldifde.

Then, export the userlist from DC as follows:

ldifde -f c:\ldifout.txt -s ADSERVERNAME -r 
"(objectCategory=CN=Person,CN=?Schema,CN=Configuration,DC=mid?michigan,DC=net) 
" -l cn 

Finally, create and run the ldifchanger.bat file as follows:

        @echo off
       del c:\ldifimport.txt
       for /f "tokens=1*" %%i in (c:\ldifout.txt) do (
           if "%%i" == "dn:" echo %%i %%j>>c:\ldifimport.txt
           if "%%i" =="cn:" (
               echo changetype: modify>>c:\ldifimport.txt
               echo add: userPrincipalName>>c:\ldifimport.txt
               echo userPrincipalName:%%j@ABC.net>>c:\ldifimport.txt
               echo ->>c:\ldifimport.txt
               echo.>>c:\ldifimport.txt
           )
       )


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell