Scheduled Tasks show running, but really aren't

From: JetCityJules (JetCityJules.1fkz2m_at_mail.webservertalk.com)
Date: 11/11/04

  • Next message: Damon: "Re: Security Event ID 675" 
    Date: Thu, 11 Nov 2004 10:37:14 -0600

    I have created a batch file to auto-create a scheduled task that
    eliminates having to setup the task using the wizard, and to circumvent
    the user account with password requirement.

    I am using this script to create a schedule task from a dos prompt:

    schtasks /create /sc daily /ru system /tn Bearback /st 22:00:00 /tr
    "c:\p6\bearback.exe AUTO"

    I found this syntax from MS site:

    http://tinyurl.com/2l38n

    Based on what MS says in this article, this creates a task using the NT
    Authority/System account which should have administrator rights and that
    does not have a password. This allows me to create a batch file that I
    can have people run on their computers without having to walk them thru
    the schedule task wizard.

    The problem lies in only some XP SP1, SP2, Win2000, and the problem is
    that the task will show as running but nothing happens. If I don’t end
    the task it continues to show status of running until the default 72
    hours expires.

    If I open up Task Manager, click on Process tab, I can see the
    Bearback.exe (what the schedule task is suppose to run) running but its
    showing CPU usage as zero.

    It doesn’t matter what the application or .exe is I’m calling on any
    will behave the same way as described on certain computers only.

    In trying to "fix" the tasks that don't really run, I have had them add
    a password to the administator account, manually create the tasks.
    Sometimes this works, other times it shows as running, but nothing is
    really happening. I am stumped.

    As I have a lot of non-computer literate people to tend to, I would
    appreciate any assistance in figuring out what the problem is, or how
    to fix it. 

    --
JetCityJules
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message466736.html
  • Next message: Damon: "Re: Security Event ID 675"

    Relevant Pages

    • Re: The task completed with an exit code of (1)
      ... Ikram - if you are looking for help regarding a batch file that throws an ... Account Operators, and using this account to run the schedule task. ... But when I make the NSUser a member of Administrators group the task runs ...
      (microsoft.public.windows.server.active_directory)
    • Re: I am running a batch file for creating new users in the Active
      ... Is D214 the name of your server or the name of your domain? ... You added NSUser to 'Account Operators' ... You log on locally to your domain controller using NSUser account. ... I running this schedule task on Domain Controller, ...
      (microsoft.public.windows.server.general)
    • Scheduled task shows as running, but nothing is really happening
      ... I have created a batch file to auto-create a scheduled task that eliminates ... having to setup the task using the wizard, and to circumvent the user account ... I am using this script to create a schedule task from a dos prompt: ... schedule task wizard. ...
      (microsoft.public.windowsxp.configuration_manage)
    • Scheduled tasks problems
      ... I have created a batch file to auto-create a scheduled task that eliminates ... having to setup the task using the wizard, and to circumvent the user account ... I am using this script to create a schedule task from a dos prompt: ... schedule task wizard. ...
      (microsoft.public.windowsxp.general)
    • Schedules tasks not working properly
      ... I have created a batch file to auto-create a scheduled task that eliminates ... having to setup the task using the wizard, and to circumvent the user account ... I am using this script to create a schedule task from a dos prompt: ... schedule task wizard. ...
      (microsoft.public.windowsxp.customize)