> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/enterprise-guide/deploying-keeper-to-end-users/forcefield.md).

# Keeper Forcefield

Deploying the Forcefield endpoint protection software to users

The installation of the standalone version of Keeper Forcefield is available through an MSI installer based on the architecture.

#### x64 (64-bit Intel/AMD)

<https://download.keepersecurity.com/forcefield/x64/keeperforcefield.msi>

#### ARM64 (64-bit ARM)

<https://download.keepersecurity.com/forcefield/arm64/keeperforcefield.msi><br>

#### Automatic Deployment

Business customers can install the MSI on end-user machines using your preferred deployment method - Intune, a Remote Monitoring and Management (RMM) tool, or Group Policy. Each solution supports silent installation of MSI packages and can push the software to your target devices automatically. Just follow your standard process for deploying software across your environment.

#### Silent Installation / Uninstallation

Install:

```bash
msiexec.exe /i keeperforcefield.msi /quiet
```

Uninstall:

```bash
msiexec.exe /x keeperforcefield.msi /quiet
```

To log installation or uninstallation:

```bash
msiexec.exe /i keeperforcefield.msi /quiet /l*v install.log
```

[Learn more about Forcefield](/en/enterprise-guide/keeper-forcefield.md)


---

# 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://newdocs.keeper.io/en/enterprise-guide/deploying-keeper-to-end-users/forcefield.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.