HP CIFS Server Administrator Guide Version A.03.01.03 (5900-2006, October 2011)
Table Of Contents
- HP CIFS Server Administrator Guide Version A.03.01.03
- Contents
- About this document
- 1 Introduction to the HP CIFS Server
- 2 Installing and configuring HP CIFS Server
- HP CIFS Server requirements and limitations
- Step 1: Installing HP CIFS Server software
- Step 2: Running the configuration script
- Step 3: Modify the configuration
- Step 4: Starting HP CIFS Server
- Other Samba configuration issues
- 3 Managing HP-UX file access permissions from Windows NT/XP/2000/Vista/Windows 7
- Introduction
- UNIX file permissions and POSIX ACLs
- Using the Windows NT Explorer GUI to create ACLs
- Using the Windows Vista Explorer GUI to create ACLs
- POSIX ACLs and Windows 2000, Windows XP, Windows Vista, and Windows 7 clients
- HP CIFS Server Directory ACLs and Windows 2000, Windows XP, Windows Vista, and Windows 7 clients
- In conclusion
- 4 Windows style domains
- Introduction
- Configure HP CIFS Server as a PDC
- Configure HP CIFS Server as a BDC
- Domain member server
- Create the Machine Trust Accounts
- Configure domain users
- Join a Windows client to a Samba domain
- Roaming profiles
- Configuring user logon scripts
- Home drive mapping support
- Trust relationships
- 5 Windows 2003 and Windows 2008 domains
- 6 LDAP integration support
- Overview
- Network environments
- Summary of installing and configuring
- Installing and configuring your Directory Server
- Installing LDAP-UX Client Services on an HP CIFS Server
- Configuring the LDAP-UX Client Services
- Enabling Secure Sockets Layer (SSL)
- Extending the Samba subschema into your Directory Server
- Migrating your data to the Directory Server
- Configuring the HP CIFS Server
- Creating Samba users in directory
- Management tools
- 7 Winbind support
- 8 Kerberos support
- 9 HP CIFS deployment models
- Introduction
- Samba Domain Model
- Windows Domain Model
- Unified Domain Model
- 10 Securing HP CIFS Server
- 11 Configuring HA HP CIFS
- 12 HP-UX configuration for HP CIFS
- 13 Tool reference
- Glossary
- Index

Table 12 Migration scripts (continued)
DescriptionScript name
Migrates services in the /etc/services file.migrate_services.pl
3
Specifies a set of routines and configuration information all the perl scripts
use.
migrate_common.ph
1
Systems have been configured with the same host name, then the migration script migrate_host.pl will create multiple
entries in its resulting LDIF file with the same distinguished name for the host name for each of the IP addresses. Since
distinguished names need to be unique in an LDAP directory, you need to first manually merge the IP addresses with
one designated host record and delete the duplicated records in your LDIF file. A resulting merge might look as follows:
. . . .
dn: cn=machineA, ou=hosts, ou=unix, dc=org, dc=hp, dc=com
objectClass: top
objectClass: ipHost
ipHostNumber: 1.3.5.72
ipHostNumber: 1.3.8.4
ipHostNumber: 1.5.8.76
cn: hostA
cn: hostA.org.hp.com
. . . .
2
Netgroup
- The NIS optimization maps 'byuser' and 'byhost' are not utilized.
-Each triple is stored as a single string.
-Each triple must be enclosed by parentheses. For example, "(machine, user, domain)" is a valid triple while "machine,
user, domain" is not.
3
When migrating services data into the LDAP directory, You keep in mind that only multiple protocols can be associated
with one service name, but not multiple service ports.
Examples
Complete the following steps to migrate the /etc/passwd file to the LDIF file:
1. Set the environment variable, LDAP_BASEDN, to specify where you want to store your data.
For example, the following command sets the LDAP base DN to org.hp.com:
$ export LDAP_BASEDN="dc=org, dc=hp, dc=com"
2. Run the following script, migrate_passwd.pl, to migrate all data in the /etc/passwd
file to the /tmp/passwd.ldif file:
$ migrate_passwd.pl /etc/passwd /tmp/passwd.ldif
A part of the output is as follows:
dn: uid=johnl,ou=People,dc=org,dc=hp,dc=com
objectclass: top
objectclass: account
objectclass: posixAccount
objectclass: Account
loginShell: /usr/bin/ksh
uidNumber: 8662
gidNumber: 8200
homeDirectory: /home/johnl
gecos: John Louie, 48S-020, 447-1890
userPassword: {crypt}aOACGvt0T, 1foacctFlags: UX
pwdLastSet: 1063301239
Migrating your data from one backend to another
Use the syncsmbpasswd tool to synchronize Samba user accounts with all currently available
POSIX user accounts in the configured password database backend. If you set the passdb
Migrating your data to the Directory Server 91