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

Registering the Object Creation Extension

· 52CE 我爱测

When an object creation extension DLL in Active Directory Domain Services is created, it must be registered with the Windows registry and Active Directory Domain Services to make COM and the Active Directory administrative MMC snap-ins aware of the extension.

When an object creation extension DLL in Active Directory Domain Services is created, it must be registered with the Windows registry and Active Directory Domain Services to make COM and the Active Directory administrative MMC snap-ins aware of the extension.

Registering in the Windows Registry

Like all COM servers, an object creation extension must be registered in the Windows registry. The extension is registered under the following key:

HKEY_CLASSES_ROOT
   CLSID
      <extension CLSID>
         InProcServer32
            (Default) = <extension path>
            ThreadingModel = Apartment

"<extension CLSID>" is the string representation of the CLSID as produced by the StringFromCLSID function. "<extension path>" contains the path and file name of the extension DLL. The ThreadingModel value for all object creation extensions must be "Apartment".

Registering with Active Directory Domain Services

Object creation extension registration is specific to one locale. If the object creation extension applies to all locales, it must be registered in the object class's displaySpecifier object in all of the locale subcontainers in the DisplaySpecifiers container. If the object creation extension is localized for a certain locale, register it in the displaySpecifier object in that locale's subcontainer. For more information about the DisplaySpecifiers container and locales, see Display Specifiers and DisplaySpecifiers Container.

There are two DisplaySpecifier attributes that an object creation extension can be registered under. These are creationWizard and createWizardExt.

The creationWizard attribute identifies primary object creation extensions to replace the existing or native object creation wizard in Active Directory administrative snap-ins. A primary creation extension provides the first set of pages and is hosted in the same way as native pages. This attribute is single-valued and requires the following format:

<CLSID>

The "<CLSID>" is the string representation of the COM object's CLSID as produced by the StringFromCLSID function.

The createWizardExt attribute identifies secondary object creation extensions. A secondary creation extension adds wizard pages to the native pages or primary extension. This attribute is multi-valued and requires the following format:

<order number>,<CLSID>

The "<order number>" is an unsigned number that represents the page's position in the wizard. When a creation wizard is displayed, the values are sorted using a comparison of each value's "<order number>". If more than one value has the same "<order number>", those pages are loaded in the order they are read from the Active Directory server. If possible, you should use a non-existing "<order number>" (that is, one that has not been used by other values in the property). There is no prescribed starting position, and gaps are allowed in the "<order number>" sequence.

The "<CLSID>" is the string representation of the COM object's CLSID as produced by the StringFromCLSID function.

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)

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

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