> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/installing-encoder-3.md).

# Install Encoder 3

Install Encoder 3, apply the initialization file, and complete its first-run configuration.

How to install Encoder 3 and get through the first run: the activation password, the Facility Codes in the ini file, and the default login.

{% hint style="info" %}
Check [Supported Operating systems and requirements](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/supported-operating-systems-and-requir.md) first. Encoder 3 needs a Parallel or USB security dongle, and the MIFARE encoders it drives are discontinued.
{% endhint %}

{% hint style="warning" %}
Windows 11 does not support the MIFARE encoder drivers for the SDI110 and SDI011 encoders.
{% endhint %}

### Install Encoder 3

1. Contact Technical Support for a link to download the installer.
2. Follow the instructions in the downloaded folders. A detailed guide is included with the install files.
3. Ensure you have a valid `Encoder3.ini` file and the appropriate activation password.
4. When you run Encoder 3 for the first time, it will ask for the activation password.

![Encoder III activation password entry](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-316022ec10c439217c2bc7f9625331c6fea9ac87%2FSECHUB-ENCODING-ENC3-INSTALL-04-activation-password-prompt.jpg?alt=media)

5. It will ask for a site name for the Facility Codes listed in the `Encoder3.ini` file.

![Encoder III naming facility codes](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-8f71ecdfad3e544d72e81410674d593769fbe3d8%2FSECHUB-ENCODING-ENC3-INSTALL-07-name-facility-codes.jpg?alt=media)

6. Select the card technology to assign to the Facility Codes. This can be changed later.
7. Default first-time login: User = `master`, Password = `master`. You will be immediately prompted to change the password.

![Encoder III change password dialog](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-370755d55d46655b667b9fe45a33615b18fefd11%2FSECHUB-ENCODING-ENC3-INSTALL-05-change-password-dialog.jpg?alt=media)

{% hint style="warning" %}
Remember the new password. There is no way to recover it.
{% endhint %}

8. Follow the instructions in the Help PDF file to configure hardware and operators. The Help file also explains how to add new Facility Codes to the system, by adding an ini file.

***

🔗 **Related**

* [Supported Operating systems and requirements](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/supported-operating-systems-and-requir.md). The dongle, the operating systems, and the encoding devices.
* [Frequently Asked Questions](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/frequently-asked-questions.md). Forgotten passwords, moving the database, and adding a Facility Code with a new ini file.
* [Encoder 3 Overview](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/encoder-3-overview.md). What Encoder 3 is for and what to use instead.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/installing-encoder-3.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.