When you try to install an ActiveX control by using Active Directory in Windows XP or in Windows Server 2003, the operation is not successful

Article translations Article translations
Article ID: 894571 - View products that this article applies to.
Expand all | Collapse all


Consider the following scenario. You use the methods that are described in the following Microsoft Knowledge Base articles to install an ActiveX control on a Microsoft Windows XP-based or Microsoft Windows Server 2003-based client computer:
241163 How to publish ActiveX controls in Windows 2000 using IntelliMirror
280579 How to install ActiveX controls in Internet Explorer using the Active Directory
However, the operation to install the ActiveX control is not successful.

  • The methods that are described in these articles are intended for Microsoft Windows 2000-based systems.
  • These methods involve the use of the Active Directory directory service.


This issue occurs when the following conditions are true:
  • You access a Web page in Microsoft Internet Explorer that requires that you install an ActiveX control on the client computer.
  • The client computer is affected by the deployment policy that is described in the Knowledge Base articles that are mentioned in the "Symptoms" section.
  • You deploy the ActiveX control to Active Directory by using an administrative tool in the Active Directory Users and Computers snap-in.
By default in Windows 2000, the COM component information is deployed together with the Microsoft Windows Installer package (.msi file) into Active Directory. However, in Windows XP and in Windows Server 2003, you have the option to include or not to include COM component information in the ActiveX deployment. To include COM component information, use the Advanced Publish feature.

Note Windows XP and Windows Server 2003 were designed with the Advanced Publish feature because the inclusion of COM component information in the ActiveX deployment requires significantly more hard-disk space.


To resolve this problem by using the Advanced Publish feature, follow these steps in Windows Server 2003:
  1. "Use the Active Directory Users and Computers snap-in to open the Group Policy Object Editor. To do this, follow these steps:
    1. Click Start, click Run, type dsa.msc, and then click OK.
    2. In the console tree, right-click your domain, and then click Properties.
    3. Click the Group Policy tab, select the group policy object that you want, and then click Edit.
  2. Expand Computer Configuration, expand Software Settings, right-click the Software installation, point to New, and then click Package.
  3. Select a .msi package that you want to deploy, and then click Open.
  4. Click to select Advanced in the Deploy Software dialog box, and then click OK.
  5. Click the Deployment tab, and then click Advanced.
  6. Click to select the Include OLE class and product information check box, and then click OK.
The COMClassID information will now be deployed into Active Directory.


To verify that you are experiencing the problem that is described in the "Symptoms" section, use the Lightweight Directory Access Protocol (LDAP) management tool, Ldp.exe, to open Active Directory. Then, expand the Active Directory nodes in the following order:
CN={Policy GUID}
CN=Class Store
CN={Package GUID}
In the left pane, you will see the COMClassID value. If the COMClassID value for an .msi file that contains an ActiveX control is all zeros, you are experiencing this problem.


Article ID: 894571 - Last Review: April 22, 2008 - Revision: 4.2
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Tablet PC Edition
kbprb kbactivedirectory kbactivex KB894571

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com