> 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/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process/printer-installation.md).

# Printer Installation

### Introduction

This topic describes how to install the printer.

### Before you begin

To view a list of supported printer integrations, view the [Gallagher Security website](http://security.gallagher.com/products/card-printers/) or contact Gallagher Technical Support.

**Note:** The printer integration may not support the latest printer and encoder drivers. Confirm the supported printer and encoder drivers with Gallagher Technical Support prior to installation.

### Procedure

To install the printer, perform the following procedure:

1. Install the printer driver (provided by the printer manufacturer) on all Command Centre workstations that will be using the printer.

   **Note:** Some printer models may require you to connect the printer during the printer driver installation.
2. Install the encoder driver (provided by the printer manufacturer) on all Command Centre workstations that will be using the printer.

   **Note:** Printers using the SCM encoder module will need to install the MIFARE Encoder Driver on all Command Centre workstations that will be using the printer. Refer to the document *"3E0774 Install Note MIFARE Encoder.pdf"* for installation instructions. This document and the MIFARE Encoder Drivers are located in the `Utilities/MIFARE Encoder Drivers` folder of the Command Centre installation files.
3. Restart the Command Centre workstations after installing the printer and encoder drivers.


---

# 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/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process/printer-installation.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.
