Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS Manual page 230

DSfW and Samba
Table C-1
Functionalities
Emulation
Management
Group Policies
Trusts
DNS and Secure Updates
Provisioning Users
230 OES 2 SP2: Domain Services for Windows Administration Guide
Samba
Emulates NT4 Domain Controller
or can be a member server of
Active Directory or NT domain.
Can be managed through
Windows NT4 Domain Server
Manager and the Windows NT4
Domain User Manager. But
cannot be managed from MMC.
No support for group policies that
are crucial to implement security
settings and enforce IT policies.
Supports NT style manual trusts
between two domains.
Does not come with DNS. Has to
be installed separately. The bind
DNS does not support secure
dynamic updates. So, the DNS
records have to be manually
managed by the Active Directory
administrators. Active Directory
administrator has to create
records for the DCs and for every
member server joined to the
domain.
Provisioning is performed by
including only Samba-specific
information in the user objects
created in the LDAP backend.
DSfW
Emulates Active Directory and
can also be a member server.
DSfW can be managed from
Microsoft MMC as well as
eDirectory web management
tools like iManager. So any
Windows member server/client
joined to the DSfW domain can
use the power of Active Directory
for creating shares, assigning
access rights, managing users,
trusts and group policies. In
DSfW the Samba-3 shares and
access rights can be managed
using iManager.
Supports Group Policies. For
more information, see Managing
Group Policy Settings.
Supports Active Directory level
trusts that includes automatic
Kerberos transitive trusts and
cross-forest trusts.
Comes packaged with Novell
Bind DNS that supports secure
dynamic updates. As it is
integrated into eDirectory, it
provides centralized Active
Directory administration and
enterprise-wide management of
DNS using iManager or Java*
Management Console. It
leverages the benefit of
eDirectory as Novell DNS
configuration information is
replicated just like any other data
in eDirectory.
Provisioning is performed by
extending the existing eDirectory
object class and including Active
Directory information in the user
objects.
As a result, DSfW has the same
information model as Active
Directory.