> 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/editing-the-piv-card-type/setup-certificate-manager.md).

# Setup Certificate Manager

### Introduction

If a required certificate does not appear in the 'Available Trusted Root Certificates' list (on the **Trusted Root Certificates** tab of the PIV Card Type properties), this procedure can be used to import the certificate into the list.

You will need to have available or download the required Root Certificate to be able to complete this procedure.

### Procedure

1. From the **Start** menu, click **Run…**
2. Type in **MMC** and click **OK**.

   The MMC Console window displays.
3. Select **File** from the menu bar, then **Add/Remove Snap-in…**

   The Add or Remove Snap-ins dialog displays.
4. Select **Certificates** in the ‘Available snap-ins’ grid on the left, and click the **Add** button.

   A Certificates snap-in screen displays.
5. Click the **Computer account** radio button, then click the **Next** button.

   The Select Computer screen displays.
6. Click the **Finish** button.
7. Click the **OK** button.

   The Add or Remove Snap-ins dialog closes.
8. Select **File** again from the menu bar, then **Save As…**
9. Choose a name, then save in your Administrative Tools programs directory.

   The local machine certificate store should now be visible in tree view in the left grid.
10. Click on the local machine certificate store in the left grid.
11. Right-click on **Trusted Root Certification Authorities**, then select **All Tasks** > **Import…**

    The Certificate Import Wizard displays.
12. Click the **Next** button.
13. Click the **Browse** button and navigate to the location of the Trusted Root Certificate.

    **Note:** You may need to change the "File Type" for the certificate to appear.
14. Select the certificate and click the **Open** button.
15. Click the **Next** button.
16. Select the **Place all certificates in the following store** option, and click the **Next** button.
17. Click the **Finish** button.

    The import completes.
18. Select **File** again from the menu bar, then **Exit**.

    The certificate should now be visible in the ‘Available Trusted Root Certificates’ grid on the **Trusted Root Certificates** tab of the PIV Card Type properties.

    **Note:** You may need to **right click** > **Refresh List** for the grid to update.


---

# 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/editing-the-piv-card-type/setup-certificate-manager.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.
