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
Main Topics
Browse All TopicsI 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?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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.
I'd follow the troubleshooting steps from the "If Application Management Policy Does Not Work" heading in Microsoft KB article 250842. One of the logs should provide hints about the cause of the problem.
http://support.microsoft.c
Hi
A good way to troubleshoot group policy application is using this tool:
Enterprise Management with the Group Policy Management Console
http://www.microsoft.com/w
Download - Group Policy Management Console with Service Pack 1
http://www.microsoft.com/d
This is native on a Windows 2003 server but can be run using an Admin logon on an XP SP1 workstation joined to a Windows 2000 domain, with .Net framework installed on the XP client (anything else required will be prompted for). The tool should give you some very useful event logs if anything is wrong with the policy and setup thereof.
In terms of the policy itself you need to ensure that:
1) The "Domain computers" group or a security group that the relevant pc's are members of have "read and apply" group policy permissions on the GPO.
2) Domain computers have read and execute permissions on the network share
3) The share itself isn't specified by a mapped drive in the GPO - it needs to be \\servername\sharename
4) XP Clients have a clever feature called Fast Logon Optimization that can prevent some aspects of group policy being applied immediately - this needs a couple of reboots or a policy change to fix
Description of the Windows XP Professional Fast Logon Optimization feature
http://support.microsoft.c
4) The policy itself needs to be assigned to computers, not published in order to run on the client PC at startup - as Shift-3 has already said.
If the above doesn't help then it could be a problem with compatibility with the msi package and GP application. What's the package you're trying to deploy?
Hope that helps
Deb :))
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!
Business Accounts
Answer for Membership
by: KromptonPosted on 2006-09-15 at 11:18:28ID: 17531449
I have deploryed a few apps this way. I did not try to change this setting but my apps did deploy during computer startup.
yValue) om/default .aspx?scid =kb;en- us; 840669 for more info
I had to add a registry setting to the Winlogon Key (Value = GpNetworkStartTimeoutPolic
See http://support.microsoft.c
But after the registry change software deployed fine.
Cheers,
Krompton