Re: Scheduling Tasks with jt.exe

Tech-Archive recommends: Speed Up your PC by fixing your registry



Maybe I wasn't clear in my posts. I don't have a problem setting up a task
if I use my own credentials. What I'm trying to do is logon to a
workstation as user A and create a task on the server to run under user B
credentials. I already made sure the user I want the task to run as is
authorized to run as a batch job on the server. Once I create the job if I
go to the task scheduler on the server and enter a password it runs
correctly.

Another thing that I have found is that I can run jobs remotely from my
workstation on our test server but not on our production server. The only
differences I found were Act as part of the operating system, create a token
object and log on as a service on the production server are all set to
domainname\ntservice. The test server has no settings. Would any of these
settings cause the problems I'm having?

"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:ORuLgTiKHHA.4460@xxxxxxxxxxxxxxxxxxxxxxx
I don't have access to a Win2000 server right now but
had no problem scheduling a task on an SBS server
from one of the workstations, using this line:

schtasks /create /s SomeServer /u SomeDomain\config
/p SomePassword /sc daily /st 13:01:00 /tn "Test"
/tr c:\temp\test.bat

The task ran at 13:01 as expected.

You must make sure that the account specified after the
/u switch is authorised to run as a batch job on the
target machine.


"Dennis" <res7wt35@xxxxxxxxxxx> wrote in message
news:5VEkh.2511$511.2314@xxxxxxxxxxx
Sorry I didn't mention the server version. In any case, I tried to
schedule
a task on a remote server from my workstation via schtasks.exe. It
creates
the task correctly, but it won't set the account information. I have
administrative rights on the remote server and the local security policy
on
the server allows me to log on as a batch job. This is basically the
same
problem I had using jt.exe. Has anyone successfully created a job on a
remote server using either schtasks or jt.exe? If so, were there any
security settings that had to be modified?
If I logon to my local machine with the userid and password that I'm
setting
the job up on the remote server to run under then it works correctly.
All
of these machines are running w2k. I've already modified schtasks.exe to
run on w2k. The following is the create statement and the warning
message
that is returned.

Please be aware that I'm a programmer, not a windows administrator so I
would appreciate it if you could be as precise as possible.

schtasks /create /tn tstdennis /tr "program name" /sc daily /st 09:00:00
/s
\\computername /u domain\user /p password /ru domain\user /rp password

WARNING: The Scheduled task "tstdennis" has been created, but may not run
because the account information could not be set.

"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:uoqyxstJHHA.320@xxxxxxxxxxxxxxxxxxxxxxx
You should have said that you wanted to run the job on
a Win2000 PC. Here is how to do it with schtasks.exe:
http://www.jsifaq.com/SUBK/tip5300/rh5335.htm


"Dennis" <res7wt35@xxxxxxxxxxx> wrote in message
news:gHdjh.1083$4e.1069@xxxxxxxxxxx
Thanks for the reply. It is my belief that schtasks doesn't work on
win2k
which is what our servers are running.

All of the users that will be using this window have administrator
rights
on
the servers so I guess I can just have them run it on the servers via
terminal service.

In the meantime, if anyone has had success setting up and running jobs
on
remote servers with jt.exe I would appreciate it if they could shine
some
light on what security settings were necessary...
"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:%238PKIhLJHHA.4000@xxxxxxxxxxxxxxxxxxxxxxx

"Dennis" <res7wt35@xxxxxxxxxxx> wrote in message
news:8bmih.2588$Iy5.1709@xxxxxxxxxxx
I'm trying to schedule tasks on a remote server by using jt.exe.
The
tasks
are being created but there are a couple of problems. The first is
the
password doesn't seem to be getting set. After I add the task I
try
to
run
it from the server and get a "cannot start" error. After I reset
the
password through the scheduler GUI it works fine. The second
problem
is
I
can't run the task on the server from a workstation. I have full
administrator rights on the server. The syntax I use for setting
up
the
job
is:

jt.exe /sm \\computername /ctj starttime=09:00 startdate=12/20/2006
type=daily typearguments=1 /sj
applicationname=c:\UIBatch\Exe\ui_batch.exe
parameters= "parm list" workingdirectory=c:\UIBatch\Exe suspend=0
/sc
DOMAINNAME\userid password /saj c:\winnt\tasks\testing.

I have already checked the local policy on the server and I can
logon
as
a
batch job. Are there any other security settings I need to check
or
set?

Thanks in advance for your help and Merry Christmas to all.

Dennis



jt.exe is not known for ease of use. Much easier to use
schtasks.exe.
It comes with WinXP.

If you have doubts about policy settings, use the interactive Task
Scheduler to schedule some test jobs.












.



Relevant Pages

  • RE: login and email problems
    ... Please carefully check settings required in my previous post and post the ... Install the RPC ping utility on the client computer and then open a command ... Microsoft CSS Online Newsgroup Support ... Leave the Default Gateway of the internal NIC blank of the server box. ...
    (microsoft.public.windows.server.sbs)
  • Re: Monitoring and Alerts
    ... Relay settings for Exchange SMTP Virtual Server: ... we pursue the performance alerts issue further. ... | Subject: Re: Monitoring and Alerts ...
    (microsoft.public.windows.server.sbs)
  • Re: User-Specific Settings
    ... clear statement from the vendor that running ACT! ... Server is *not* supported. ... it would explain why changes in settings are not preserved. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.apps)
  • Re: All remote access stopped ?
    ... Server 2003 Remote Web Workplace ... Microsoft CSS Online Newsgroup Support ... <Firewall Settings on lefthand side, Advanced settings, Under attack ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Client not yet reported
    ... The client still fails to report. ... Check your server status ... Suggestion 2: Check the IIS settings: ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)