N
net_tech
Guest
An admin created a few scheduled tasks on a standalone system (Windows 10 x64 1607) that start 1 min after ANY user logs in to the computer. Both tasks start powershell scripts. Tasks are set to run only when user is logged on and Users group is selected under Use the following user account. The trigger is at log on of Any user and delay task for 1 min is set. All tasks created in the past are showing up in the task scheduler library and respective XML files can be seen under C:\Windows\System32\Tasks.
The same admin created another scheduled task for another ps script using the same triggers and settings. New tasks is visible in the C:\Windows\System32\Tasks and the task scheduler library for the admin, when admin logs off and new user logs in to the system new task does not show up for the user in the task scheduler library. We can replicate the problem with a missing task for new and existing users which rules out the problem with profiles.
Does anyone have any suggestions on how to repair this issue?
The perms of the old and new XML files seem to match.
Thanks
Edit: Users are getting access denied to HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\
More...
The same admin created another scheduled task for another ps script using the same triggers and settings. New tasks is visible in the C:\Windows\System32\Tasks and the task scheduler library for the admin, when admin logs off and new user logs in to the system new task does not show up for the user in the task scheduler library. We can replicate the problem with a missing task for new and existing users which rules out the problem with profiles.
Does anyone have any suggestions on how to repair this issue?
The perms of the old and new XML files seem to match.
Thanks
Edit: Users are getting access denied to HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\
More...