Copyright: Copyright ©Novell, Inc.


Architecture of NDS for NT

Applications that need information from the NT** domain make requests to SAMLIB.DLL. This includes applications run on the Windows NT** Server or an NT workstation. Some of the applications that require information from the NT domain are NT User Manager, NT Server Manager, and Microsoft** Exchange.

SAMLIB.DLL communicates to SAMSRV.DLL using Remote Procedure Calls (RPC). For applications being run on the server this is all done internally. For requests originating from a workstation, the RPC requests are received at the server via the network. Once the request is received by the server RPC, the request is extracted and passed to SAMSRV.DLL. SAMSRV.DLL then accesses the Windows NT Security Accounts Manager (SAM) where the NT domain name base is stored and performs the requested operation.

NDS* for NT integrates NT domains into NDS by replacing the NT SAMSRV.DLL with a new DLL that directs domain access calls to NDS. The new SAMSRV.DLL directs all requests from the domain to the NDS database through the IntranetWare Client. NDS can then be populated with User, Computer and Group objects that take the place of the objects previously used from the domain.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Contents

Understanding NDS for NT

What is NDS for NT?

Product Components and Licensing

How Network Users Benefit

How IntranetWare and NT Administrators Benefit

Architecture of NDS for NT

Frequently Asked Questions

Release Notes

Setting Up NDS for NT

Installation Instructions

Installing NDS for NT

Removing NDS for NT

Using NDS for NT

Managing Users

Managing Domain Users in NDS

Managing SQL Users in NDS

Managing Exchange Users in NDS

Integrating Domain Applications in NDS

Deploying Applications with NDS


Deploying Applications with NDS

Administrators typically spend a lot of time installing and managing applications.

Novell* Application Launcher* (NAL) 2.01 software lets you distribute applications to users' workstations and manage those applications as objects in the NDS tree.

Users access the applications that you assign them using the NAL Window and NAL Explorer components.

These components, or delivery mechanisms, display Application objects as clickable icons in a window or in the Windows** Explorer.


Frequently Asked Questions

What is NDS*?

NDS is a database of information, providing a list of objects that represent network resources, such as network users, servers, printers, print queues, and applications. Network administrators can use NDS to manage these network resources. For example, if a user named John wants to use a printer in a new area, the network administrator can grant rights to John to use the printer via the network.

The NDS Directory is stored on a server. On IntranetWare servers, these files are on volume SYS. For other operating systems hosting NDS, the NDS Directory is stored on the server's local drive in a subdirectory of the NDS installation directory.

See Understanding NDS for more information about NDS.

What is NDS for NT?

NDS for NT** allows interoperability between IntranetWare* and NT networks. NDS for NT provides single point of administration and single sign-on to the mixed network environment.

NDS for NT technology allows deployment of NT Servers and services, such as Microsoft Exchange, SQL Server, and SMS by allowing NT domains to be managed as NDS objects, thus eliminating the negative side effects of managing NT domains and the required trust relationships.

The NT authentication and access control to file, print, Exchange, SQL server, and SMS is handled by NDS.

What Happens to My NT Domains?

NDS for NT enables NT domains to be relocated to the NDS tree. The relocation, while transparent to the user, enables the NT domains to become manageable NDS Group objects, called Domain objects.

NDS for NT provides network administrators and users with all the benefits of NDS, while fully supporting domain-required applications.

Does the Domain Object Wizard Convert NT domain Trust Relationships into NDS Object Relationships?

Yes, trust relationships are preserved by NDS for NT. You will be able to view the NT domain trust relationships via MIcrosoft's Administrative tools.

Does the Domain Object Wizard Move More than One NT domain at a Time?

No, the Domain Object Wizard only moves one NT domain over to NDS at a time. You will need to run the NDS for NT installation for each Primary Domain Controller (PDC) and each Backup Domain Controller (PDC) you want to move to NDS.

Can I Go Back to an NT-Only Solution After Using NDS for NT?

Yes, you can return to an NT-only solution by uninstalling NDS for NT.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


How IntranetWare and NT Administrators Benefit

Network administrators from either the IntranetWare* side or the Windows NT** Server side will benefit from the interoperability and manageability of NDS for NT.

Some of these benefits include:

Single point of administration from anywhere on the network.

Single sign-on to the mixed IntranetWare/NT network.

The NT domain becomes equivalent to an NDS Group object.

Network administrators are given the preference on using IntranetWare or NT administrative tools. NDS for NT allows administrators to use NWAdmin or User Manager to modify or add users or other network resources.

Only a single object is needed per user.

No NT domain trusts relationships to manage.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


How Network Users Benefit

Network users working on a mixed IntranetWare*/Windows NT** network benefit from the interoperability and manageability of NDS* for NT.

Some of these benefits include:

Single sign-on from anywhere on the network.

Making the NT domain part of the NDS tree provides great network management benefits, while remaining transparent to the network user.

Users are not limited to network constraints exercised to cut cost and administration time as with NT servers.

Allows deployment of enterprise-wide applications (i.e. Exchange).

Allows both IntranetWare and NT network users to run NT domain-required applications.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installation Prerequisites


Installing NDS for NT


Integrating Domain Applications with NDS

Because the NT Server was designed with small workgroups in mind, Enterprise-ready applications (large-scale applications) run better using NDS for NT.

NDS for NT fully supports all NT domain-required applications.


Managing Exchange Users in NDS


Managing the IntranetWare/NT Network

A typical administration job is to create User objects for new network users and to assign appropriate rights.

NWAdmin gives you a great number of options for the kind of information you want NDS to keep for each user.

Novell's and Microsoft's network administrative tools interoperate using this product.


Moving NT Domains to the NDS Tree

The Domain Object Wizard is a network administrative tool that relocates NT domains on the NDS tree. This relocation, while transparent to the user, enables the NT domains to become manageable NDS Group objects, called Domain objects.

 The network administrators can manage the Domain objects using network administrative tools of Novell or Microsoft.

See How Network Users Benefit and How IntranetWare and NT Administrators Benefit.


Product Contents

NDS* for NT** provides you with tools you need to manage your mixed IntranetWare*/Windows NT** networks. NDS is the recognized industry-standard directory with an installed base of 22 million users.

Product Components

NDS for NT product components include:

NDS for NT Domain Object Wizard is a network administrative tool that relocates NT domains to the NDS tree. This relocation, while transparent to the user, enables the NT domains to become manageable NDS objects called Domain objects. The network administrators can manage NT domains using network administrative tools of Novell or Microsoft.

NWAdmin (32-bit NT version) is a graphical network administrative tool that allows single point of administration on your mixed IntranetWare/NT network. NWAdmin helps network administrators manage network resources.

Domain Object Snap-in is an administrative snap-in to NWAdmin that allows Domain objects to be viewed and managed in NDS. With the use of this tool, you can perform network administrative tasks, such as create a local group, create new global group, create new workstation, etc.

NDS Manager v1.24 is an administrative tool that allows network administrators to manage partitions, replicas, servers, repair operations, printing, and preferences.

Bundled Components

Bundled components include:

Novell Application Launcher (NAL) lets network administrators distribute network applications to users' workstations and manage those applications as objects in the NDS tree on the mixed IntranetWare/NT network. NAL gives network administrators powerful, unparalleled control over applications after they have been distributed to workstations. Network users will not need to worry about workstation configurations, drives, ports, command-line parameters, application source directories, or whether they have the latest upgrade.

NAL is installed separately from the NDS for NT product. The install utilities for NAL are located in the i386\GOODIES\NAL directory.

NWAdmin snap-ins include:

NAL Snap-in is an administrative snap-in to NWAdmin that lets you manage the NAL software.

Exchange Snap-in is an administrative snap-in to NWAdmin that lets you manage Microsoft Exchange Mail accounts in  NDS.

These NWAdmin snap-ins are installed with the NDS for NT product installation of the administration utilities.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Release Notes

[Release Note information will be added here.]

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Removing NDS for NT


Trademarks


What is NDS for NT?

NDS* for NT** enables interoperability between IntranetWare* and Windows NT** networks.

NDS for NT provides the following benefits:

Enables a network administrator to manage NT domains within NDS.

Eliminates the cost associated with managing NT domains.

Fully supports NT domain-required and Enterprise class applications.

NDS for NT relocates NT domains to the NDS tree. This relocation, while transparent to the user, enables NT domains to become manageable NDS Group objects, called Domain objects. With NDS for NT, network administrators can manage NT domains using network administrative tools of Novell or Microsoft.

See Understanding NDS for more information about the benefits of NDS

See Also

Product Contents

How IntranetWare and NT Administrators Benefit

How Network Users Benefit

Architecture of NDS for NT

Frequently Asked Questions

Release Notes

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.