|
|
Information:
|
Information received from Microsoft:
How to generate OIDs
It is strongly recommended that you prefix your custom schema attributes and classes with the name of your organization. For example: if your prefix is "Microsoft", you should name schema elements like "microsoft-Employee-ShoeSize". For more information on the prefix, view the Schema Naming Rules in the server Application Specification.
You can create subsequent OIDs for new schema classes and attributes by appending a .X to the OID where X may be any number that you choose. A common schema extension scheme generally uses the following structure:
If your assigned OID was: 1.2.840.113556.1.8000.999999
then classes could be under: 1.2.840.113556.1.8000.999999.1
which makes the first class OID: 1.2.840.113556.1.8000.999999.1.1
the second class OID: 1.2.840.113556.1.8000.999999.1.2
etc.
Using this example, attributes could be under: 1.2.840.113556.1.8000.999999.2
which makes the first attribute OID: 1.2.840.113556.1.8000.999999.2.1
the second attribute OID: 1.2.840.113556.1.8000.999999.2.2
etc.
How to generate link IDs
Autogeneration of link IDs is a new feature in Windows Server 2003. The system will automatically generate a link ID for a new linked attribute when the linkID attribute is set to 1.2.840.113556.1.2.50.
Example:
ldapDisplayName: myForwardLinkAttr
OID: 1.2.840.113556.6.1234
LinkID: 1.2.840.113556.1.2.50
ldapDisplayName: myBackLinkAttr
OID: 1.2.840.113556.6.1235
LinkID: 1.2.840.113556.6.1234 or myForwardLinkAttr
It is important that you provide all the required registration information completely in order for your request to be processed in a timely fashion:
Company name:
Contact name:
E-mail address:
Phone number: <Please provide country and area codes if you are outside the U.S.>
Prefix registered: <If applicable>
OID registered: <If applicable>
|
|
