On Jul 4, 3:02*am, "Pegasus [MVP]" <n...@microsoft.com> wrote:
> *** See below.
>
> "Jose" <jose_e...******.com> wrote in message
>
> news:0deb53d0-20c7-45ec-8725-57e7cf356d50@y9g2000yqg.googlegroups.com...
> On Jul 3, 8:23 pm, "NICK MEALE" <nmeal...@earthlink.net> wrote:
>
> > XP Software
> > When trying to set a new time for Norton to scan a box says I don't have
> > permission to do this...How do I get permission?...Error
> > 0x80041310...Thanks,Nick Meale
>
> The Properties of a Scheduled Task desire an account that has a
> password. *You can create a new task (and it will complain), but it
> will never run without a password. *Be sure the Windows Task Service
> is running and set to Automatic.
> *** The service is called "Task Scheduler".
>
> You can add a password to the account you are trying to use, set up a
> separate account just for STs you create.
>
> I used to swear a password was required but found a way around it that
> I don't really care for. *The first two options are the best. *I would
> not recommend adding a password to the Administrator account because
> if you ever forget it and need that account, you may be in some big
> trouble!
> *** This flies against all good computing practice. Having an administrator
> *** account without a strong password renders the machine wide open
> *** to all types of abuse, in particular by hackers. There are several
> *** standard methods to protect against forgotten passwords, e.g.
> *** - Keep a printed list in a safe place of all passwords.
> *** - Have more than one admin account so that you can use one to
> *** - reset the password of the other.
> *** - Use a password resetting tool such as the Nordahl boot disk.
>
> All of your STs are in the c:\windows\tasks folder where you can
> browse them, create, modify, test (Run) them by right clicking and
> trying the properties and options. *You may want to create a simple
> task just to run CMD.EXE and figure out how to get that to work bu
> running it manually and then apply your skill to your more difficult
> tasks.
>
> There is a ST log file in c:\windows called schedlgu.txt which helps
> troubleshooting. *Stop the Windows Task Service to delete the file of
> junk, restart the Service to recreate a new log file. *Google any
> errors or come back here.
> *** Deleting the Task Scheduler log file is neither necessary nor
> *** recommended. Since it is a circular log file, it has a fixed size.
> *** The "junk" you refer to (= records of past tasks) will be
> *** overwritten automatically, without having to stop/start any
> *** service.

My bad on the task name.

The OP can run his computer however he/she chooses to run it.

The OP did not ask for advice or best practices regarding password
creation. The problem is troubleshooting a scheduled task that is not
working. Once that is resolved, apply whatever security measures that
fulfill your requirements.

I believe my post is the most efficient method of troubleshooting this
problem while at the same time supplying knowledge that will help with
any future scheduled task issues and eliminating the need for the "it
(still) doesn't work" exchanges later.

Now, the OP will know there is another way to investigate STs without
having to go through the inefficient method of beginning with the
Start button every time. Not everyone knows this.

The OP also learns that there is a log file, where it is and how to
manipulate it so it only contains information relevant to the
afflicted task.

Not everyone knows there even is a log file, where it is, how to
interpret it or how to empty it when they feel like it. This
knowledge makes it easier to troubleshoot the current ST problem. Why
repeatedly look through log file entries that have nothing to do with
the current problem or information from the current troubleshooting
efforts? The OP knows all this now without even asking.

Supply enough information to troubleshoot and solve the problem as
efficiently as possible, avoid needless time consuming and potentially
frustrating interactions by anticipating future questions before they
are asked, while at the same time imparting knowledge and information
that the OP may not know.