Setting Up NT Domain

While you set up the NT system, have your NT Administrator work with you.

NOTE:  Details about driver architecture and driver/application relationships are discussed in the driver implementation guides. You can reference driver implementation guides on the Novell Documentation Web Site.

To prepare a lab workstation to provision NT Domain users, complete the following sections:


Prerequisites

The computer where you will install Remote Loader and the driver must be running the following software:


Collecting Configuration Information

You'll need to provide a number of system-specific details when you install and configure Novell Nsure Resources for NT Domain. Some of these details can be collected before you complete the following procedures, others will be defined during the process.

Print and complete the Import Driver Form for NT Domain, which mirrors the actual form you will fill out in iManager, or print the following table and record information there.

System Value

 

Domain Server

 

Domain Name

NOTE:  If you are also synchronizing Exchange 5.5 data, the domains must be the same.

 

Authoritative User

(See Creating an Authoritative User .)

 

Password

(See Creating an Authoritative User .)

 

IP Address and Port Number the for Remote Loader (Remote Host Name and Port)

(See Installing and Configuring the Remote Loader and Driver .)

 

Driver Object Password

(See Installing and Configuring the Remote Loader and Driver .)

 

Remote Loader Password

(See Installing and Configuring the Remote Loader and Driver .)

 

Creating an Authoritative User

The driver needs Read/Write rights to the domain. You can configure the driver to use any existing account with the appropriate rights, or to ease future management, you can create a new account to be used exclusively by the driver. If you are also using the Exchange 5.5 driver, you can use a single authoritative user for both drivers.


Granting Rights to the Driver

You need to grant rights to the driver so that it can access the SAM keys in the registry of the server that has the domain you want to use.

Creating an Administrator equivalent gives the driver rights to read and write to the domain, but, by default, even the Administrator cannot access the registry until you explicitly assign that access.

  1. Log in to NT as Administrator.

  2. Run regedt32.

  3. Select the HKEY_LOCAL_MACHINE window.

  4. Select the SAM key, then go to the Security menu and select Permissions.

  5. Check the Replace Permission on Existing Subkeys check box.

  6. Give Full Control permission to Administrators, then click OK.

  7. Click Yes to replace the permission on all existing subkeys within SAM.

  8. Close the registry.


Installing and Configuring the Remote Loader and Driver

If you are running another DirXML Remote Loader service on this computer, such as the Remote Loader for the Exchange driver, stop that service before starting this procedure. Restart the service after completing this Remote Loader installation.

  1. Insert the Novell Nsure Resources CD and click Next at the Welcome screen.

  2. At the License page, click I Accept.

  3. At the Components dialog box, select DirXML Remote Loader Service, then click Next.

  4. Accept the default installation path for the Remote Loader, then click Next.

  5. Mark the following items, then click Next.

  6. Review the Product Summary, then click Finish to install Remote Loader files.

  7. When prompted, create a shortcut.

  8. Run the DirXML Remote Loader Configuration Wizard from your desktop.

  9. At the Welcome page, click Next.

  10. Keep the default Command Port number, then click Next.

  11. Keep the default Configuration File Name, then click Next.

  12. In the DirXML Driver dialog box, mark Native, browse to the NT Domain driver, c:\Novell\Remoteloader\NTDomainShim.dll, then click Next.

  13. In the Connection to DirXML dialog box, leave the default Port settings, and ensure that Use SSL is unchecked.

  14. Record the port number in the table under Collecting Configuration Information , then click Next. This information will be required later during driver parameter configuration.

  15. Set Trace Level to 3, so that you'll get minimal tracking data for troubleshooting, specify a location and filename for the trace file, then click Next.

    NOTE:  If you are running multiple Remote Loader sessions on a single computer, you should create separate trace files.

  16. Mark Install the Remote Loader Instance as a Service, then click Next.

  17. Set Remote Loader and Driver Object passwords.

    We recommend keeping remote passwords and driver passwords the same across systems and change it later when you go to production. Record the passwords in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.

  18. Review the summary, then click Finish.

  19. When prompted, start the service.

    The NT system is prepared to provision resources to employees. Complete preparation of other participating systems and then proceed to Configuring DirXML Drivers .