Admin Tip #81: Schema Object Identifiers OIDs

Hits: Failed to execute CGI : Win32 Error Code = 3


Every object in Active Directory has required and optional attributes. The required attributes includes the Object Identifier ( OID ). The idea is analogous to internet addresses but instead of defining networks and subnets, the OIDs are used to define object classes and attributes. Unlike tcpip addresses there is no limitation to the length of the dotted notation. Like ip networks, there are multiple registrars to get your own OID. OIDs are owned by corporations, for example, Microsoft's OID is 1.3.6.1.4.1.311. To make some sense of the OID:

If you do a search for Microsoft, part of what you find will be: The top levels are

You can do searches (again analogous to internet domain names). Individuals as well as organizations can get their own registered OID. But getting back to Active Directory, the schema will contain definitions of all object classes including the OID. Expect vendors to start registering their own object classes as OIDs. If your organizations has internal development projects, you should get an OID for your organization (if you do not already have one - many corporations already do) and use it to manage whatever objects you need to define to AD schema. Like domain names, get a reqistered name, that OID, to avoid object clashes. Everything defined under your OID is unique and under your control. You can have as many sublevels as your development environment requires.

If you are not sick of OIDs by now, for more information that you ever wanted to know about OIDs, or if you want to search the OID dbs, see the OID Web page.