SystemRequirements

System Requirements and Remote Troubleshooting

Any system since the release of IE4 will have either Task Scheduler V1 or V2.
- Task Scheduler V2 was released with Windows Vista and Windows Server 2008.
To use the Task Scheduler Managed Wrapper (Microsoft.Win32.TaskScheduler), you must install the corresponding NuGet package(s) linked off the home page.

Windows XP, Windows Server 2003 and Prior

User must be a member of the Administrators, Backup Operators, or Server Operators group on the local computer.
User must have read/write permissions on the %windir%\Tasks\ directory.
Remote only: The Windows Firewall must be enabled.
Remote only: Allow the "File and Printer Sharing" firewall exception.
- To allow this exception click Start, Control Panel, double-click Windows Firewall, select the Exceptions tab, and then select the "File and Printer Sharing" firewall exception. Then click the Ok button in the Windows Firewall dialog box.

Windows Vista, Windows Server 2008 and Later

Local system access is configured by default as it is used by numerous processes within Windows.
Local users must have "Log on as a batch job" and "Log on as a service" privileges.
It is rare, but confirm that the "Task Scheduler" service is running and not producing failure errors in the Windows Event Log.
Remote access is not configured by default and may be limited by your Domain Administrator via Group Policy. Remote connection to the Windows Task Scheduler requires the following:
- Enable the "Remote Scheduled Tasks Management" firewall exception.
  - To allow this exception click Start, Control Panel, Security, Allow a program through Windows Firewall, and then select the "Remote Scheduled Tasks Management" check box. Then click the Ok button in the Windows Firewall Settings dialog box.
- Enable the "Remote Event Log Management" firewall exception.
  - See above.
- If you are using a 3rd-party firewall, you will need to work with that ISV or your IT department to enable access to the above two items.
- The "Remote Registry" service must be running in order for the Task Scheduler V1 to connect to this computer. This is also the case if specifying forceV1=true when connecting from a V2 system in the TaskService constructor.
  - In Service Manager on the remote system, you may need to set this service to start automatically.

Windows 10

User @erniealega contributed this list of inbound firewall rules that must be enabled in order for remote connections to work: