> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Path for the Client Installation Folder

> Define a custom installation folder for the Syteca Windows Client - useful for endpoints with non-default Program Files paths, deployment via GPO with standardized install locations, or compliance scenarios requiring agents on specific volumes.

The **Custom Path for the Client Installation Folder** parameter defines where the Syteca Windows Client is installed, rather than using the default `<systemdisk>\Program Files\Ekran System\Ekran System` location. Configured **at install time** - during remote Client installation from the Management Tool, or during generation of the Client installation package.

<Note>
  **Applies to**: Windows Clients only. macOS and Linux Clients use OS-native package management (`.pkg`, `.rpm`, `.deb`) with their conventional install paths.
</Note>

## When to use it

| Scenario                               | Why a custom path                                                                                                   |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Non-default Program Files location** | Endpoints with non-standard `%ProgramFiles%` mapping (e.g. remapped to a non-C: drive).                             |
| **Standardized GPO deployment**        | Organization-wide standard for where third-party agents are installed (often a specific corporate-tools directory). |
| **Volume management**                  | Compliance scenarios requiring agents on a specific encrypted or audited volume.                                    |
| **Test/sandbox deployments**           | Install the Client in a non-standard location to keep it separate from production deployments on the same image.    |

## Supported environment variables

You can use Windows environment variables in the path definition. Common ones:

| Variable         | Resolves to                                                           |
| ---------------- | --------------------------------------------------------------------- |
| `%programfiles%` | `C:\Program Files` *(or `C:\Program Files (x86)` for 32-bit context)* |
| `%appdata%`      | `C:\Users\<user>\AppData\Roaming`                                     |
| `%temp%`         | `C:\Users\<user>\AppData\Local\Temp`                                  |

Other Windows environment variables (e.g. `%localappdata%`, `%systemdrive%`, `%programdata%`) are also supported as long as they resolve to a valid, writable path on the target endpoint.

## Fallback behavior

If the location you define is **not accessible** or is **write-protected**, the Client falls back to the default install path:

```text theme={"system"}
<systemdisk>\Program Files\Ekran System\Ekran System
```

## Where the parameter is set

This is an **install-time** parameter, configured during one of two procedures:

| Procedure                                                           | Where to set the custom path                                                                                                                                     |
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Remote Windows Client installation** *(from the Management Tool)* | Install dialog - Custom Path field. See [Install Windows Clients remotely](/docs/administration/clients/install-windows#remote-installation-via-the-management-tool). |
| **Generation of the Windows Client installation package**           | Package generation dialog. See [Generate Windows Client installation package](/docs/administration/clients/install-windows#generate-the-installation-package).        |

The Custom Path is **not changeable after install** without uninstalling and reinstalling the Client. If you need to move an installed Client, plan for the uninstall-reinstall cycle rather than expecting an in-place path change.

## Related

<CardGroup cols={2}>
  <Card title="Install Windows Clients" icon="laptop" href="/docs/administration/clients/install-windows">
    Per-OS installation procedures - where install-time parameters live.
  </Card>

  <Card title="Protected mode" icon="shield-check" href="/docs/administration/clients/parameters/protected-mode">
    Driver-level protection - interacts with install-time hardening choices.
  </Card>

  <Card title="Custom Client uninstallation key" icon="key" href="/docs/administration/clients/uninstall#the-client-uninstallation-key">
    Another install-time parameter for Windows Clients.
  </Card>

  <Card title="Windows Clients" icon="laptop" href="/docs/administration/clients/windows">
    Full Windows Client documentation.
  </Card>
</CardGroup>