Active Directory was first released in beta form in 1997 when Microsoft came to the point of implementing a Lightweight Directory Access Protocol (LDAP)-based directory service to support its NOS environment.
The first version of the Lightweight Directory Access Protocol (LDAP) was released in 1993 as Request for Comments (RFC) 1487, but due to the absence of many features provided by X.500, it never really took off. It wasn’t until LDAPv2 was released in 1995 as RFC 1777 that LDAP started to gain popularity.
In 1997, the last major update to the LDAP specification, LDAPv3, was described in RFC 2251. It provided several new features and made LDAP robust enough and extensible enough to be suitable for most vendors to implement.
Hierarchical paths in Active Directory are known as distinguished names and can be used to uniquely reference an object. Distinguished names are defined in the LDAP standard as a means of referring to any object in the directory.If the domain had been called mydomain.mycorp.com, the distinguished name of the root would have looked like this:
dc stands for domain component and is used to specify domain or applicationpartition objects.
Active Directory supports using CN, L, O, OU, C, and DC. CN or OU is used in the majority of cases.
In Windows 2000 Server and Windows Server 2003, the directory service is named Active Directory.
In Windows Server 2008 and Windows Server 2008 R2 or later Windows Server verison, the directory service is named Active Directory Domain Services (AD DS).
In order to create custom attributes in active directory schema, go to active directory schema snap-in, right click on attributes container and select create attribute.
Tip – In order to open active directory schema snap-in you need to run command regsvr32 schmmgmt.dll from the Domain Controller. After that you can use MMC and add active directory schema as snap-in.
Then system will give a warning about the schema object creation and click OK to continue.
It will open up a form and this is where we need to define the details about custom attribute.
1) Common Name – This is the name of the object. It is only allowed to use letters, numbers and hyphen for the CN.
2) LDAP Display Name – When object is referring in script, program or command line utility it need to call using the LDAP Display name instead of the Common Name. when you define the CN, it will automatically create the LDAP Display name.
3) X500 Object ID – Each and every attribute in active directory schema has unique OID value. There is script develop by Microsoft to generate these unique OID valves. it also can directly run using following PowerShell command.
4) Syntax – It define the storage representation for the object. It is only allowed to use syntaxes defined by Microsoft. One attribute can only associate with one syntax. In below I listed few common used syntaxes in attributes.
Along with the syntax we also can define the minimum or maximum values. If it’s not defined it will take the default values.
In following demo, I like to add a new attribute called NI-Number and add it to the User Class.
As the next step, we need to add it to the user class. In order to do that go to classes container, double click on user class and click on attributes tab. In there by clicking the add button can browse and select the newly added attribute from the list.
Now when we open a user account we can see the new attribute and we can add the new data to it.
© 2022 Digcode.com