Group Policy Task Schedule deployed to User Configuration not working, works when in Computer Configuration?
User policies must be applied to an OU with user accounts in it, not computer accounts. GPO's cannot be applied to the default users OU however. A new OU must be created and those users moved to it.
user80130
Updated on September 18, 2022Comments
-
user80130 over 1 year
I added a Scheduled Task on my Windows 2008 R2 Domain Controller in the Group Policy Manager:
MyDomain Policy
User Configuration
Preferences
Control Panel Settings
Scheduled Tasks
Basic Task, like starting notepad, when user unlocks his workstation.
This should show up in the client workstation's task scheduler, but it dosn't. No errors or anything like that.
If I use the "Computer Configuration" instead of "User Configuration" the task appears, and I'm able to run the task.
I've tried the
gpupdate /force
followed bygpresult
and checked the report, but it dosn't contain the GPO Scheduled Tasks I created? (again, does show up when using "Computer Configuration".)The issue is that I have to run the application in the current users context, and only on a specific Employee OU, and thereby limit this task only to Employee Workstations and not apply the application when the same employee log on to internal servers and such.
Primary domain dontroller is a Windows 2008 R2, workstations Windows 7 Enterprise.
What am I doing wrong ?
-
user80130 almost 13 yearsHi orange aruelius, thanks for your feedback - our GPO's are quite simple, and we don't have such a rule, but I will look into the Group Policy Loopback Processing, and check if this will do the trick for me.