dcirona86
asked on
GPO software install
Hi,
I have a server 2008 R2 environment with windows 7 laptops for my staff. I need to push out IE 9 via GPO as these laptops are not configured for WSUS. These laptops are configured to connect to the wireless once the user has entered their credentials so I have the issue where I want to push out this software package linking it to the computer OU where the computer objects reside however this means that the install happens upon system boot up which creates an issue for me where the GPO won't run due to lack of connectivity to the network until the user logs in.
If I set this GPO under the User configuration then if staff log onto another machine then it will try to install on any other machine that they log onto.
Is there a way around this so it installs on a specific OU containing the laptops?
By linking the GPO to the Computer OU it doesn't seem to run
I have a server 2008 R2 environment with windows 7 laptops for my staff. I need to push out IE 9 via GPO as these laptops are not configured for WSUS. These laptops are configured to connect to the wireless once the user has entered their credentials so I have the issue where I want to push out this software package linking it to the computer OU where the computer objects reside however this means that the install happens upon system boot up which creates an issue for me where the GPO won't run due to lack of connectivity to the network until the user logs in.
If I set this GPO under the User configuration then if staff log onto another machine then it will try to install on any other machine that they log onto.
Is there a way around this so it installs on a specific OU containing the laptops?
By linking the GPO to the Computer OU it doesn't seem to run
ASKER
The wireless network is configured to use the user account login credentials to connect to the wireless which is one of my main issues with this
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> lack of connectivity to the network until the user logs in.
What should that mean? Why would the user logon have anything to do with connectivity? If you have very fast booting systems, then set the policy "always wait for the network" to make sure the network is initialized before logon and your policies will run before logon. http://technet.microsoft.com/en-us/magazine/gg486839.aspx