Reference record for OID 1.2.840.113556.1.8000

parent

1.2.840.113556.1 (1)

node code

8000

node name

8000

dot oid

1.2.840.113556.1.8000

asn1 oid

{iso(1) member-body(2) us(840) microsoft(113556) 1(1) 8000(8000)}

iri oid

/iso/member-body/us/microsoft/1/8000

iri by oid_info

/ISO/Member-Body/US/113556/1/8000

Description by oid_info

Companies
View at oid-info.com

Information by oid_info

Information received from Microsoft:
How to generate OIDs
To generate an OID root for your organization, please download and run this VBScript.

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
You can use auto generated link IDs. Autogeneration of LinkIDs 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. A back link for this forward link is created by setting the linkID to the attributeId or ldapDisplayName of the forward link. The schema cache must be reloaded after creating the forward link and before creating the back link. Otherwise, the forward link attributeId or ldapDisplayName will not be found when the back link is created. The schema cache is reloaded on demand, a few minutes after a schema change is made, or when the DC is rebooted. Reloading the schema cache on demand is described in Help docs. Create all forward links, reload schema cache and then create all back links.

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
Exception: You will need to request link IDs from Microsoft if your Active Directory environment contains Domain Controllers running on Windows 2000 Server or prior releases.

Requesting link IDs for Active Directory environments that contain Domain Controllers running on Windows 2000 Server or prior releases:
Your registration request has been received and will be processed within 15 business days. Registration is free of charge.

It is important that you provide all the required registration information completely in order for your request to be processed in a timely fashion. The following recapitulates the registration information that you should have already submitted:
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>

Here are some other useful links regarding AD schema:
- Active Directory Schema
- Schema Technical Reference
- Step-by-Step Guide to Using Active Directory Schema and Display Specifiers

First Registration Authority

Microsoft

Current Registration Authority (recovered by parent 1.2.840.113556)

Koos Rommelse

Children (7)

Brothers (4)