Link to home
Start Free TrialLog in
Avatar of KenHuber
KenHuber

asked on

Group Policy Software Deployment problem

I am trying to create a software deployment package in Group Policy that is assigned to computers.  When I create the package, the deployment option "Install on logon" is disabled.  The option "Auto-install this application by file extension activation" is selected but also disabled.  This happens in any OU in AD.  Any ideas?
SOLUTION
Avatar of Krompton
Krompton
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
FYI: I took a quick look at the deployment options. I think they may be controled from options within the msi file itself. (Not 100% sure though)

Krompton
Those options are only available if you publish the package to users, not to computers.  Packages assigned to computers always install at startup, before the logon screen comes up.
Avatar of KenHuber
KenHuber

ASKER

Group Policy IS being applied to the computers.  There is an entry in the event log that says "changes to software installations settings were successfully applied".  No applications are being installed though.  Security is properly set on the shared folder that holds the installation files to allow access to domain computers.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This is how I had AD set up:

Software Distribution OU
          Specific Package(s) OU 1
                    Target Computers Group
          Specific Package(s) OU 2
                    Target Computers Group

I created the GPO for the Specific Package(s) OU and then put the group with the target computers as members into the OU.  I could have sworn that this worked for me before with a MS Office Project deployment but I must be mistaken.  It's been awhile...

So the problem is that there were no computers or users in the OU for the policy to be applied to.  Thanks for all of your responses - I had already tried most of those things but your answers helped keep me on the right track and verify that I was doing somethings right.

I am splitting the points between the 3 of you with the most going to Debsyl99 because of the effort and detail she put into her post.
Thanks again!