I am attempting to set up my first group policy to install an msi package. I linked the group policy in a sub folder that contained no users or computers. I set a new security group containing the computers I wanted this installation to happen on. I set that security group in the Security Filtering in the Scope tab, and also added that security group to the Delegation tab.
This policy would not go into effect on the computers in the security group until I linked the policy to a folder above where the computers were AND enforced it. If the policy wasn't enforced, rsop.msc would show the policy under software settings>software installation, but the actual package would not be listed. Only when I turned on enforced did the package actually show up. I would like this to work without having to put the policy in a higher folder. So my main question is what could be causing this? There are other policies in place that were made by someone else, could they be causing the trouble? And if so, any guesses to where and what settings policies could cause this?
Also, I only had 2 computers in this security group, both were in different folders in active directory. When I got the policy to apply after enforcing it, the software installed immediately on one machine, but the installation never began on the other. The computer where the installation never started has the package listed in rsop.msc but after 30+ minutes, then install never began, under the users login nor the administrator login. Any guesses/suggestions on what could be the issue here? The policy itself is set for both computer and user to do windows installs with elevated privileges, but the one that the install did work on is one of our IT computers and has more privileges from other policies than other computers we want to install this software on.