> 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/support-console.md).

# Support Console

The Support Console is an on-device troubleshooting overlay for store associates and technicians. It surfaces device health and quick-recovery actions without requiring administrative access or a remote support session.

This page covers what the panel shows and how each section is driven by configuration. For the full field reference, see [Technical Guide → emsSupportTool](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/technical-guide#emssupporttool).

### Opening the Panel <a href="#opening-the-panel" id="opening-the-panel"></a>

A **System Information** icon sits in the taskbar next to the clock. Clicking it toggles a popup anchored to the bottom-right of the screen; clicking outside the popup, or the icon again, closes it.

### Sections <a href="#sections" id="sections"></a>

The panel renders up to four sections, top to bottom. A section is omitted entirely if it has nothing configured to show.

#### 1. Help <a href="#id-1-help" id="id-1-help"></a>

Rendered only when `emsSupportTool.helpInfo.entries` has at least one entry. Each entry renders one of two ways:

* **`{ "label", "value" }`** — a static display row (e.g. a phone number or site code).
* **`{ "label", "url" }`** — a clickable link that opens in the device's default browser.

The section heading comes from `helpInfo.helpLabel` (default `"Help"`).

#### 2. Services & Processes <a href="#id-2-services--processes" id="id-2-services--processes"></a>

Rendered only when at least one configured service or process returns a status. The section heading comes from `systemMonitoring.servicesLabel` (default `"Services & Processes"`).

Each monitored **service** shows its Windows display name and a colored status (`Running` in green; `Stopped`/`Paused`/other in red or gray). A **Restart** button appears whenever the status is `Stopped` or `Paused`:

* If the service entry has a `restart` path, that script/executable/shortcut runs.
* Otherwise, a built-in PowerShell script restarts the Windows service directly by its service name.

Each monitored **process** shows its configured name and status (`Running` / `NotRunning`). Unlike services, a process's Restart button appears **only when** the process is `Stopped` **and** a `restart` path is configured — there's no generic way to relaunch an arbitrary process without knowing how to start it, so processes have no built-in fallback.

After any successful restart, both lists refresh immediately so the new status is visible right away.

#### 3. Network Info <a href="#id-3-network-info" id="id-3-network-info"></a>

Always rendered (shows a "No network information available" message if empty). One card per network adapter, showing **Connection Type**, **IP Address**, and **MAC Address**.

#### 4. Computer Info <a href="#id-4-computer-info" id="id-4-computer-info"></a>

Always rendered (shows a failure message if the underlying script didn't return data). Shows **Name**, **Manufacturer**, **Model**, **Serial**, and **Uptime**.

### Configuring Its Content <a href="#configuring-its-content" id="configuring-its-content"></a>

Everything except Network Info and Computer Info (which are always gathered automatically) is driven by the `emsSupportTool` block in `launcher.json`:

| Key                              | Description                                                                                                                                                                                                                  |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `helpInfo.helpLabel`             | Heading text for the Help section.                                                                                                                                                                                           |
| `helpInfo.entries`               | Array of `{ label, value }` or `{ label, url }` entries — see [Help](https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/Lesly/Documents/repos/bfe-windows-authentication-agent/docs/system-info-panel.md#1-help) above. |
| `systemMonitoring.servicesLabel` | Heading text for the Services & Processes section.                                                                                                                                                                           |
| `systemMonitoring.services`      | Array of `{ name, restart? }`. `name` must be the Windows **service name**, not its display name (e.g. `wuauserv`, not "Windows Update").                                                                                    |
| `systemMonitoring.processes`     | Array of `{ name, restart? }`. `name` is the process image name without `.exe`. A `restart` path is required for the Restart button to appear.                                                                               |

```json
"emsSupportTool": {
  "orgId": "<YOUR-ORG-ID>",
  "eventUrl": "https://ems-services-api.bluefletch.com/eventsAPI/apiv1/event",
  "systemMonitoring": {
    "servicesLabel": "POS Components",
    "services": [
      { "name": "wuauserv" },
      { "name": "EventLog", "restart": "C:\\ProgramData\\BlueFletch\\scripts\\restart_eventlog.ps1" }
    ],
    "processes": [
      { "name": "chrome", "restart": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe" },
      { "name": "notepad" }
    ]
  },
  "helpInfo": {
    "helpLabel": "Service Desk",
    "entries": [
      { "label": "Desk Phone", "value": "555-1234" },
      { "label": "Submit a Ticket", "url": "https://support.example.com/submit" }
    ]
  }
}
```

In this example, `notepad` is monitored (its status shows in the panel) but has **no** Restart button, since it has no `restart` path configured.

{% hint style="info" %}
`orgId` and `eventUrl` are mandatory on `emsSupportTool` even if you don't use `systemMonitoring` or `helpInfo` — they're also used for EMS login/logout event reporting and Central Auth. See [Configuration Structure → emsSupportTool](https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/Lesly/Documents/repos/bfe-windows-authentication-agent/docs/configuration-structure.md#emssupporttool).
{% endhint %}


---

# 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://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/support-console.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.