Nt4-Specific Limitations - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

NT4-Specific Limitations

• Active Directory uses the attribute
physical or postal address. Directory Server uses the RFC2798 inetOrgPerson
attribute
streetAddress
Directory also has the
streetAddress
Windows Sync maps
Server, and therefore, precludes the use of the
Directory.
NT4-Specific Limitations
The NT4 LDAP Service attempts to reflect the NT4 NTLM user database (as
accessed via the Net API) in LDAP. In general, this works well, but there are some
fundamental incompatibilities between LDAP schema and the underlying data
store. These incompatibilities are listed below:
• The schema supported by the NTLM database is severely limited compared
to Active Directory. There is little support for information beyond username
and full name. The missing attributes therefore cannot be synchronized.
• There is no support for the incremental Dirsync found in Active Directory.
What this means is that every time the Directory Server performs a
synchronization pass, it will pull the complete set of all entries from NT4. This
has implications for the consistency of data because if a modification is made
to an entry on the Directory Server side and the same entry is read from NT4
in a synchronization operation before the change has been propagated
outbound, then the change will be undone.
• There is no support for tombstone entries in NT4. What this means is that
entries deleted from NT4 will not be automatically deleted from the Directory
Server side. It will be necessary to delete those entries manually.
• NT4 has no
requires
person schema with NT4, when new user entries are created in the sync
process, they are given a
name. This can be changed later by the admistrator to the correct value. This
issue only applies to new entries created in Directory Server by a sync
operation. If the associated Directory Server entry for an NT4 user account
already exists, its
568 Red Hat Directory Server Administrator's Guide • May 2005
for this purpose. However, as defined in RFC2256,
street
is an alias for
street
but a separate attribute that can hold an independent value.
streetAddress
attribute. However, the
surname
have a value. In order to allow the use of the standard
surname
surname
attribute is left unchanged.
surname
streetAddress
. To compound the confusion, Active
street
attribute, but it is not an alias for
in Windows to
street
inetOrgPerson
attribute value that is equal to the NT user
for a user or group's
in Directory
street
attribute in Active
object class