--- title: Installing the Scheduler Windows service related: - https://docs.kentico.com/13/configuring-xperience/scheduling-tasks/scheduling-custom-tasks.md - https://docs.kentico.com/13/external-utilities/kentico-xperience-installation-manager.md - https://docs.kentico.com/13/external-utilities/kentico-xperience-service-manager.md --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). > **Info:** **Enterprise license required** > > Features described on this page require the **Kentico Xperience Enterprise** license. Xperience provides a dedicated Windows service for executing scheduled tasks. You can use the service to execute tasks externally outside of the live site or Xperience administration application (typically for resource-consuming tasks). ## Installing the Scheduler Windows service using Kentico Service Manager The easiest way to install the Scheduler Windows service is to use the Kentico Xperience Service Manager utility: 1. Launch the [Kentico Xperience Service Manager](https://docs.kentico.com/13/external-utilities/kentico-xperience-service-manager.md) utility from the Kentico program files group in the Windows Start menu. - You can also launch the **KSM** utility from [Kentico Xperience Installation Manager](https://docs.kentico.com/13/external-utilities/kentico-xperience-installation-manager.md) using the **Services** button. 2. Choose the Xperience instance where you want to install the service (select the CMS folder). 3. Select the **Kentico Scheduler** service. 4. Click **Install**. ![Installing the Xperience scheduler service](https://docs.kentico.com/docsassets/13/installing-the-scheduler-windows-service/Scheduler_Service_Install.png "Installing the Xperience scheduler service") 5. Click **Start** to start the service after it is installed. You have installed the **Kentico Scheduler** service, which is now running and ready to be used. You can uninstall the service at any time by clicking **Uninstall** in the Kentico Service Manager utility. ## Installing the Scheduler Windows service from the command line To install the Windows service from the command line, you need to use **Installer Tool** (InstallUtil.exe), which is a native part of the .NET Framework: 1. Open the Windows command line (type _cmd_ in the Start menu search box) 2. Navigate to the .NET folder containing _InstallUtil.exe_ (e.g. _c:\Windows\Microsoft.NET\Framework64\v4.0.30319\\_). 3. Execute _InstallUtil.exe_ from the Windows command line with the following parameters: ```powershell InstallUtil.exe /webpath="C:\inetpub\wwwroot\Kentico\CMS" "c:\inetpub\wwwroot\Kentico\CMS\bin\SchedulerService.exe" /LogToConsole=true /i ``` The following table describes the used parameters: | **/webpath** | Path to the CMS folder of the Xperience instance for which you want to install the service. | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **second parameter** | Path to the _SchedulerService.exe_ file in the _Bin_ folder inside the application (typically _c:\inetpub\wwwroot\Kentico\CMS\bin\SchedulerService.exe_). | | **/LogToConsole** | Optional parameter that determines whether the installation progress is logged to the console. | | **/i** | If this parameter is used, the Installer Tool performs installation of the Windows service. | 4. Open the **Services** management console (type _services.msc_ into the Start menu search box). 5. Select the **Kentico Scheduler ()** service in the list. 6. Click the **Start Service** button on the top toolbar. ## Configuring database permissions for services By default, Kentico Xperience services run under the **Local System** (_NT AUTHORITY\System_) account. If you experience problems with services not starting, the Local System account may not have sufficient permissions for your Xperience database. Either grant sufficient permissions for the _NT AUTHORITY\SYSTEM_ login in your database (at least assign a schema with the _Connect_ permission), or use the Windows **Services** management console to change the _Log on as_ account of individual services to a different account with database access. ## Configuring file permissions for search indexing If you plan to run scheduled tasks that perform updates on the file system of your live site or administration application, you need to give _Write_ permissions for the given folder to the account used by the Windows scheduler service (_Network Service_ by default). For example, if using [locally stored search indexes](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes.md) together with the _Execute local search tasks_ scheduled task. You can configure the account for services via the _Log on as_ property in the Windows **Services** management console. ## Uninstalling the Scheduler Windows service from the command line 1. Open the Windows command line (type _cmd_ in the Start menu search box). 2. Navigate to the .NET folder containing _InstallUtil.exe_ (e.g. _c:\Windows\Microsoft.NET\Framework64\v4.0.30319\\_). 3. Execute _InstallUtil.exe_ from the Windows command line with the following parameters: ```powershell InstallUtil /webpath="C:\inetpub\wwwroot\Kentico\CMS" "c:\inetpub\wwwroot\Kentico\CMS\bin\SchedulerService.exe" /LogToConsole=true /u ``` After executing this command, the Scheduler Windows service for the Xperience instance specified by the **/webpath** parameter is uninstalled.