大网数据广告活动
域与目录服务

Impact of Schema Changes

· 52CE 我爱测

This topic describes how a schema extension impacts the Active Directory forest.

A schema extension impacts a domain forest controlled by Active Directory Domain Services in several ways:

  • Schema changes are global. There is a single schema for an entire forest. The schema is globally replicated: a copy of the schema exists on every DC in the forest. When you extend the schema, it is extended for the entire forest.

  • Schema object additions cannot be reversed. When a new class or attribute object is added to the schema, it cannot be removed. An existing attribute or class can be disabled, but not removed. For more information, see Disabling Existing Classes and Attributes. Disabling a class or attribute does not affect existing instances of the class or attribute, but prevents the creation of new instances. You cannot disable an attribute if it is included in any class that is not disabled.

  • OIDs must be unique. When an attribute or class is added to the schema, no attribute or class with the same OID can be added. This is true even if a class or attribute has been disabled. For this reason it is you must use valid OIDs. Do not synthesize an OID, and do not reuse an existing OID. For more information about obtaining a valid OID, see Obtaining a Root Object Identifier.

  • Some changes can be made after creation:

    • For a category 1 or category 2 class, you can add or remove values in the possSuperiors attribute. The possSuperiors values specify the object classes that can contain the class.
    • For a category 1 or category 2 class, you can add or remove values in the mayContain attribute. The mayContain values specify the optional attributes, but may be present in an instance of the class.
  • The lDAPDisplayName for a Category 2 class or attribute can be changed after it has been created. Typically, you should not change the lDAPDisplayName. However, there is one legitimate reason for changing the LDAP name and that is if you made a mistake in defining the attribute or class and must create a new one to replace the old one. You do not have to rename the relative distinguished name (RDN) of the attribute or class schema to do this. When the LDAP name is changed this enables you to work around a mistake rather than rebuilding your whole Windows 2000 infrastructure. For more information, see Disabling Existing Classes and Attributes.

    The lDAPDisplayName for predefined (category 1) classes or attributes cannot be changed. For more information about category 1 and 2 schema objects, see Restrictions on Schema Extension.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。