Re: Scheduled Task on Client PC with NT AUTHORITY/SYSTEM account f

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Claus,
I'm trying to have SpyBot Search and Destroy run nightly. It auto-updates
when it runs, so it involves connecting to the internet and downloading
updates.
I have not even been able to run the windows calculator as a scheduled task
with this account, though, and that's all local (I hope).
I've added the scheduled task user account to various groups: first Users
and Internet Users, then Power Users, then Administrators (just for a test).
I did a "gpupdate" on the client PC after each change. No joy.
Alas, if I can't fix it, these tasks might just have to run under my user
account and I'll have to change the password on them when I change mine...
Not a huge bother, as we're a small office.
Thanks,
Ari

"Claus" wrote:

And what program are you trying to run? Is it local or does it involve
network resources?

--
Claus
"doucettea" <doucettea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9461966C-45B6-46CA-B7F8-9EDD761D1A58@xxxxxxxxxxxxxxxx
The client PC is running XP Pro SP2, with all the latest updates.
I've tried making a local and then a domain user account for scheduled
tasks. Neither has worked.
I does work if I schedule the task under my administrator account,
though...

I don't get why they won't work on this PC... All the other PCs have
scheduled tasks running as the system account. This particular PC recently
had XP reinstalled on a new HDD.

"Claus" wrote:

A bit more info might help us to help you. What OS is running on that
box?
What program are you trying to run? What error messages do you get?

Also, it is not a good idea to schedule anything under the System
account.
If you are trying to run something locally, create an account for that
and
give it the permission it needs to do the task. If it is not defined to a
local task, create a domain account with the appropriate permissions and
run
the task under that account.

--
Claus
"doucettea" <doucettea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C4AF62B-41E8-4694-ACCD-779DD18A0FA0@xxxxxxxxxxxxxxxx
Hi all,
I have scheduled tasks running under the NT AUTHORITY\SYSTEM account on
some
PCs, but it doesn't work on one client PC.
At first, I thought this might have to do with network permissions and
the
System account, but I can't even get it to run a local program like
"calc.exe"...
Has anyone else run into this? Do you know how I can fix it?
Thanks,
Ari






.



Relevant Pages

  • Re: Log on as a batch job
    ... Depending on the task you are trying to run, the account you use may need ... be a member of the local Administrators group on the PC. ... And the entire point of Logon as a Batch Job privilege is to ... My brief experiments suggest that running a scheduled task requires the user ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Scheduled Task on Client PC with NT AUTHORITY/SYSTEM account fails
    ... tasks under NT AUTHORITY\SYSTEM account. ... Right click the scheduled task and click Properties. ... Microsoft Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Disk Clean Up
    ... It may be part of the TIF cleanup, ... > see anything in the CLEANMGR /SAGESET that would clean that out. ... > 4) Go to Control Panel, Scheduled Tasks, Add Scheduled Task. ... > and the password for that account. ...
    (microsoft.public.windowsxp.newusers)
  • Re: Local System account and network resource access
    ... "Pegasus (MVP)" wrote: ... a domain account, there wasn't any issues, no issues at all. ... If there no ways we can specify a share that allows the scheduled task ... access network resource, our discussion ...
    (microsoft.public.win2000.file_system)
  • Re: Disk Clean Up
    ... MS-MVP Windows Media Center\Windows Powered Smart Display ... >> see anything in the CLEANMGR /SAGESET that would clean that out. ... >> 4) Go to Control Panel, Scheduled Tasks, Add Scheduled Task. ... >> and the password for that account. ...
    (microsoft.public.windowsxp.newusers)