LDAP-UX Client Services 4.0 with Windows Server 2003 R2 Schema Support Release Notes

attributemap: group:nismapname=nisMapName msSFU30NisDomain
attributemap: group:userpassword=*NULL*
servicesearchdescriptor: group:?sub?(&(objectclass=group)(gidNumber=*))
attributemap: pam:uid=uid
attributemap: pam:uidnumber=uidNumber
attributemap: pam:userpassword=*NULL*
servicesearchdescriptor: pam:?sub?(&(objectclass=user)(uidNumber=*))
attributemap: rpc:cn=cn msSFU30Aliases
attributemap: rpc:nismapname=nisMapName msSFU30NisDomain
attributemap: rpc:oncrpcnumber=oncRpcNumber
servicesearchdescriptor: rpc:?sub?(objectclass=oncRpc)
attributemap: protocols:cn=cn msSFU30Aliases
attributemap: protocols:ipprotocolnumber=ipProtocolNumber
attributemap: protocols:nismapname=nisMapName msSFU30NisDomain
servicesearchdescriptor: protocols:?sub?(objectclass=ipProtocol)
attributemap: networks:cn=cn msSFU30Aliases
attributemap: networks:ipnetworknumber=ipNetworkNumber
attributemap: networks:nismapname=nisMapName msSFU30NisDomain
servicesearchdescriptor: networks:?sub?(objectclass=ipNetwork)
attributemap: hosts:cn=cn msSFU30Aliases
attributemap: hosts:iphostnumber=ipHostNumber
servicesearchdescriptor: hosts:?sub?(&(objectclass=computer)(ipHostNumber=*))
attributemap: services:cn=msSFU30Name msSFU30Aliases
attributemap: services:ipserviceport=ipServicePort
attributemap: services:ipserviceprotocol=ipServiceProtocol
attributemap: services:nismapname=nisMapName msSFU30NisDomain
servicesearchdescriptor: services:?sub?(objectclass=ipService)
4. cd /opt/ldapux/config
5. Run the LDAP-UX setup program, setup, as usual. When prompted to select the attribute map to
use with the directory server, select one of the following options, then complete the LDAP-UX setup.
• If you modify the default_profile_attr_ads_sfu2.ldif file, select option 1 “SFU2.0”.
• Otherwise, if you modify the default_profile_attr_ads_sfu3.ldif file, select option 2
“SFU3.0/3.5”.
Modifying the Output Files of the Migration Scripts
LDAP-UX Client Service provides ADS migration scripts to assist administrators to migrate the name
service data from UNIX source files to the Windows Active Directory Server. These migration scripts are
located under the /opt/ldapux/migrate/ads directory. The output of the ADS migration scripts is a
file in ldif format which is ready to be imported into the directory server.
To generate the ldif file with the LDAP entries that are compliant with the R2’s RFC2307 schema, you
must perform the following steps to ensure a successful mapping:
1. Ensure to perform all the steps documented in the “Modifying the Default Template File” section.
2. If you want to migrate /etc/passwd and /etc/group data, you can use the output ldif file of the
migrate_passwd_ads.pl and migrate_group_ads.pl migration scripts without any
modification.
Otherwise, for the output ldif files of the migrate_hosts_ads.pl, migrate_ protocol_ads.pl,
migrate_networks_ads.pl, migrate_rpc_ads.pl, and migrate_services_ads.pl scripts,
you must use the sed command to modify the output ldif files before importing them to the directory
server. For example, to migrate the /etc/hosts data to the Windows 2003 R2 Server, you must
perform the following steps:
1. Run the migration script, migrate_hosts_ads.pl, to get the output ldif file. For example,
the following commands migrate /etc/hosts data to generate the output.ldif file:
cd /opt/ldapux/migrate/ads
Workarounds 11