HP-UX Directory Server 8.1 administrator guide

Table 9-2 User schema mapped between Directory Server and Active Directory
Active DirectoryDirectory Server
namecn
1
sAMAccountNamentUserDomainId
homeDirectoryntUserHomeDir
scriptPathntUserScriptPath
lastLogonntUserLastLogon
lastLogoffntUserLastLogoff
accountExpiresntUserAcctExpires
codePagentUserCodePage
logonHoursntUserLogonHours
maxStoragentUserMaxStorage
profilePathntUserProfile
userParametersntUserParms
userWorkstationsntUserWorkstations
1
The cn is treated differently than other synchronized attributes. It is mapped directly (cn to cn) when synchronizing
from Directory Server to Active Directory. When synchronizing from Active Directory to Directory Server, however,
cn is mapped from the name attribute on Windows to the cn attribute in Directory Server.
Table 9-3 User schema that are the same in Directory Server and Windows servers
physicalDeliveryOfficeNamecn
1
postOfficeBoxdescription
postalAddressdestinationIndicator
postalCodefacsimileTelephoneNumber
registeredAddressgivenName
snhomePhone
sthomePostalAddress
streetinitials
telephoneNumberl
teletexTerminalIdentifiermail
telexNumbermobile
titleo
userCertificateou
x121Addresspager
1
The cn is treated differently than other synchronized attributes. It is mapped directly (cn to cn) when synchronizing
from Directory Server to Active Directory. When synchronizing from Active Directory to Directory Server, however,
cn is mapped from the name attribute on Windows to the cn attribute in Directory Server.
9.3.2 User schema differences between Directory Server and Active Directory
Although Active Directory supports the same basic X.500 object classes as Directory Server, there
are a few incompatibilities of which administrators should be aware.
9.3 Synchronizing users 409