# Installing Sherpa Coordinator on Windows

Before installing the Sherpa RPA Coordinator, you need to add a "Coordinator" type Robot on the "Robots" screen in the Orchestrator. More details about adding a Robot can be found here:

{% embed url="<https://docs.sherparpa.ru/sherpa-orchestrator/rabota-v-sherpa-orchestrator/nachalo-raboty-v-sherpa-orchestrator/dobavlenie-robota-v-orkestratore>" %}

The distribution [SherpaRPACoordinator.exe](https://sherparpa.ru/downloads/SherpaRPACoordinator.exe) is installed under an administrator account and subsequently runs as a service under the System account.

The Robot, regardless of the installation method (with Designer or without), can have the following Role:

* Attended,
* Unattended.

This is determined by its License:

* local,
* obtained from the Orchestrator.

As well as the launch method (locally or through the Orchestrator).

The operation principle of the Coordinator is described here:

{% embed url="<https://docs.sherparpa.ru/sherpa-orchestrator/rabota-v-sherpa-orchestrator/nachalo-raboty-v-sherpa-orchestrator/principy-raboty-raznykh-tipov-robotov-v-orkestratore>" %}

The program installation is performed by the installer launched by the SherpaRPACoordinator.exe file. Save this file to your computer and run it. In the opened window, click the "Next" button.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-6288795b6b3d511f53911052a2d93d706cf988df%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(440).png?alt=media" alt=""><figcaption></figcaption></figure>

Then fill in the following fields:

* Orchestrator. Server domain / IP;
* Orchestrator. Coordinator GUID.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-b17d7657123e063f4660cb814e7069d859bba0db%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(441).png?alt=media" alt=""><figcaption></figcaption></figure>

> The Coordinator GUID must be copied from the Robot card. To do this, open the Robots screen in the Orchestrator. Then open the Robot card and copy the GUID.

Next, you need to check the connection. To do this, click the button ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-46516ab8368bc68696c4fde52582058489a95624%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20\(443\).png?alt=media) in the Coordinator installation window.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-b48caa7796f4ff41c3ca53a398426720473ca33d%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(442).png?alt=media" alt=""><figcaption></figcaption></figure>

If necessary, you can use the additional settings of the Coordinator (using the button ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-9d9cbd91da22dd6f24e18a1ef2b74b8d1ba27735%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20\(445\).png?alt=media)).

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-b1244ca9874efa646d871fa23034f9258976bcfe%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(444).png?alt=media" alt=""><figcaption></figcaption></figure>

The additional setting "Reset hung sessions after:" allows you to configure the frequency of resetting hung RDP sessions. This functionality works if the Robot has completed the Work, initiated the exit from the RDP session, and closed itself, but the operating system did not allow the session to end, for example, due to updates being installed or another program.

In this case, the Coordinator forcibly terminates the RDP session process and restarts it. The principle of operation of this functionality is as follows: when the Robot is running, it sends a message to the Orchestrator every 15 seconds. When a new Work appears for this Robot, a command to start and the time of this last Robot message is sent to the Coordinator. If the time exceeds the specified limit, the Coordinator resets the current session and starts a new one.

You can also configure the proxy (using the button ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-ca7e7c4d7cfeda4ebc9255c1f40659a549f9d280%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20\(446\).png?alt=media)).

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-604f830d79d140feb693904426b3f9f98f156d2e%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(447).png?alt=media" alt=""><figcaption></figcaption></figure>

During installation, you can choose one of two methods for creating an RDP connection:

* FreeRDP - this method is based on the open-source program "FreeRDP". When using this method, minimal system requirements are involved for initializing the connection;
* MS RDP - this method uses the standard connection method built into Windows. It is more resource-demanding but also more stable.

After configuring the additional parameters of the Coordinator, click the "Next" button. The installation process will begin:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-1a9c12b1ae2ee96735f9103f449c3c3d94558009%2F2%20(2).png?alt=media" alt=""><figcaption></figcaption></figure>

After that, you will see a window saying "The program has been successfully installed on your computer!".

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-924bc33755cd0df184a047971b6be54913a23d4b%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(448).png?alt=media" alt=""><figcaption></figcaption></figure>

After the installation of the Coordinator is complete, the “Sherpa RPA Service” is started. To check for the presence of the “Sherpa RPA Service,” you need to go to the “Services” of the computer.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-74f6518098fbd8f24e6458fa8ccb2088c2725da2%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(449).png?alt=media" alt=""><figcaption></figcaption></figure>

When checking for the Sherpa RPA Service in the service registry, it is visible that it is installed and is in the "Running" state.

In the properties settings of the “Sherpa RPA Service,” there is an option to select the “Startup type” (General tab). For convenience, the startup type can be set to “Automatic (Delayed Start)”:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-ebda545024279cf2a3ecbabd7ac1112d90bd1dea%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(450).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/razvertyvanie-platformy-pod-upravleniem-orkestratora/ustanovka-sherpa-rpa-coordinator/ustanovka-sherpa-rpa-coordinator-na-windows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.