Opening Application Installs New Application

  • Article

You assign or publish an application with a Group Policy object, and a user installs the managed application. When the user opens the application, a new application installs. For example, opening Microsoft Word starts Microsoft FrontPage installation.

Possible Causes:

  • You set Auto-Install when configuring the application in the Software Installation snap-in.

  • You created an upgrade relationship between the existing (base) application and the new (upgrading) application.

  • The Download missing CLSID from Active Directory Group Policy is enabled.

  • The application that starts shares a class identifier (CLSID) with the published application.

Diagnostic Tests:

Check the file name extension priorities for the Group Policy object.

Check for an upgrade relationship to the base application.

Start the Group Policy snap-in and check for the Download missing CLSID from Active Directory Group Policy.

Check the CLSIDs for the two applications for duplicate CLSIDs.

note-iconNote

Checking Event Viewer for the application log does not provide any useful information for this problem because the new application installs correctly. It is not an installation error; rather, it is a case of correctly installing the wrong application.