32
Deny log on as a batch job
Member Server
Default
Legacy Client
Enterprise Client
High Security Client
Not Defined
Guests;
Support_388945a0;
Guest
Guests;
Support_388945a0;
Guest
Guests;
Support_388945a0;
Guest
Note:
ANONOYMOUS LOGON, Built-in Administrator, Support_388945a0; Guest; and all NON-
operating system service accounts are not included in the .inf security template. These accounts and
groups have unique SIDs for each domain in the network. Therefore, they must be added manually.
For further information, see the Manual Hardening Procedures in section 2.8.7.
The
Deny log on as a batch job
user right determines which accounts are prevented from logging on
to the system as a batch job. A batch job is not a batch file (bat)-but rather a batch-queue facility.
Accounts used for scheduling jobs via the Task Scheduler need this right. This
Deny log on as a batch
job
user right setting overrides the
Log on as a batch job
user right setting. Accounts with this logon
right could be used to schedule jobs that could consume excessive system resources leading to a DoS
condition. For this reason, not assigning the
Deny log on as a batch job
user right to the
recommended accounts can be a security risk.
Deny log on through Terminal Services
Member Server
Default
Legacy Client
Enterprise Client
High Security Client
Not Defined
Built-in Administrator;
Guests;
Support_388945a0;
Guest ;all NON-
operating system
service accounts
Built-in Administrator;
Guests;
Support_388945a0;
Guest ;all NON-
operating system
service accounts
Built-in Administrator;
Guests;
Support_388945a0;
Guest ;all NON-
operating system
service accounts
Important:
For all HP NAS server systems, administrators should only deny Guests,
Support_388945a0, Guest, and all NON-operating system service accounts
Note: ANONOYMOUS LOGON, Built-in Administrator, Support_388945a0; Guest; and all NON-
operating system service accounts are not included in the .inf security template. These accounts and
groups have unique SIDs for each domain in the network. Therefore, they must be added manually.
For further information, see the Manual Hardening Procedures in section 2.8.7.
The
Deny log on through Terminal Services
user right determines which users and groups are
prohibited from logging on as a Terminal Services client. After joining the baseline member server to
a domain environment, there is no need to use local accounts to access the server from the network.
Domain accounts can access the server for administration and end-user processing. Remember, the
MSBP will not receive this Group Policy until the server is joined to the domain and restarted twice.
Therefore, the use of the local Administrator accounts is prohibited.