Published software not displayed in Add/Remove Programs

Posted on

A server stack is the collection of software that forms the operational infrastructure on a given machine. In a computing context, a stack is an ordered pile. A server stack is one type of solution stack — an ordered selection of software that makes it possible to complete a particular task. Like in this post about Published software not displayed in Add/Remove Programs was one problem in server stack that need for a solution. Below are some tips in manage your windows server when you find problem about windows, installation, group-policy, deployment, msi.

I just followed How to use Group Policy to remotely install software in Windows Server 2003 to try publishing a software (MSI file). I could follow all the steps, but the supposedly successfully published software does not appear on client/user machine’s Add/Remove Programs.

Could some help figure why this may not be working.


On reading this question on Experts-Exchange, tried gpresults. Output extract follows:


The following GPOs were not applied because they were filtered out
        Filtering:  Denied (Security)

    Default Domain Policy
        Filtering:  Denied (Security)

The GPResult output shows that the target computer account (i.e. the COMPUTERNAME$ Active Directory account for the machine you’re using) doesn’t have permission to the software deployment GPO you created.

The target account(s) (i.e. computer accounts, in your case) need both Read and Apply Group Policy permissions, in the Security settings for the GPO you’ve created. (At the bottom of the Security tab in the Group Policy Management console)

Note also that if the installation isn’t silent (i.e. displays UI) and you’ve not created a silent installation MST for it, it’ll hang the computer when it boots (while waiting for invisible user input), for 15/30 minutes.

Note that as of MS16-072, you need computer accounts to be able to read (only Read, not apply) group policy in order to be able to apply User policy.

Have you tried forcing the policy on the OU? You may have another policy that is blocking the application of the policy. I’m assuming that the XADistribution policy is the one containing your package? Once done you can force replication (assuming more than one domain controller) and then force a group policy update with the gpupdate /force command. You can then re-run gpresult to see if the policy is being applied. With that in place I believe a reboot would be necessary to initiate the package installation.

Group Polices have security permissions. There is permission for “apply group policy” that you have to check for users/groups that you want the Group Policy to apply to. You get to the security settings throe the property button on the Group Policy tab.

To publish a software put it under the “user”-tree.

To force a software to be installed put it under “computer”-tree.

May you choose the wrong path when you are clicking the GPO together.

Leave a Reply

Your email address will not be published.