Deny log on as a batch job
- Windows 10
Describes the best practices, location, values, policy management, and security considerations for the Deny log on as a batch job security policy setting.
This policy setting determines which accounts are prevented from logging on by using a batch-queue tool to schedule and start jobs automatically in the future. The ability to log on by using a batch-queue tool is needed for any account that is used to start scheduled jobs by means of the Task Scheduler.
- User-defined list of accounts
- Not defined
- When you assign this user right, thoroughly test that the effect is what you intended.
- Within a domain, modify this setting on the applicable Group Policy Object (GPO).
- Deny log on as a batch job prevents administrators or operators from using their personal accounts to schedule tasks, which helps with business continuity when that person transitions to other positions or responsibilities.
Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment
The following table lists the actual and effective default policy values for the most recent supported versions of Windows. Default values are also listed on the policy’s property page.
|Server type or GPO||Default value|
|Default Domain Policy||Not defined|
|Default Domain Controller Policy||Not defined|
|Stand-Alone Server Default Settings||Not defined|
|Domain Controller Effective Default Settings||Not defined|
|Member Server Effective Default Settings||Not defined|
|Client Computer Effective Default Settings||Not defined|
This section describes features and tools available to help you manage this policy.
A restart of the device is not required for this policy setting to be effective.
Any change to the user rights assignment for an account becomes effective the next time the owner of the account logs on.
This policy setting might conflict with and negate the Log on as a batch job setting.
On a domain-joined device, including the domain controller, this policy can be overwritten by a domain policy, which will prevent you from modifying the local policy setting.
For example, if you are trying to configure Task Scheduler on your domain controller, check the Settings tab of your two domain controller policy and domain policy GPOs in the Group Policy Management Console (GPMC). Verify the targeted account is not present in the Deny log on as a batch job
User Rights Assignment and also correctly configured in the Log on as a batch job setting.
Settings are applied in the following order through a Group Policy Object (GPO), which will overwrite settings on the local computer at the next Group Policy update:
- Local policy settings
- Site policy settings
- Domain policy settings
- OU policy settings
When a local setting is greyed out, it indicates that a GPO currently controls that setting.
This section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation.
Accounts that have the Deny log on as a batch job user right could be used to schedule jobs that could consume excessive computer resources and cause a denial-of-service condition.
Assign the Deny log on as a batch job user right to the local Guest account.
If you assign the Deny log on as a batch job user right to other accounts, you could deny the ability to perform required job activities to users who are assigned specific administrative roles. You should confirm that delegated tasks are not affected adversely.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.