You can use this procedure to first register the dynamic-link library (DLL) that is required for the Active Directory Schema snap-in. You can then add the snap-in to Microsoft Management Console (MMC).

Membership in Domain Admins, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at https://go.microsoft.com/fwlink/?LinkId=83477.

To install the Active Directory Schema snap-in

  1. Open a command prompt, type the following command, and then press ENTER:

    regsvr32 schmmgmt.dll

  2. Click Start, click Run, type mmc, and then click OK.

  3. On the File menu, click Add/Remove Snap-in.

  4. Under Available snap-ins, click Active Directory Schema, click Add, and then click OK.

  5. To save this console, on the File menu, click Save.

  6. In the Save As dialog box, do one of the following:

    • To place the snap-in in the Administrative Tools folder, in File name, type a name for the snap-in, and then click Save.

    • To save the snap-in to a location other than the Administrative Tools folder, in Save in, navigate to a location for the snap-in. In File name, type a name for the snap-in, and then click Save.
Caution

Modifying the schema is an advanced operation that is best performed by experienced programmers and system administrators. For detailed information about modifying the schema, see Active Directory Schema (https://go.microsoft.com/fwlink/?LinkId=80809).

Additional considerations

  • To perform the Schmmgmt.dll registration portion of this procedure, you must be a member of the Domain Admins group in the domain or the Enterprise Admins group in the forest, or you must have been delegated the appropriate authority. Adding the Active Directory Schema snap-in to MMC requires only Domain Users group membership. However, making changes to the schema requires membership in the Schema Admins group.

  • The Windows Server 2008 Administration Tools Pack cannot be installed on computers running Windows XP Professional or Windows Server 2003.

Additional references

Table Of Contents