HP CIFS Server 3.0a Administrator's Guide version A.02.01

Updating HP CIFS Server A.01 to A.02
Behavior Differences Between HP CIFS Server A.01.* and A.02.*
Chapter 10 181
that must be specified for this purpose. A.02.* does not fall back to
use the add user script option in the absence of an add machine
script option.
• The join domain command
In A.02.*, the "smbpasswd -j domain_name -r PDC_hostname -U
administrator%passwd"command used to join a domain has been
replaced by net commands.
The Windows NT domain or Windows 2000 mixed mode domain uses
the "net rpc join -j domain_name -U Administrator%passwd”
command, or the "net rpc join -U Administrator%passwd"
command by specifying the domain name with the workgroup
parameter in the smb.conf file.
The Windows 2000 ADS domain, under Kerberos configuration uses
the "net ads join -j domain_name -U Administrator%passwd"
command, or the "net ads join -U Adminitrator%passwd”
command by specifying the domain name with the workgroup
parameter in the smb.conf file.
• The LDAP schema has been enhanced. If you choose to use the LDAP
backend, you must choose between continuing with your current
schema or moving to an updated schema. Set the passwd backend
parameter to ldapsam://ldapserver in the smb.conf file if you
choose to use the updated schema. Set the passwd backend
parameter to ldapsam_compat://ldapserver if you want to use the
current schema.
• A.02.* versions cannot join A.01.* domains. Some mixing of A.01.*
and A.02.* versions is permitted because A.01.* version servers can
be member servers to an A.02.* PDC, but A.02.* cannot serve as a
BDC or member server to an A.01.* PDC. A.02.* version servers also
cannot be member serves to an Advance Server for UNIX (ASU)
PDC.
• When the winbind daemon, winbindd, is not running, a domain
user must have a local account for access to shares of an HP CIFS
Server acting as a Windows ADS or NT4 domain member. Without
the local account, HP CIFS Server denies logon. If you add the add
user script option to the smb.conf file, the local account of a logon
user is automatically created in the server. When the winbind
daemon, winbindd, is running, a domain user does not need a local
acccount. Winbindd can map Windows SID to Unix UID/GID.