ITHand Posted May 31, 2018 Posted May 31, 2018 Hello everyone, I want to push a scheduled task to turn off the computers in Windows 10 by GPO, but I can not. Despite all my research and my various tests from many posts found here or everywhere on the web, no way to achieve it. Here is the configuration that seems most prevalent on the web that does not work: I did the testing with an admin account in the AD and the system account with the option "Run only when user is logged on" which would seem to be the option to previle and the option "Run whether user is logged" on or not ". This configuration works when I test it locally on a machine and the GPO is deployed, because several other parameters are included in it and they are applied. I do a gpupdate /force after each replication to make sure that everything is on the computer ... AD is on Windows Server 2012 and computer is on Windows 10 1709 EDU. Any ideas? Thank you in advance!
Rob_D Posted May 31, 2018 Posted May 31, 2018 In the "action" options/settings, make sure you have "sart in" set. This has caught me out before.
ITHand Posted May 31, 2018 Author Posted May 31, 2018 I actually found this information that I also tested, with no more success unfortunately ...
Rob_D Posted May 31, 2018 Posted May 31, 2018 So am I right in assuming that the scheduled task isn't being created on the target machine? Or it is being created but not running? If it's not being created try using the "Update" or "Create" action rather than "Replace". If it's just not running check the event logs for errors. (In fact do this anyway, it might point you in the right direction).
ITHand Posted May 31, 2018 Author Posted May 31, 2018 The task does not appear on the computer, and I also tested the option "update", without more success, there might be the option "create" to try, but the option "replace" and "update" should normally create it to what I read, but I will do this test immediately in case. For logs, given that it is not displayed, I can not find anything in the logs ...
ITHand Posted May 31, 2018 Author Posted May 31, 2018 (edited) Unfortunately, no more success with the function "create" ... Another idea? Is it a security feature implanted in Windows 10 that blocks this? Edited May 31, 2018 by ITHand
free780 Posted May 31, 2018 Posted May 31, 2018 Make sure you are using SYSTEM from AD not the server/client that you are running the Group Policy MMC on. Failing that turn on GPP logging.
ITHand Posted May 31, 2018 Author Posted May 31, 2018 I found the solution, when I was looking for the verification name "NT AUTHORITY\ SYSTEM" on my AD in French, the name it changed automatically for "AUTHORITY NT\ SYSTEM" ... It was functional locally this way, but we must believe that by GPO, it's more capricious ... I hope that this information can help someone else... Thank for your responses! 1
Rob_D Posted June 1, 2018 Posted June 1, 2018 Thanks for letting us know and glad this all worked out for you.
jjd81 Posted September 12, 2018 Posted September 12, 2018 the issue I had was that is wouldn't create the task IF i didn't use '-' for the arguments instead of '/'. so weird... this was for W10 1803 systems with domain at 2012r2.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now