{
	"id": "6f5be359-6f43-44e3-a852-dab29f2ee1d5",
	"created_at": "2026-04-06T02:12:54.152813Z",
	"updated_at": "2026-04-10T03:22:01.059306Z",
	"deleted_at": null,
	"sha1_hash": "b5e4524f77afface70d3b15689cfad138d1d59eb",
	"title": "Domain controller: Allow server operators to schedule tasks",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 43097,
	"plain_text": "Domain controller: Allow server operators to schedule tasks\r\nBy Archiveddocs\r\nArchived: 2026-04-06 01:50:51 UTC\r\nApplies To: Windows Server 2003, Windows Vista, Windows XP, Windows Server 2008, Windows 7, Windows\r\n8.1, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2012, Windows 8\r\nThis security policy reference topic for the IT professional describes the best practices, location, values, and\r\nsecurity considerations for this policy setting.\r\nThis policy setting determines whether server operators are allowed to submit jobs by means of the at command.\r\nIf you enable this policy setting, jobs that are created by server operators by means of the at command run in the\r\ncontext of the account that runs the Task Scheduler service. By default, that is the Local System account.\r\nNote\r\nThis security option setting affects only the scheduler tool for the at command. It does not affect the Task\r\nScheduler tool.\r\nEnabling this policy setting means jobs that are created by server operators through the at command will be\r\nexecuted in the context of the account that is running that service—by default, that is the Local System account.\r\nThis means that server operators can perform tasks that the Local System account is able to do, but server\r\noperators would normally not be able to do, such as add their account to the local Administrators group.\r\nThe impact of enabling this policy setting should be small for most organizations. Users, including those in the\r\nServer Operators group, will still be able to create jobs by using the Task Scheduler Wizard, but those jobs will\r\nrun in the context of the account that the user authenticates with when setting up the job.\r\nEnabled\r\nDisabled\r\nNot defined\r\nBest practices for this policy are dependent on your security and operational requirements for task\r\nscheduling.\r\nGPO_name\\Computer Configuration\\Windows Settings\\Security Settings\\Local Policies\\Security Options\r\nThe following table lists the actual and effective default values for this policy. Default values are also listed on the\r\npolicy’s property page.\r\nhttps://technet.microsoft.com/library/jj852168.aspx\r\nPage 1 of 3\n\nServer type or GPO Default value\r\nDefault Domain Policy Not defined\r\nDefault Domain Controller Policy Not defined\r\nStand-Alone Server Default Settings Not defined\r\nDC Effective Default Settings Not defined\r\nMember Server Effective Default Settings Not defined\r\nClient Computer Effective Default Settings Not defined\r\nThere are no differences in this policy between operating systems beginning with Windows Server 2003.\r\nThis section describes features and tools that are available to help you manage this policy.\r\nNone. Changes to this policy become effective without a computer restart when they are saved locally or\r\ndistributed through Group Policy.\r\nThe at command schedules commands and programs to run on a computer at a specified time and date. The\r\nSchedule service must be running to use the at command. For more information about the at command, see At\r\n[Vista].\r\nThis section describes how an attacker might exploit a feature or its configuration, how to implement the\r\ncountermeasure, and the possible negative consequences of countermeasure implementation.\r\nTasks that run under the context of the Local System account can affect resources that are at a higher privilege\r\nlevel than the user account that scheduled the task.\r\nDisable the Domain controller: Allow server operators to schedule tasks setting.\r\nThe impact should be small for most organizations. Users (including those in the Server Operators group) can still\r\ncreate jobs by means of the Task Scheduler snap-in. However, those jobs run in the context of the account that the\r\nuser authenticates with when setting up the job.\r\nhttps://technet.microsoft.com/library/jj852168.aspx\r\nPage 2 of 3\n\nSource: https://technet.microsoft.com/library/jj852168.aspx\r\nhttps://technet.microsoft.com/library/jj852168.aspx\r\nPage 3 of 3",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://technet.microsoft.com/library/jj852168.aspx"
	],
	"report_names": [
		"jj852168.aspx"
	],
	"threat_actors": [],
	"ts_created_at": 1775441574,
	"ts_updated_at": 1775791321,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/b5e4524f77afface70d3b15689cfad138d1d59eb.pdf",
		"text": "https://archive.orkl.eu/b5e4524f77afface70d3b15689cfad138d1d59eb.txt",
		"img": "https://archive.orkl.eu/b5e4524f77afface70d3b15689cfad138d1d59eb.jpg"
	}
}