"logon as a service" and "logon as a batch job"

Gurus,

I understand, in highly secure environments, where you have to in certain
situations have to give certain accounts the "logon as a service" right.
But how does one know when to also give that account the "logon as a batch
job" right?

--
Spin

Pegasus
Sat Sep 02 06:06:25 CDT 2006


"Spin" <Spin@spin.com> wrote in message
news:4lt3p5F3ia0bU1@individual.net...
> Gurus,
>
> I understand, in highly secure environments, where you have to in certain
> situations have to give certain accounts the "logon as a service" right.
> But how does one know when to also give that account the "logon as a batch
> job" right?
>
> --
> Spin
>
>

You need it for accounts used for scheduling tasks.

Roger
Sat Sep 02 07:02:37 CDT 2006

"Spin" <Spin@spin.com> wrote in message
news:4lt3p5F3ia0bU1@individual.net...
> Gurus,
>
> I understand, in highly secure environments, where you have to in certain
> situations have to give certain accounts the "logon as a service" right.
> But how does one know when to also give that account the "logon as a batch
> job" right?
>
> --
> Spin
>
>
It is not actually an "also give" situation, maybe also,
so both rights are allowed, else separately so the "also"
is not necessary.

If submitted to a batch scheduler, like MsTask, batch;
if started in contolled context by the system SC, service.
Pretty unusual to give both for the same binaries used.
--
Roger