We are continueing testing of a Master
Server with a Remote Contol client on
Win2K servers. The Remote Control user
submits a job to the Master Server, once
in awhile the job will show up in the
monitor, most of the time it does not.
When it doesn't show up in the monitor, the
job doesn't run. The user properly saves
the submitted job each time.

Any ideas? Also, when the jobs do successfully
run, they seem to run as the use who has started
the 24x7 scheduler on the Master Server.

Thanks, Don

Set the job to run synchronous and see what happens. Also what you get in the job log for this particular job?

: We are continueing testing of a Master
: Server with a Remote Contol client on
: Win2K servers. The Remote Control user
: submits a job to the Master Server, once
: in awhile the job will show up in the
: monitor, most of the time it does not.
: When it doesn't show up in the monitor, the
: job doesn't run. The user properly saves
: the submitted job each time.

: Any ideas? Also, when the jobs do successfully
: run, they seem to run as the use who has started
: the 24x7 scheduler on the Master Server.

: Thanks, Don

: Set the job to run synchronous and see what happens. Also what you get in the
: job log for this particular job?

The box to set the job to Asyncronous is not
checked, so I am hopefully correctly assuming
that the job is running synchronously. When
the job does not show up in the Monitor, it does
not run and there is no trace in the job log
for it either.

Don

: The box to set the job to Asyncronous is not
: checked, so I am hopefully correctly assuming
: that the job is running synchronously. When
: the job does not show up in the Monitor, it does
: not run and there is no trace in the job log
: for it either.

: Don

As a folow up, after a little more testing, here
is a bit more information. The monitor part seems
if the user does not try to "change the user" when
he submits the job regularly, the job shows up
in the monitor, runs, and shows up in the log. This
job prints a file showing that job submitted
is trying to reference a preference file
under the user who started the Master Server and
not the user who submitted the job.

When the user changed the submit to run as
a different user (he used his login name and
password, job failed with an error: 1314
"A required privilege not held by the client." I then
added the user to the Standard User Group with
his normal login and password.

It was at this point where we stopped seeing
anything in the Monitor or job log.

Don

The user needs to have "Logon as a batch job" privilege which is no given by default to anyone and must be given expicitly.

: As a folow up, after a little more testing, here
: is a bit more information. The monitor part seems
: if the user does not try to "change the user" when
: he submits the job regularly, the job shows up
: in the monitor, runs, and shows up in the log. This
: job prints a file showing that job submitted
: is trying to reference a preference file
: under the user who started the Master Server and
: not the user who submitted the job.

: When the user changed the submit to run as
: a different user (he used his login name and
: password, job failed with an error: 1314
: "A required privilege not held by the client." I then
: added the user to the Standard User Group with
: his normal login and password.

: It was at this point where we stopped seeing
: anything in the Monitor or job log.

: Don

: The user needs to have "Logon as a batch job" privilege which is no
: given by default to anyone and must be given expicitly.

We are still working on the "Run As
Another User" issue, we have made the
change to the local security policy.
Our network folks are reticient about
making a change to the GPO. Acording to
them, the change would effect about 1500
people and not just the 2 or 3 we have
testing. In total, only about 10 or 12
people would be using 24x7 in the end.

The question of dual processors came up.
If we are running Queues A and B, would
jobs be assigned a processor based upon
availability or would all jobs from both
queues run on the same processor. And
would it matter if 24x7 was running as
a service or a user on the Master Server?

Thanks,
Don

It would not matter if 24x7 was running as
a service or as a standalone server app. Queues are not bound to processors. The system decides which CPU(s) to use for each queue. The default behaviour on multi-processor machines is that the scheduling engine is mostly using CPU #1 while the operation system picks for all other processes which CPU or (CPUs) to use.

We provide a utility that can be used for binding processes to specific CPUs. This utility can help with the load balancing. You can get it here
http://www.softtreetech.com/24x7/script.htm

Look for BindCPU.exe.

PS. To schedule run of a batch file or external exe on specific CPUs used BindCPU with parameters in the job command line. To bind a script type job to specific CPU(s) set the job to run detached execute it using 'BindCPU [affinity mask] 24x7.exe /JOB [job id or name]' command.

: We are still working on the "Run As
: Another User" issue, we have made the
: change to the local security policy.
: Our network folks are reticient about
: making a change to the GPO. Acording to
: them, the change would effect about 1500
: people and not just the 2 or 3 we have
: testing. In total, only about 10 or 12
: people would be using 24x7 in the end.

: The question of dual processors came up.
: If we are running Queues A and B, would
: jobs be assigned a processor based upon
: availability or would all jobs from both
: queues run on the same processor. And
: would it matter if 24x7 was running as
: a service or a user on the Master Server?

: Thanks,
: Don