HP CIFS Server 3.0b Release Note version A.02.01.01

HP CIFS Server Release Note
HP CIFS Deployment Models
Chapter 1 11
For more information on how to set up and configure the Samba domain
model, refer to Chapter 11, “HP CIFS Deployment Model” in the HP
CIFS Server A.02.01 Administrator’s Guide.
Windows Domain Model
The Windows deployment domain model offers the following
characteristics and benefits:
• Consists of the following two domain environments:
— A domain with the Windows NT as a PDC, one or more Windows
NT servers acting as BDCs, and multiple Windows NT or HP
CIFS member servers.
— A domain with the Windows 2000 as a DC, and multiple
Windows or HP CIFS member servers.
• Winbind is used to provide UID and GID generation and mappings
for Windows users. For large deployment environments, you can also
centralize management of ID maps in an LDAP directory across
multiple HP CIFS servers instead of the local idmap file.
• The NTLMv2 security is used for NT Domain membership and
Kerberos security is used for Windows 2000 membership.
For more information on how to set up and configure the Windows
domain model, refer to Chapter 11, “HP CIFS Deployment Model” in the
HP CIFS Server A.02.01 Administrator’s Guide.
Unified Domain Model
The Unified deployment domain model offers the following
characteristics and benefits:
• Uses the Windows ADS and the Services for Unix (SFU) to
consolidate windows and UNIX user accounts on the directory. All
user management is unified on the Windows ADS, winbind is not
required
• Supports any number of HP CIFS servers which provide file and
print services for number of users. This requires LDAP-UX
Integration software on an HP CIFS member server.
• Supports Windows domain member single sign on, network logon,
and Windows and UNIX account management system.