New
#21
Was this task scheduler entry you created built with the "run with highest privileges" as the tutorial describes?
If so, I suspect that is why there was no UAC interference.
Anyway, many thanks for trying this experiment. Very interesting.
I'm going to pass along this thread's URL to the Clockwise author, just for reference. Hopefully the Win7-compatible program (which is not a scheduled task, but an always-running program) will somehow accomplish this "run with highest privileges" status on its own, I would guess. Or else it would have to make use of a scheduled task (perhaps built as part of the Clockwise installer process) to do just what you've done, rather than from within the program itself as was acceptable under WinXP.
As my scheduled Time Synchronization task has not worked since installation, I have been doing some minor tweaking. The task would always finish with code 0x5 which translates to Access denied.
Which led me to accounts and privileges. Originally, it was set to run under NT AUTHORITY\NETWORK SERVICE account (security principal).
First I changed it to NT AUTHORITY\LOCAL SERVICE. No game, 0x5 again.
So I went and had the President of the System do it , i.e. NT AUTHORITY\SYSTEM. And, bingo. Result 0x0, Time Service started (and later shut down), time synchronized, the whole shebang. It works.
The funny thing is that the task seems to work on my Windows 7 Enterprise x86 under the NT AUTHORITY\LOCAL SERVICE account, which has been set up like that there since installation (but, why is it different from my Ultimate x64 )
Therefore, I need feedback, preferably from Windows 7 x64 Ultimate users.
1. Does the Time Synchronization task in Task Scheduler work (Last Run Result 0x0)?
2. If not, does it fail with Last Run Result 0x5 (= ACCESS_DENIED)?
3. Which account (i.e. security principal) does it run under in either case?
Hello Tomislav,
Here's my exported task if it will help any. It runs just fine for me as well.