From 5b1d225cff3790dba79b55a1fca488ff60318322 Mon Sep 17 00:00:00 2001 From: Siddarth Mandalika Date: Mon, 11 Jul 2022 12:49:42 +0530 Subject: [PATCH] Update domain-controller-allow-server-operators-to-schedule-tasks.md --- ...omain-controller-allow-server-operators-to-schedule-tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/security-policy-settings/domain-controller-allow-server-operators-to-schedule-tasks.md b/windows/security/threat-protection/security-policy-settings/domain-controller-allow-server-operators-to-schedule-tasks.md index ad7e4030e3..4d00465fda 100644 --- a/windows/security/threat-protection/security-policy-settings/domain-controller-allow-server-operators-to-schedule-tasks.md +++ b/windows/security/threat-protection/security-policy-settings/domain-controller-allow-server-operators-to-schedule-tasks.md @@ -27,7 +27,7 @@ Describes the best practices, location, values, and security considerations for ## Reference -This policy setting determines whether server operators can use the**at** command to submit jobs. If you enable this policy setting, jobs that are created by server operators by means of the **at** command run in the context of the account that runs the Task Scheduler service. By default, that is the Local System account. +This policy setting determines whether server operators can use the **at** command to submit jobs. If you enable this policy setting, jobs that are created by server operators by means of the **at** command run in the context of the account that runs the Task Scheduler service. By default, that account is the Local System account. >**Note:**  This security option setting affects only the scheduler tool for the **at** command. It does not affect the Task Scheduler tool.