In many cases, it is far better to import the schema extensions with a LDIF file. You can use Microsoft's ldifde.exe or SunOne's ldapmodify.exe tool to apply the following LDIF file:
dn: CN=hr-Salary-Level,CN=Schema,CN=Configuration,DC=example,dc=com
changetype: add
adminDescription: Human Resources Salary Level
adminDisplayName: hr-Salary-Level
attributeID: 1.2.840.113556.1.4.7000.141
attributeSyntax: 2.5.5.9
isSingleValued: TRUE
lDAPDisplayName: hrSalaryLevel
oMSyntax: 2
objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=example,dc=com
objectClass: attributeSchema
searchFlags: 0
dn: CN=hr-Social-Security-Number,CN=Schema,CN=Configuration,DC=example,dc=com
changetype: add
adminDescription: Human Resources Social Security Number
adminDisplayName: hr-Social-Security-Number
attributeID: 1.2.840.113556.1.4.7000.142
attributeSyntax: 2.5.5.12
isSingleValued: FALSE
lDAPDisplayName: hrSocialSecurityNumber
oMSyntax: 64
objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=example,dc=com
objectClass: attributeSchema
searchFlags: 0
rangeLower: 0
rangeUpper: 128
dn:
changetype: modify
replace: schemaupdatenow
schemaupdatenow: 1
-
dn: CN=hr-Human-Resources,CN=Schema,CN=Configuration,DC=example,dc=com
changetype: add
adminDescription: Human Resources Auxilliary Class
adminDisplayName: hr-Human-Resources
governsID: 1.2.840.113556.1.4.7000.17
lDAPDisplayName: hrHumanResources
objectCategory: CN=Class-Schema,CN=Schema,CN=Configuration,DC=example,dc=com
objectClass: classSchema
objectClassCategory: 3
rDNAttID: cn
possSuperiors: organizationalUnit
possSuperiors: container
subClassOf: top
mayContain: hrSocialSecurityNumber
mayContain: hrSalaryLevel
dn:
changetype: modify
replace: schemaupdatenow
schemaupdatenow: 1
-
dn: CN=User,CN=Schema,CN=Configuration,DC=example,dc=com
changetype: modify
add: auxiliaryClass
auxiliaryClass: hrHumanResources
-
dn:
changetype: modify
replace: schemaupdatenow
schemaupdatenow: 1
-
