# Configure the Scheduling Services

The Test Studio Scheduling services work together to ensure the seamless communication between the project and machines, which execute the tests. Their configuration is related and, thus, performed in a single config wizard.

The below article describes the configuration steps.



* [Configure the Scheduling Services](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#configure-the-scheduling-services)
  * [Start the Test Studio Scheduling Config Wizard](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#start-the-test-studio-scheduling-config-wizard)
  * [Configure the Test Studio Services](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#configure-the-test-studio-services)
    * [Communication Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#communication-tab)
    * [Encryption Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#encryption-tab)
    * [MongoDB Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#mongodb-tab)
    * [Storage Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#storage-tab)
    * [Scheduling Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#scheduling-tab)
    * [Automatic Email Notification for Scheduled Executions](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#automatic-email-notification-for-scheduled-executions)
    * [Executive Dashboard Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#executive-dashboard-tab)
    * [Execution Server Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#execution-server-tab)
    * [Browsers Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#browsers-tab)
  * [Finish the Test Studio Services Configuration](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#finish-the-test-studio-services-configuration)

> **Important**
> <br>
> <br>
> The Test Studio Services must be configured from a Windows Administrator account.

## Start the Test Studio Scheduling Config Wizard

You can start the Scheduling config wizard in any of the following ways:

* The  wizard can be accessed through the Windows Start menu by typing *Configure Test Studio Services*.

  ![Configure scheduling setup wizard](https://www.telerik.com/teststudio/documentation/assets/41c4b9d01c6a47a305835b547c8918c8/fig2a.png)

* The **Configure Test Studio Services** can be accessed through the opened in Test Studio project - click **Configure** button under the *Project* tab in the *Scheduling* section.

  ![Configure](https://www.telerik.com/teststudio/documentation/assets/b49cdc14bec2d9cda936439851c0402b/fig2.png)

* Once Test Studio services get installed (no matter in which edition of the product), the installation wizard suggests to start the **Configure Test Studio Services** automatically.

  ![Start scheduling setup wizard after installation of services](https://www.telerik.com/teststudio/documentation/assets/481baabb513c11337a30199b45df082a/fig1.png)

## Configure the Test Studio Services

> **Important**
> <br>
> <br>
> If the machines have active firewall, ensure that the following ports are opened in both the inbound and outbound directions for all machines used in the configuration:
>
> * Scheduling Service: 8009
> * Storage Service: 8492
> * Execution Machine(s): 55555

There are a few tabs in the **Scheduling configuration wizard**, which provide the configuration details for each of the components of the Scheduling setup.

Go through each tab to setup the Test Studio services:



* [Communication Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#communication-tab)

* [Encryption Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#encryption-tab)

* [MongoDB Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#mongodb-tab)

* [Storage Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#storage-tab)

* [Scheduling Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#scheduling-tab)

* [Automatic Email for Scheduled Test Lists](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#automatic-email-for-scheduled-test-lists)

* [Executive Dashboard Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#executive-dashboard-tab)

* [Execution Server Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#execution-server-tab)

* [Browsers Tab](https://www.telerik.com/teststudio/documentation/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#browsers-tab)

### Communication Tab

The Communication tab lets you manage the **Communication Key** which is required by all Test Studio Scheduling components - services and clients. It is used to establish the connection and successful communication between each of the Scheduling modules.

![Communication tab](https://www.telerik.com/teststudio/documentation/assets/f4a4655b26c05ec7fbf58fa1dc4a9e9f/communication-tab.png)

The **Current Key** section indicates which is the key in use. The Scheduling setup is configured to use a default communication key for each Test Studio installation. Thus, after initial install you see the current key is the **Default Key Loaded**. In this configuration you can't copy or see the key.

![Default Communication key](https://www.telerik.com/teststudio/documentation/assets/995950d17cf35c6e2500f2550eab67e6/communication-tab-default-key.png)

> **Tip**
> <br>
> <br>
> We strongly recommend to generate a new custom communication key and replace it for all machines in the setup.
> <br>
> See <a href="/knowledge-base/scheduling-kb/generate-communication-key#generate-new-key" target="_blank">here step-by-step instructions on updating the communication key</a>.

Once a custom key is generated and imported, the **Current Key** section allows you to copy the value of the key using the **Copy to Clipboard** button, or see it using the **Show** button (for the cases when copying is not an option). The key value can be reset to the default value using the **Reset to Default** button.

![Custom Communication key](https://www.telerik.com/teststudio/documentation/assets/bcda29ae75ee796b5ddd8683e6061104/communication-tab-custom-key.png)

The **Replace Key** section lets you **Generate** a new key. Once generated, the new value is populated in the text field and is ready to be imported. Hit the **Import** button to replace the current key with the new one.

![Replace Communication key](https://www.telerik.com/teststudio/documentation/assets/bab8136a2aa8c7ec422d30a5e894af82/communication-tab-replace-key.png)

> **Note**
> <br>
> <br>
> Importing a new key in the Scheduling Config wizard **restarts the Scheduling service on that same machine to apply the new value**.
> <br>
> <br>
> The Execution Client application is stopped but you need to start it manually.
> If Test Studio application is also running on the same machine at the time of renewing the communication key, it is not automatically restarted. To apply the recent changes you **need to restart the standalone Test Studio app manually**.
> <br>
> <br>
> See <a href="/knowledge-base/scheduling-kb/generate-communication-key#generate-new-key" target="_blank">here step-by-step instructions on updating the communication key</a>.

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Encryption Tab

The Encryption tab lets you manage the **Encryption Key** which is used to secure sensitive data across the Test Studio projects including:

* Passwords for connecting to source control repository or bug tracking systems, and database connection strings used in data driven tests; SMTP credentials if used in the Scheduling configuration;
* Password steps recorded in automated tests when the *'Encrypt'* step property is enabled.

> **Note**
> <br>
> <br>
> The same **encryption key must be imported on all machines** where Test Studio product is in use. This is **mandatory** to ensure encrypted data remains accessible and test execution is not disrupted.

![Encryption tab](https://www.telerik.com/teststudio/documentation/assets/baf34cb895677dd9655097a0aaf51403/encryption-tab.png)

The **Current Key** section indicates which is the key in use. Test Studio installation uses a default encryption key and you see the current key is the **Default Key Loaded**. In this configuration you can't copy or see the key.

![Default Encryption key](https://www.telerik.com/teststudio/documentation/assets/197e8099f37ede58ec8abddaa7d9ba52/encryption-default-key.png)

> **Tip**
> <br>
> <br>
> We **strongly recommend to generate a new encryption key** and replace it for all machines in the setup.
> <br>
> See <a href="/knowledge-base/project-configuration-kb/generate-encryption-key" target="_blank">here step-by-step instructions on updating the communication key</a>.

Once a custom key is generated and imported, the **Current Key** section allows you to copy the value of the key using the **Copy to Clipboard** button, or see it using the **Show** button (for the cases when copying is not an option).

![Custom Encryption key](https://www.telerik.com/teststudio/documentation/assets/d778c12177f2cd2c6c03d74bf53bdef2/encryption-custom-key.png)

The **Replace Key** section lets you **Generate** a new key. Once generated, the new value is populated in the text field and is ready to be imported. Hit the **Import** button to replace the current key with the new one.

![Replace Encryption key](https://www.telerik.com/teststudio/documentation/assets/8ec90859043840afd0b8d41941e5b89c/encryption-generate-key.png)

> **Note**
> <br>
> <br>
> When **importing a custom encryption key for the first time** some of the encrypted data becomes inaccessible. To **continue using your Test Studio projects in such case you must**:
>
> * **re-enter all passwords** for connecting to source control repository or bug tracking systems, and SMTP settings if used in Scheduling configuration;
> * all projects on the machine are upgraded to use the new key for password steps in automated tests when the *'Encrypt'* step property is enabled and for database connection strings used in data driven tests - **no further interaction is needed** for these.

> If you decide to **regenerate the encryption key and import a new one** all encrypted data becomes inaccessible. To **continue using your Test Studio projects in such case you must**:
>
> * **re-enter all passwords** for connecting to source control repository or bug tracking systems, and database connection strings used in data driven tests, and SMTP settings if used in Scheduling configuration;
> * **re-record all password steps** in automated tests when the *'Encrypt'* step property is enabled.

> See <a href="/knowledge-base/project-configuration-kb/generate-encryption-key" target="_blank">here step-by-step instructions on updating the encryption key</a>.

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### MongoDB Tab

The **MongoDB** tab contains the details required for the MongoDB database, which is used as a storage database in the Scheduling configuration.

The **MongoDB data path** and **mongod.exe path** fields are populated with the values for a default MongoDB installation, so you need to change these, **only if the MongoDB installation was modified**.

Hit the **Apply** button and confirm the *'MongoDB is running'* status appears in the lower left corner of the wizard.

![MongoDB](https://www.telerik.com/teststudio/documentation/assets/ab1918c2c7c4c832351b4a13794676e8/fig2new.png)

> **Note**
> <br>
> <br>
> The **MongoDB** tab is grayed out (inactive) if you do not have MongoDB installed on the machine! This gets enabled when the correct **Storage Service Location** is set in the **Scheduling** tab.

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Storage Tab

The **Storage** tab displays the connection details used from Test Studio Storage Service to access the MongoDB. The listed **MongoDB connection string** is the default connection string to be used for MongoDB database and is the only valid connection option for the Storage service.

Hit the **Apply** button and check the *'Telerik Storage Service is started'* status appears in the lower left corner of the wizard.

![Storage](https://www.telerik.com/teststudio/documentation/assets/1c0adfacd7c713b9bffe54762c5e8958/fig3new.png)

> **Note**
> <br>
> <br>
> The **Test Studio Storage Service and MongoDB** require to be installed on the same machine.

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Scheduling Tab

The **Scheduling** tab provides information about the location of the **Test Studio Storage and Scheduling services**. The default populated values point to the local machine - *'localhost'*.

Hit the **Apply** button and check the *'Telerik Scheduling Service is running'* status appears in the lower left corner of the wizard. Once started, the Scheduling service also shows details about the connected Storage service's status and database version in the **Storage Service Location** section.

![Scheduling](https://www.telerik.com/teststudio/documentation/assets/195898c2185edfa95534aa8ffec6c9f6/fig5new.png)

> **Note**
> <br>
> <br>
> If the Test Studio services are hosted on different machines, you can enter the respective machine name or IP to configure these.

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Automatic Email Notification for Scheduled Executions

Optionally, the **Test Studio Scheduling service can be configured to use an Email (SMTP) server** by specifying the email server connection details. By adding these settings you will be able to <a href="/features/scheduling-test-runs/schedule-execution#step-3" target="_blank">send an automatic email</a> with the results of a scheduled test list.

The SMTP server settings are listed in the expandable section **Configure Email (SMTP) server** in the **Scheduling** tab. Mandatory fields are the **'SMTP server address'** and the **'Port'** to communicate with it, and the **'User Email'**, who sends the email. Depending on the SMTP server configuration, the **'Password'** field and **'Ssl'** checkbox may not be explicitly required.

Once the necessary data is entered, hit the **Apply** button to reflect the changes to the Scheduling service and check if the status *'Telerik Scheduling Service is running'* appears in the lower left corner of the wizard.

![Scheduling SMTP](https://www.telerik.com/teststudio/documentation/assets/46089180b8858b149b41364514dda294/fig5a.png)

> **Note**
> <br>
> <br>
> If you are using an Outlook account with two-factor authentication enabled, you need to use an **Application password** created for the SMTP configuration. See the response in <a href="https://learn.microsoft.com/en-us/answers/questions/602284/sending-email-with-smtp-while-two-factor-enable" target="_blank">this Microsoft forum post</a> for further details.

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Executive Dashboard Tab

The **Executive Dashboard** tab provides information about the **Storage Service Location** from which the <a href="/general-information/test-results/executive-dashboard" target="_blank">Dashboard</a> takes results. The default populated value points to the local machine - *'localhost'*. If the Test Studio services are hosted on different machines, you can enter the respective machine name or IP where the Storage service is running.

The **Executive Dashboard** section of the tab allows changing the port on which the locally hosted Dashboard page runs. From the hyperlink in this section you can load the Dashboard page in your default set browser.

Hit the **Apply** button and check the *'Telerik Scheduling Service is running'* status appears in the lower left corner of the wizard.

![Executive dashboard](https://www.telerik.com/teststudio/documentation/assets/058d6d49d9ca1ca57d0327ccc2da2c23/fig4new.png)

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Execution Server Tab

The **Execution Server** tab contains information for the configuration settings of the Execution client application on the current machine. In this tab you can change the Scheduling URL to which the Execution client is connected, the port and temp folder it uses, and whether to run it on startup.

The default populated values point to the local machine Scheduling service - *localhost* using the port 55555. Hit the **Apply** button to apply any changes - wait until you see a message in the lower left corner of the wizard stating *'Changes applied successfully'*.

![Execution Server config tab](https://www.telerik.com/teststudio/documentation/assets/ec1950499ebeef518789658397a39090/execution-client-tab.png)

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Browsers Tab

When available, the **Browser support update** notification appears along with the **Update** button and indicates that you must update Test Studio.

![Browser Update available](https://www.telerik.com/teststudio/documentation/assets/bb14c1be9364b9ebc169c252b826c9b2/browsers-tab-update-aval.png)

Hit the **Update** button to trigger the update. After the update, **restart Test Studio** for the changes to take effect.

![Restart required](https://www.telerik.com/teststudio/documentation/assets/1d379c451c38f12c8dd434c87817c30f/browsers-tab-restart-after-update.png)

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

### Browsers Tab

When available, the **Browser support update** notification appears along with the **Update** button and indicates that you must update Test Studio.

![Browser Update available](https://www.telerik.com/teststudio/documentation/assets/bb14c1be9364b9ebc169c252b826c9b2/browsers-tab-update-aval.png)

Hit the **Update** button to trigger the update. After the update, **restart Test Studio** for the changes to take effect.

![Restart required](https://www.telerik.com/teststudio/documentation/assets/1d379c451c38f12c8dd434c87817c30f/browsers-tab-restart-after-update.png)

<br>
<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
<br>

## Finish the Test Studio Services Configuration

When all necessary settings are applied and all services are reported running, close the wizard window to finish the Scheduling Services setup.

## See Also

* <a href="https://www.telerik.com/blogs/test-studio-step-by-step-running-tests-remotely" target="_blank">Test Studio Step-by-Step: Running Tests Remotely</a>
