Installed Application Is Unexpectedly Removed

You assign applications using Group Policy and a user installs the assigned applications. When the user logs on (in the case of user-assigned applications), or the user restarts the computer (in the case of computer-assigned applications), the applications are removed.

Possible Causes:

• You selected the Remove when policy does not apply check box, and the scope of management is changed — that is, the Group Policy object that contains the setting is no longer in effect.
• The software is managed by site, and the computer moved to a new site.

Diagnostic Tests:

Check to see if the Group Policy object with the managed application still applies to the user or computer.

Check to see if the computer is in a new site, and the Group Policy object with that site does not have the application.

Note

If a user or computer is moved from one organizational unit to another, or from one site to another, and if all aspects of the managed application do not match (for example, the package and the transform as well as the software distribution point), then you can remove and reinstall the application. This works even if the application appears to be managed by both Group Policy objects.

© 1985-2000 Microsoft Corporation. All rights reserved.