Re: Task Scheduler question

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hmmm. A little more difficult. Have you tried to change the security of the
task to "full control" for everyone or the users desired? I don't know if
this would allow a user to initiate a scheduled task under different
credentials, but worth a try.

--
/kj
"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F2A5A664-60F8-43B6-B920-168816E64680@xxxxxxxxxxxxxxxx
When I tried to create a task, it first asked me to input 'administrator'
password, after the task was created, I still couldn't 'Run' (right click
on
the task) it without 'set password' for it.

Our goal is to set the task (by our program/packaging/other methods) so
that
users won't need to do anything after installing the package and the task
can
run both as scheduled and at anytime if a user clicks 'Run'.

Thanks for your input anyways.

Peter

"kj" wrote:

Perhaps schtasks /create /tn (taskname) or schtasks /change will help?

--
/kj
"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:40E3953F-E2A7-49BF-B5E3-9211E8DD6EDB@xxxxxxxxxxxxxxxx
Thanks Jerold.

Using AT.exe is not good since it won't allow us to set the proper task
name
we want.

The task was set by a package, so there is no way that we can have the
task
scheduled and run, and users don't need to do anything (set password)
after
the package installation?

Or different ideas from anybody?

Thanks again,
Peter

"Jerold Schulman" wrote:

On Wed, 20 Sep 2006 16:11:02 -0700, Peter
<Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I am adding a task to Task Scheduler on WS2003.

I have set the user account as 'Local System Account' by providing
empty
strings for both user(account) name and password in my program. But
when
I
logged on as administrator, the added task had been set ('Run As'
box)
under
server-name/Administrator account, and before the task can be 'run',
I
have
to 'Set Password' for the account.

Is there anyway I can avoid that, i.e. to run the task without
setting
password? I read some doc and learned that I can schedule the task
under
system account, so anybody can run it (and I don't need to set
password - I
assume), how can I do it? Is that done via setting parameters (in my
program)
or it has to be done through manual?


Thanks,
Peter

See tip 3215 » How do I schedule a job to run under the SYSTEM
context?
in the 'Tips & Tricks' at http://www.jsifaq.com

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com






.

Relevant Pages

  • SSIS Scheduling Failure - AcquireConnection Error
    ... package into SSIS services in Management Studio and ran the job manually. ... I got the dreaded 'AcquireConnection' error when I tried to schedule ... while logged onto the SQL Server 2005 database server itself. ... the 'SQL Agent Service Account'. ...
    (microsoft.public.sqlserver.dts)
  • Re: Scheduling a simple local package wont stick
    ... Well my domain account is the owner, and it is member of the local ... Where do I find out if this Sql server service account has the necessary ... - When you run the DTS package yourself, it runs with your credentials, ... DTS packages do not retain a schedule. ...
    (microsoft.public.sqlserver.dts)
  • Re: Grant Object Access
    ... Tweaking the ACL on the service will let the account inquire ... > has no control over the scheduled tasks in themselves (all the user can do ... > "Roger Abell" wrote in message ... >>> Schedule service correctly without making it a local administrator? ...
    (microsoft.public.windows.server.security)
  • Re: Task Scheduler question
    ... to 'full control' for everyone. ... The task was set by a package, so there is no way that we can have the ... I have set the user account as 'Local System Account' by providing ... I read some doc and learned that I can schedule the task ...
    (microsoft.public.windows.group_policy)
  • Re: Task Scheduler question
    ... to 'full control' for everyone. ... The task was set by a package, so there is no way that we can have ... I have set the user account as 'Local System Account' by providing ... I read some doc and learned that I can schedule the task ...
    (microsoft.public.windows.group_policy)