LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

NOTE: Keep the following considerations in mind when using
the -O option:
• The ldapugdel tool does not support attribute mappings.
For example, if the uidNumber attribute has been mapped
to the employeeNumber attribute, ldapugdel will
attempt to remove uidNumber attribute and not
employeeNumber.
• Because the uid, cn and description attributes are
commonly used by other user or group object classes,
ldapugdel does not attempt to remove uid and
description attributes for a user entry or cn and
description attributes for a group entry, unless failure
to remove those attributes can cause an object class
violation (because the remaining object classes for that
entry do not define them as their attributes). Use of the -O
-x option forces ldapugdel to remove those attributes if
allowed by the remaining object classes for that entry.
• Because the userPassword attribute is often used by
other user-related object classes, ldapugdel does not
attempt to remove the userPassword attribute when
removing user entries. Use of the -O -y -t passwd
options forces ldapugdel to remove this attribute if
allowed by the remaining object classes in that entry.
• The ldapugdel tool attempts to remove the
posixAccount and posixGroup object classes only if
they are present. In some cases, when a user or group entry
is built using an abstract class, the posixAccount and
posixGroup object classes might not be present in the
entry.
• If ldapugdel determines that the entry being deleted is
stored on a Windows ADS directory server, ldapugdel
does not remove the homeDirectory attribute. The
Window user entry contains the User object class and the
homeDirecotroy attribute is part of the User object class.
• The Microsoft Services for UNIX (SFU) schema does not
use RFC 2307 standard attributes. Also ldapugdel does
not support attribute mapping as defined by the LDAP-UX
configuration profile when the tool is used to access a
Windows ADS with msSFU 2.0 or msSFU3.0/3.5 schema
installed. When the -O option is specified and ldapugdel
determines that it is connected to a Windows ADS with
these schema installed, ldapugdel does not remove the
mapped POSIX object class and attributes (msSFU30xxx
or msSFU20xxx) for the specified user or group entry.
• The -O option functions properly with Windows ADS 2003
R2, because it uses standard RFC 2307 attributes, with the
exception of the homeDirectory attribute.
Specific Return Codes for ldapugdel
The ldapugdel tool returns a list of return codes shown in Table C-9.
Table C-9 Return Codes for ldapugdel
MessageReturn Codes
The specified attributes are invalid POSIX attributes.
DEL_COMMANDLINE_ERR
216 Command, Tool, Schema Extension Utility, and Migration Script Reference