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.
  • 0

    Hi,

    Out of interest, if you set the key mentioned here:

    /search?q= 13229

    do you get the same behaviour when attempting a push?

    Regards,

    Jak

    :39107
  • 0

    Thank you, Jak. I looked at this but it did not seem to apply exactly. I checked the Scheduled Task logs and see this: "Sophos_InstTask.job" (setup.exe) 4/8/2013 3:56:49 PM ** ERROR **
     The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.
     The specific error is:
     0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.

    I then found this kb link: http://support.microsoft.com/kb/317529

    It seems to me that the credentials don't work after getting passed to the client. If I then reschedule the task that Sophos has already pushed, (which includes prompting me for credentials), it will then work, and my guess is that it works because I have thus manually provided the credentials that it needs.

    This leads me to believe that I will have to abandon my plan to push to the XP clients from the console due to this glitch, which is disappointing because I believe that means I will need to start over and use Active Directory for the rollout. If there is a way to make the XP clients work from the console, that would be my preference. If you can shed some light on this I would be quite appreciative! In any case, thanks for your assistance.

    :39177
  • 0

    Hello VictorSlade,

    the quoted KB article applies to NT/2000. Looking around I've found two other articles, both for XP SP1 and the issue fixed in SP2 - unlikely that your clients are still on SP1. Can you remotely and manually (from the console) create and run a task using  schtasks? 

    Christian  

    :39187
  • 0

    Yes, Christian, we are at SP3. I tried SCHTASKS from the console to the PC, but get "access denied" and have not figured out the proper syntax.

    :39229
  • 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