> 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/piv-card-support/installing-the-necessary-applications-tools-for-a-pivclass-workstation.md).

# Installing the necessary applications/tools for a pivCLASS Workstation

### Introduction

PIV cards can be enrolled for FIPS201 using either:

* **Command Centre Client** (the preferred method)

  Refer to the "PIV Cardholder Registration Process" in the **Gallagher Command Centre Client User Guide** for detailed instructions for this method.

  OR
* **a pivCLASS Workstation** (covered in this topic)

  The following applications/tools all need to be installed before PIV cards can be enrolled for FIPS201 using a pivCLASS Workstation:

  * **pivCLASS PACS Plug-in for Command Centre** (to be installed on the Gallagher Command Centre Server)
  * **pivCLASS Workstation** (to be installed on the workstation - either server or remote)
  * **Gallagher Command Centre Import/Export Service**
  * **CCFT Data Manager** (configure only as this is installed with the Import/Export Service)

    **Note:** The pivCLASS PACS Plug-in must be restarted whenever a change is made to CCFT Data Manager.

pivCLASS Workstation captures the PIV data when PIV cards are enrolled, and the pivCLASS PACS Plug-in passes them to Gallagher Command Centre using the Gallagher Command Centre Import/Export Service.

**Note:** If your site is using supported Morpho (Sagem) contact card PIV encoders, you will need to install (or upgrade) their drivers to version MorphoSmart\_USB\_Driver\_3\_59\_1\_3, located in the `'Utilities\Morpho\Device Drivers\MorphoSmart'` folder of the Command Centre installation files.

### Pre-requisites in Command Centre

Before proceeding with this procedure, ensure the following pre-requisites have been configured in Command Centre:

* Add a "CardholderId" text unique PDF which holds the FASC-N.
* Add a "Photo" PDF.
* If needed, create a default Access Group for PIV cardholders to be assigned on enrolment.
* Add the two PDFs created above to the default PIV Access Group.
* Add the "CardholderId" PDF as the Third Party ID on the **Import** tab of the Server Properties.
* Create an operator for pivCLASS to use for enrolment, and give them the "Edit Cardholder", "Edit Cardholder Notes" and "Modify Access Control" privileges.

### Procedure

Use the following procedure to install and configure all the applications/tools required for enrolling PIV cards for FIPS201.

**Note:** All User Manuals referred to in this procedure are located in the `'PIV Solution'` directory of the Gallagher Command Centre installation files.

#### Installing pivCLASS PACS Plug-in

1. Run the **pivCLASSPACSServiceCommandCentre-1.2.xxx.0.msi** file, located in the `'PIV Solution'` directory of the Gallagher Command Centre installation files.

   The Welcome screen of the pivCLASS PACS Service plug-in wizard displays.
2. Work your way through the wizard. When you reach the 'Completion' screen, click the **Finish** button.

   Refer to the "Installing the PACS Service" topic in Chapter 3 of the **PACS Service User Manual** for a detailed procedure.

   The pivCLASS PACS Plug-in is installed.

   **Note:** It installs to the default location `'C:\Program Files\HID Global\pivCLASS PACS Service'`, or another location if you opted to change it on the 'Destination Folder' screen of the wizard. A pivCLASS PACS Plug-in desktop shortcut may also have been selected during the install.
3. Configure the pivCLASS PACS Plug-in, by completing the "Configuring the PACS Database Parameters" procedure on page 16 of the **Command Centre Plugin User Manual**.

   **Notes:**

   * Use the default user name and password, "admin" and "password" on the Login screen.
   * Use the operator already created (as a prerequisite above) for **Username** and **Password**.
   * The **Server name** can be "localhost" if Command Centre is installed on the same server.
   * Both **Test** buttons need to be clicked to enable the **Accept** button.
   * The "Database Connection Parameters" section can be ignored.
   * Browse the Product path and select the correct path for your installation of Command Centre.
4. In the XML template file, change the Access Groups section to reflect the default PIV Access Group chosen/created (as part of the Prerequisites above), as follows:
   1. Open the **template.xml** file, usually located in `'C:\Program Files (x86)\HID Global\pivCLASS PACS Service\templates'` in a text editor.
   2. Scroll down to the Access Groups item:

      \<item>

      \<card>Access Group 1\</card>

      \<pacs>AccessGroup.1\</pacs>

      \</item>
   3. Modify the " \<card>Access Group 1\</card>" section to reflect the name of the Access Group you want the cardholders assigned when they are enrolled.
   4. Save the modified **template.xml** file.

#### Installing pivCLASS Workstation

5. Run the **pivCLASSWorkstation-1.2.xxx.0.msi** file, located in the `'PIV Solution'` directory of the Gallagher Command Centre installation files.

   The Welcome screen of the pivCLASS Workstation Setup wizard displays.
6. Work your way through the wizard. Once you reach the 'Completion' screen, click the **Finish** button.

   Refer to the "Installation" topic in Chapter 5 of the **pivCLASS Registration Workstation Use Manual** for a detailed procedure.

   pivCLASS Workstation is installed.
7. Login to pivCLASS Workstation and license it.

   Refer to "Chapter 5-13: Logging In and Licensing pivCLASS" of the **pivCLASS Registration Workstation Use Manual** for a detailed procedure.

   **Notes:**

   * Once the software is deployed at the customer site, the technician must send the system ID to **<ordersamer@hidglobal.com>**.

     Once pivCLASS receive this information, they will return a licensing key with licensing to match what was purchased via the GGL purchase order.
   * Use the default user name and password, "admin" and "password" on the Login screen.
8. Configure pivCLASS Workstation as appropriate.

   Refer to "Chapter 6: Configuring pivCLASS" of the **pivCLASS Registration Workstation Use Manual** for a detailed procedure.
9. Complete the "Client Authentication" section on pages 40 - 42 of the **pivCLASS Registration Workstation Use Manual**, to add the pivCLASS Workstation client to the pivCLASS PACS Plug-in.
10. Complete the installation and configuration of your selected Smart Card Reader that will be used for enrolment of cardholders via pivCLASS. Refer to the "Peripheral Setup" section in Chapter 4 of the **pivCLASS Registration Workstation Use Manual** for a detailed procedure.

#### Installing the Gallagher Command Centre Import/Export Service

11. Install the Gallagher Command Centre Import/Export Service on the same PC as pivCLASS PACS Plug-in.

    Refer to the "Installing the Service" topic in the *Gallagher Command Centre Import/Export Utility User Guide* ( **Import\_User Guide.chm** ) for a detailed procedure. This document is located in the `'Utilities\import export'` directory of the Gallagher Command Centre installation files.


---

# 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/piv-card-support/installing-the-necessary-applications-tools-for-a-pivclass-workstation.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.
