Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 3867 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Client push to XP problem: scheduled task is created but fails, then succeeds when scheduled

VictorSlade

We have run into this on all our XP machines (Win7 works smoothly for us). We push from the Enterprise Console (v5.2). The scheduled task gets setup on the XP client, but fails. If I click on it to RUN it, it fails. But if I schedule it, say, 2 minutes out (which has me enter a userID/pw), it then runs successfully. Any suggestions are much appreciated. Thanks

:39099


This thread was automatically locked due to age.
Parents
  • 0

    Hello VictorSlade,

    as a task can obviously created by SEC the access denied is likely caused by some error when entering the command. The following should work:

    schtasks /create /s <target> /u <user> /p <pwd> /ru <user> /rp <pwd> /SC ONCE /ST 23:00:00 /TN Test /TR C:\windows\system32\calc.exe /v1

     where <target> is the PC and <user> <pw> are the credentials you enter in Protect Computers. The /v1 is needed if the target is pre-Vista.  A common cause for a task w/o a user set are incorrect values for /ru or /rp (you then get a WARNING: The Scheduled task "Test" has been created, but may not run because the account information could not be set) - but as there's only one set of credentials when using Protect Computers this can be ruled out. 

    Christian

    :39243
Reply
  • 0

    Hello VictorSlade,

    as a task can obviously created by SEC the access denied is likely caused by some error when entering the command. The following should work:

    schtasks /create /s <target> /u <user> /p <pwd> /ru <user> /rp <pwd> /SC ONCE /ST 23:00:00 /TN Test /TR C:\windows\system32\calc.exe /v1

     where <target> is the PC and <user> <pw> are the credentials you enter in Protect Computers. The /v1 is needed if the target is pre-Vista.  A common cause for a task w/o a user set are incorrect values for /ru or /rp (you then get a WARNING: The Scheduled task "Test" has been created, but may not run because the account information could not be set) - but as there's only one set of credentials when using Protect Computers this can be ruled out. 

    Christian

    :39243
Children
No Data