ei00004
asked on
Group Policy updates does not apply to some Windows 7 computers.
After making a change to an existing group policy that was previously applied to all computers in the domain, now will only update some computers with the change, not all.
ASKER
Sure, the GPO sets the task scheduler on the remote Windows 7 & 10 PCs, I changed the task scheduler "trigger" in the GPO from running every hour to just run whenever anyone logs into the computer. The policy is applied to all machines, but it only updated the trigger part on a few Windows 7 and 10 machines. I changed it 2 days ago.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the tip, I actually had the scheduler action set to "Create", not Update. I have now changed it to "Update" since I only what to update the trigger part. When you say "Item Level Targeting" are you referring to File path or object filtering?
Task Scheduler is a GPP (Group Policy Preferences).
When you create a preference there is a setting to target specific targeted groups without having to create multiple GPO with security filtering.
https://blogs.technet.microsoft.com/grouppolicy/2009/07/30/security-filtering-wmi-filtering-and-item-level-targeting-in-group-policy-preferences/
Since it seems that your are not familiar with this it most likely is not set.
Update and replace do somewhat the same thing. I have experienced updates not to work sometimes where replace did the job.
When you create a preference there is a setting to target specific targeted groups without having to create multiple GPO with security filtering.
https://blogs.technet.microsoft.com/grouppolicy/2009/07/30/security-filtering-wmi-filtering-and-item-level-targeting-in-group-policy-preferences/
Since it seems that your are not familiar with this it most likely is not set.
Update and replace do somewhat the same thing. I have experienced updates not to work sometimes where replace did the job.
ASKER
Thanks for the explanation. Luckily just changing the scheduler action to "Update" resolved my issue. Only the trigger part was changed to "Run on any user logon" on task scheduler on each user's computer. So now when anyone logs on, it will trigger the script to run.
Your question is vague and to help us the more detail you give the easier it will be for one of us to give you a recommend course of action.