HP CIFS Server Administrator's Guide Version A.03.01.01 (5900-1282, May 2011)

group: files ldap
hosts: dns [NOTFOUND=return] files ldap
networks: files ldap
protocols: files ldap
rpc: files ldap
publickey: files
netgroup: files ldap
automount: files
aliases: files
services: files ldap
Windows Domain Model
You can use the Windows Domain Model in environments with the following characteristics:
• Deploy Windows NT4, Windows 200x Mixed Mode, or Windows 200x ADS servers (with
NetBIOS enabled).
• Support for any number of HP CIFS servers that provide file and print services for corresponding
numbers of users. It requires HP-UX LDAP Integration Client software for ADS domain member
servers.
• Access to an LDAP-UX Netscape Directory Server as the backend storage for larger deployments
to maintain winbind ID maps across multiple HP CIFS Servers.
The Windows Domain Model provides the following benefits:
• Support for Windows domain member single sign on, network logon, and Windows account
management system.
• Support for easy user management across multiple HP CIFS servers by using winbind.
• Easy expansion capability.
Figure 9-6 shows the Windows Domain Deployment Model as follows:
Figure 28 Windows Domain
Windows NT
Windows NT
or Windows
ADS/PDC
HP CIFS
Member
Server
LDAP
ldap-ux client
winbind daemon
libnss_winbind
idmap.tdb
idmap backend
windows
users
BDC
windows
users
idmaps
winbind
winbind
= ldap
In the Windows Domain Model, HP CIFS Server can join to a Windows domain as a member
server with Windows NT or Windows 200x domain controllers. HP CIFS Server supports winbind
to provide UID and GID mappings for Windows users. For a larger deployment environment, you
can use the LDAP directory to maintain unique ID maps across multiple HP CIFS Servers.
122 HP CIFS Deployment Models