mvbighead
Diamond Member
Well, this sucks. I have deployed Schtasks that run at routine intervals for various system maintenance in my environment. Today I am seeing that the tasks have stopped being pulled down (GPO) and installing, and further yet, I cannot even create a simple scheduled task on any machine (with admin access).
Further yet, I am checking permissions on the C:\Windows\Tasks via a method suggested on another forum that I found using google. The permissions are right where they should be, and I am even able creating any number of .txt files and other files in the tasks directory, but as soon as I attempt to create a .job file or rename a file to .job, I am denied access. I am at my wits end here... anyone have an idea?
All updates current on each and every machine, and the last round of updates have been rolled back to test but still encountering this problem.
Further yet, I am checking permissions on the C:\Windows\Tasks via a method suggested on another forum that I found using google. The permissions are right where they should be, and I am even able creating any number of .txt files and other files in the tasks directory, but as soon as I attempt to create a .job file or rename a file to .job, I am denied access. I am at my wits end here... anyone have an idea?
All updates current on each and every machine, and the last round of updates have been rolled back to test but still encountering this problem.
