I even tried, on one of the faulty computers, changing the task to run under my user account (a domain admin) rather than the system account, and the issue is the same. There is nothing I can see that sets the 2 faulty computers apart from the others except than this one issue. These computers are all running windand they are all built from the same image, all on the same domain.
#Freefilesync batch task scheduler code#
On the faulty computers, it gives a return code of 2147942401 which googling tells me is an "illegal operation" but I haven't found a more precise explanation. On the good computers, the history tab, "Action competed" category it gives a return code of 0. But the history tab logs another successful task completion. Right click the task and select "Run", I get no pop up, and the computer does not restart in 5 minutes.
With the exception of the 2 faulty computers, on each computer that I tested, when I right click the task and select "Run" I immediately see a popup telling me the computer will reboot in 5 minutes - and then it does. Action: Start a Program: shutdown,exe /r /t 300.Run the task under user Local_Machine\System I have double and triple checked the settings on the faulty computers, even deleted the task and recreated it bu the issue remains. I setup the task identically on each computer. The strange thing is that if I look in the "History" tab of the scheduled task GUI It says the task completed successfully - but it didn't reboot. This is working on most of the computers, but for some reason 2 of them are not rebooting.
#Freefilesync batch task scheduler windows 10#
I created a scheduled task on each of our windows 10 computers (about 40 of them) to reboot every Saturday evening at 8:00.
0 kommentar(er)
