> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/getting-started/installation.md).

# Installation

Installation is driven by a single script, `BFEWindowsLauncher_installationScript.ps1`, which:

1. Silently installs the MSI to `C:\Program Files\BlueFletch\BlueFletch Launcher\`.
2. Copies your configuration to `C:\ProgramData\BlueFletch\launcher.json` (if `-ConfigPath` is provided).
3. Configures the Windows shell for the chosen user setup mode (if `-UserSetup` is provided).
4. Sets up auto logon if required information is provided.

### Installation Script

```powershell
# Application + configuration + shell assignment + set auto logon
.\BFEWindowsLauncher_installationScript.ps1 -MSIPath "C:\path\to\BlueFletchLauncher-<VERSION>-x64.msi" `
  -ConfigPath "C:\path\to\launcher.json" -UserSetup '<USER_INSTALLATION_TYPE>' -Domain "<DOMAINNAME>" -Username "<USERNAME>" `
  -AutoLogonPath "C:\path\to\Autologon64.exe" -Password "<PASSWORD>"
```

| Parameter                      | Required              | Description                                                                                                                                                                                                                               |
| ------------------------------ | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `-MSIPath`                     | Yes                   | Full path to the Launcher MSI.                                                                                                                                                                                                            |
| `-ConfigPath`                  | No                    | Path to a JSON configuration file; script copies it to `C:\ProgramData\BlueFletch\launcher.json`                                                                                                                                          |
| `-UserSetup`                   | No                    | `KIOSK`, `LOCAL`, or `DOMAIN` — see the [Supported Windows Account Types](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/getting-started/installation/supported-windows-account-types). |
| `-Username` / `-Domain`        | With `LOCAL`/`DOMAIN` | The Windows account whose shell becomes the Launcher.                                                                                                                                                                                     |
| `-AutoLogonPath` / `-Password` | No                    | Path to `Autologon64.exe` and the account password, to enable Windows auto-logon.                                                                                                                                                         |

### Before running script

The script can be used as a reference for either [Local Installation](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/getting-started/installation/local-installation-guide) or MDM Deployment. The following sections provide steps for using the script in these separate MSI installation scenarios.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/getting-started/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 `automate deployments from our CI pipeline` 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.