Computer-Assigned Applications Do Not Install

  • Article

You assign an application to a computer managed by a Group Policy object, and a user restarts the computer. When he or she logs on to the computer, the computer's assigned application does not install.

Possible Causes:

  • Computer (machine) Group Policy is not applied — that is, the computer has not been restarted since the application was assigned to the computer.

  • The Group Policy object does not apply to the computer. For example, the computer is in a different organizational unit, or the computer is filtered out of the Group Policy object by a security group.

  • Group Policy did not run.

  • The Appmgmt extension did not run.

  • The computer is not able to access Active Directory.

  • The computer is not able to access the software distribution point.

Diagnostic Tests:

Restart the computer and open the Group Policy object with the Group Policy snap-in to make sure the Group Policy object manages the computer.

Run the Gpresult.exe tool to see if Group Policy took effect.

Check to see if the Appmgmt extension ran, by running the Addiag.exe tool.

To check that the computer can access Active Directory

  1. Ping the domain controller by IP address to test base-level connectivity.

  2. Ping the domain controller by server name to test DNS.

  3. Use the net view command to view the \\ ServerName \Sysvol share to test that the computer can read the Sysvol.

To check that the computer can access the software distribution point

  1. Ping the software distribution point by IP address to test base level connectivity.

  2. Ping the software distribution point by server name to test DNS.

  3. Use the net view command to view the \\ ServerName \ AppShare share to test that the computer can read the software distribution point.

note-iconNote

There are cases where installation of an assigned application can cause the computer to stop responding during restart. If the application package requires user intervention, but the Windows Installer cannot display the necessary user interface, the Windows Installer is effectively blocked. If a computer with an assigned application continually stops during startup for no apparent reason, remove the assigned application. Then, either reassign the application, allowing the user access to the interface, or deploy the application in such a way that user input is not needed. It is always recommended that you test installations on another computer before deployment.