Microsoft KB Archive/931034

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


PolicyMaker extensions do not appear in Group Policy Object Editor after you install PolicyMaker on a management computer

Article ID: 931034

Article Last Modified on 1/26/2007



APPLIES TO

  • PolicyMaker Standard Edition 2.0



SYMPTOMS

Extensions for Desktop Standard PolicyMaker Standard Edition do not appear in Group Policy Object Editor after you install PolicyMaker Standard Edition on a management computer.

CAUSE

This issue occurs because Microsoft XML 3.0 (MSXML3) is not registered earlier than other versions of MSXML that are on the computer. PolicyMaker Standard Edition depends on MSXML3.

WORKAROUND

To work around this issue, reregister each version of MSXML that is on the computer to make sure that MSXML3 is registered earlier than all other versions of MSXML. To do this, follow these steps:

  1. Download the Xmlinst.exe tool.

    Note To download the Xmlinst.exe tool, visit the following Microsoft Web site:
  2. At the command prompt, type xmlinst.exe -u to unregister all versions of MSXML.
  3. At the command prompt, change the directory to SystemDrive\Windows\System32. For example, type cd C:\Windows\System32.
  4. At the command prompt, type regsvr32 msxml3.dll to register MSXML3.
  5. At the command prompt, type regsvr32 msxml2.dll to register MSXML2 if MSXML2 is required.
  6. At the command prompt, type regsvr32 msxml.dll to register MSXML if MSXML is required.
  7. Restart Group Policy Object Editor.

Note If other applications require a version of MSXML other than MSXML3 to be registered first, these applications may work incorrectly.


Keywords: kbexpertiseinter kbtshoot kbprb KB931034