Leveraging An Existing Edirectory Setup; Interoperability Between Active Directory And Edirectory; Section 3.3, "Leveraging An Existing Edirectory Setup; Section 3.4, "Interoperability Between Active Directory And Edirectory - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS Manual

Accessing applications without Novell Client
Figure 3-3
Before After
MMC MMC
Server Server
w w
iManager iManager
Desktop Desktop
Novell
Client
Server Server
IMPORTANT: Do not install the Novell Client for Windows on a workstation for which you plan
TM
to provide native Windows access to DSfW servers. Novell Client access and native Windows
access to DSfW servers do not work well together on the same workstation. But if you already have
Novell Client installed on your workstation, we recommend that you follow the instructions in
Joining a Workstation that Has Novell Client Installed

3.3 Leveraging an Existing eDirectory Setup

If you already have an eDirectory setup but want to install DSfW in your environment, it is
recommended you utilise the existing eDirectory setup and install DSfW in a container in the
existing eDirectory tree. This way you can utilise all the user information in the eDirectory
container. This kind of setup is known as a name-mapped setup.
For more details on name-mapped setup, see Section 5.4.2, "Installation Prerequisites for a Name-
Mapped Setup," on page 35 and Section 4.2, "Deploying DSfW in a Name-Mapped Setup," on
page 27
3.4 Interoperability Between Active Directory
and eDirectory
Trust relationships are a key to managing Domain Services for Windows (DSfW). To facilitate
communication between Windows and Linux environments you can create a trust to access
resources from another domain. When a domain is installed, a trust is automatically established with
its parent domain.
To assist you in doing this, DSfW supports installing into a new eDirectory tree, an existing
eDirectory tree, or an existing forest, creating multiple DSfW domains, and setting up multiple
DSfW domain controllers within the same domain.
Figure 3-4 illustrates a typical deployment scenario in a mixed Novell/Microsoft environment.
Use-Cases 23