Novell Open Enterprise Server 2

Domain Services for Windows

Domain Services for Windows streamlines user and group management and simplifies infrastructure complexity in mixed environments. This innovative technology allows Microsoft Windows users to access OES services using native Windows and Active Directory protocols. By allowing eDirectory servers running on Open Enterprise Server to behave as if they were Active Directory servers, this technology enables companies with both directory services deployments to achieve better coexistence between the two platforms. Users can work in a pure Windows desktop environment and still take advantage of some Open Enterprise Server back-end services and technology, without the need for a Novell Client on the desktop.

Administration is simplified, also. Administrators can use either Novell iManager or Microsoft Management Console (MMC) to administer users and groups. Network administrators manage file systems using the the native tools of each server, as well as centrally administer Samba shares on OES Linux/DSFW servers using iManager. Administrators can use MMC to create one-way inter-domain trusts between DSFW domains and Active Directory domains.

When deployed in an environment that also supports NetWare Core Protocol (NCP), Domain Services for Windows supports cross-protocol locking. Whether customers decide to use only Windows clients, NCP clients, or a combination of both, access rights for files is enforced by the Novell Storage Services (NSS) file system.

Domain Services for Windows is not a meta-directory or a synchronization connector between eDirectory and Active Directory. It does not do desktop emulation. Domain Services for Windows can only run on SUSE Linux Enterprise deployments of Open Enterprise Server 2 SP1.

Deployment Scenarios

Install a new Domain Services for Windows domain in an existing tree. This scenario allows existing eDirectory users that become part of the new domain to run without the Novell Client, while others continue to run the Novell NCP client. This scenario is for customers that have existing Novell infrastructure and want to run with mixed client configurations.

Manage data using NSS as the file system of choice. This scenario is for customers that are familiar with NSS and its advantages over other file systems. In this scenario, customers manage their data using native NSS tools, but they also make their data available via Samba so that the workstations without the Novell Client can access that data.

Install a new DSFW domain in a new tree, emulating an AD domain. This scenario is for customers that have no existing Novell infrastructure, but want to experiment with ways to deploy Linux via Open Enterprise Server instead of costly Windows servers.

Manage data using POSIX file systems. This scenario is for customers that have no existing Novell infrastructure and are likely familiar with other Linux servers and have deployed some Samba servers, but now want the Active Directory support that DSFW offers instead of the NT-style protocols that a plain Samba 3 server supports.

For more information about how to install, configure, and use Domain Services for Windows, click here.

To speak with someone about how Domain Services for Windows will help streamline management of your mixed environment, click here.