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

# Support Installer

## Overview <a href="#overview" id="overview"></a>

Support Installer is designed to facilitate the proper App Usage permissions for Support Application. After installing the application, the Silent Init Activity needs to be invoked. Once the Support Tool Installer runs, it will install the Support Tool application via the Zebra EMDK, which will give all defined permissions to the Support Application.

### Invoking Silent Init Activity with ADB Command

To launch the Silent Init Activity using ADB, use the example below as a guide:

```json
adb shell am start -n com.bluefletch.ems.supportinstaller/com.bluefletch.ems.supportinstaller.SilentActivity
```

### Invoking Silent Init Activity with Airwatch Command

To launch the Silent Init Activity using AirWatch, use the example below as a guide:

```json
mode=explicit,action=android.action.intent.MAIN,package=com.bluefletch.ems.supportinstaller,class=com.bluefletch.ems.supportinstaller.SilentActivity,broadcast=false
```

{% hint style="info" %}
This installer currently supports Zebra devices only.
{% 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 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/support-application/support-installer.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.
