> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/3.1/setup/installation/stifler-beacon-installation.md).

# StifleR Beacon installation

For more information about what a Beacon Server is and does, see the [Beacons Page](/stifler/3.1/operations-and-features/beacons.md).

## Prerequisites

| Requirement                | Detail                                                         |
| -------------------------- | -------------------------------------------------------------- |
| Operating system           | Windows Server 2016 or newer; Windows 10 version 1607 or newer |
| Runtime                    | Microsoft .NET 8                                               |
| Network — inbound TCP 5201 | iPerf3 bandwidth measurement port                              |
| Network — inbound TCP 5200 | FastPing latency check port                                    |
| Credentials                | Local administrator                                            |
| StifleR Server             | Must be running and reachable before the beacon can register   |

Both ports must be reachable from the subnets whose clients will be measured. If you\
use Windows Firewall, the installer creates the required rules automatically. For\
third-party firewalls, open TCP 5200 and TCP 5201 inbound.

> **iPerf3 is included.** The beacon installer ships iPerf3 as part of the installation.\
> You do not need to install iPerf3 separately on the beacon, nor on client machines —\
> the StifleR Client agent ships its own copy.

***

## Installation Steps

1. Download the beacon installer (`StifleR.Beacon.x64.msi`) from 2Pint Software.
2. Run the installer from an elevated command prompt or right-click → **Run as**\
      **administrator**.
3. Accept the license agreement and choose a destination folder (default is\
      `C:\Program Files\2Pint Software\StifleR Beacon`).
4. Click **Install**. The installer registers the beacon as a Windows service\
      and starts it.
5. After installation completes, open the **StifleR Beacon Config Editor** from the\
      Start menu or the installation directory.
6. Set **StifleR Server** (under **Infrastructure**) to the URL of your StifleR\
      Server API, for example `https://stifler.contoso.com:9000/`.
7. Click **Save** and restart the beacon service.

***

## Post-Installation: Approving the Beacon

The beacon registers with the StifleR Server automatically on startup. It will not\
be used for measurements until it has been approved.

1. Open the StifleR Dashboard.
2. Navigate to **Administration → Infrastructure Services**.
3. Find the newly registered beacon (it will show **Pending** status).
4. Click the beacon entry and select **Approve**.

Once approved, the beacon appears on the **Beacons** page and is available for\
assignment to network groups, locations, or areas.

***

## Verifying the Installation

After approval, confirm the beacon is healthy:

* The **Beacons** page shows the beacon with an **Online** status indicator. A beacon\
    is considered online if it has sent a heartbeat within the last 30 seconds (default\
    threshold; configurable in the server settings).
* The **Infrastructure Services** page shows the beacon version and last heartbeat\
    time.

If the beacon shows as offline immediately after approval, verify that the StifleR\
Server URL is correctly configured in the Config Editor and that the service has been\
restarted after the change.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/3.1/setup/installation/stifler-beacon-installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.