> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/operations/clients/windows-installation.md).

# Windows App Installation

How to install the PASCOM app on Windows and on the terminal server

The Windows installation process does not require any admin privileges and be performed directly in the home-directory of the currently logged in user:

1. Download the [Windows App](https://my.pascom.net/update/client/cloud/windows)
2. Run the **pascom-client-setup.exe**
3. Follow the install guide

### Windows Silent Installation

A silent installation is an installation method for software where no user interaction is required and no graphical user interface is displayed. With a silent installation, all necessary installation parameters are set in advance and the installation runs in the background without the user having to confirm or select anything. You can customise the target of the installation package via the properties or start the installation package via the command line.

```
pascom-installer.exe /S
```

A shortcut for the PASCOM app is also automatically created on the desktop.

**Setting the autostart behaviour**

To simultaneously adjust the autostart behaviour of the PASCOM app during installation, you can use the following command line parameter.

```
AUTOSTART="yes"
```

**Silent Uninstallation**

Proceed in the same way as for the installation. You will find the uninstaller in the app directory of the PASCOM app.

```
uninst.exe /S
```

### Windows QoS Settings (Optional)

In order to achieve the maximum voice quality, the PASCOM App marks all voice data accordingly with QoS flags.

With the exception of Windows, this happens automatically on all other platforms.

The following group policies "**Policy-based QoS**" are required under Windows to mark the packages accordingly.

The group policies are created under the following path:

```bash
Local Computer Policy > Computer Configuration 
> Windows Settings > Policy-based QoS
```

|                    | Policy 1          | Policy 2          | Policy 3          |
| ------------------ | ----------------- | ----------------- | ----------------- |
| *Policy Name*      | pascomSIP         | pascomRTP         | PASCOM WebSocket  |
| *Application Name* | pascom Client.exe | pascom Client.exe | PASCOM Client.exe |
| *Protocoll*        | TCP and UDP       | UDP               | TCP               |
| *Source Port*      | \*                | \*                | \*                |
| *Destination Port* | 5060:5062         | 30000:35000       | 443               |
| *Source-IP*        | \*                | \*                | \*                |
| *Destination-IP*   | \*                | \*                | \*                |
| *DSCP Value*       | 24                | 46                | 24                |
| *Throttle Rate*    | -1                | -1                | -1                |

## Terminalserver Installation

(Optional) On the Microsoft Terminal Server it is possible to install the PASCOM desktop App directly in the programmes directory instead of the corresponding user's home directory.

The disadvantage of this type of installation is that you will need to manually perform all PASCOM desktop App updates, as the updates require admin rights. The advantage of terminal server installations is that you can save upto ca. 100MB storage space per user.

1. Download the [Windows Desktop App](https://my.pascom.net/update/client/cloud/windows)
2. Open the command prompt as an Administrator
3. Start the setup and specify the install directory

Example

```
pascomClient-setup.exe /D=C:\Program Files\pascom Client
```

{% hint style="warning" %}
The automatic updates of the PASCOM App are only deactivated if the PASCOM App has no **write permissions**. This is the default behaviour if you use the **example path**. Otherwise, it may happen that auto-updates are activated and you have to deactivate them again via **flags** or **environment variables**.
{% endhint %}

## Windows Installer Command Line Parameters

| Parameter | Explanations                                                                                                                                                          |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| /S        | Enables an installation in to run in the background, without displaying any dialog windows.                                                                           |
| /D=PATH   | Enables the defining of the installation folder, i.e path. This parameter must always be the last parameter in the command line and only supports absolute file paths |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/operations/clients/windows-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.