> 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/visitor-management-kiosk/visitor-management-kiosk-installation-instructions.md).

# Visitor Management Kiosk Installation Instructions

### Introduction

Initial installation of the Visitor Management Kiosk should be performed by a user who has administrative rights on both the server and client PC. The Visitor Management Kiosk then needs to be installed by each user individually, (i.e. there is no option to install for all users of the client PC). These subsequent Visitor Management Kiosk client installs do not need to be performed by Administrators, the users just need to have access to the VMClientUpdate shared folder on the server, (i.e. \\\[ServerName]\ VMClientUpdate).

**Note:** When installing Visitor Management Kiosk, make sure the operator logged into the kiosk has the privilege to view all cardholders who might badge at the kiosk for rapid entry.

***

### Procedure

The following procedure for installing the Visitor Management Kiosk has been split into three parts:

* Server Installation,
* Client Installation, and
* Card Scan Driver Installation (if business card scanning capability is going to be used).

<details>

<summary>Visitor Management Kiosk Server Installation</summary>

1. Ensure the site licence file **CommandCentre.lic**:

   * is accessible on the PC. It is recommended that this file be copied to `'C:\Windows'` prior to commencing the installation, and
   * contains the following options:

     <table><thead><tr><th width="198">License option</th><th>Description</th></tr></thead><tbody><tr><td><code>[Features]</code><br><code>VisitorManagement=1</code></td><td>Allows you to see and configure the Kiosk in Configuration Client on the Division setup.</td></tr><tr><td><code>[Limits]</code><br><code>Visit Kiosk=X</code></td><td>The number <code>X</code> indicates how many Kiosk Clients can be connected at one time.</td></tr></tbody></table>

   In addition to these two options, if you want Hosts to be automatically notified of their visitor's arrival, your site licence file must also contain the option:

   `[Features]`\
   `Notifications=1`
2. Install Gallagher Command Centre.

   Refer to the appropriate release note with the Gallagher Command Centre installation files, (i.e. either the "New Installations" release note or the "Upgrade Procedures" release note), for the procedure.
3. At the time Command Centre is installed, the Visitor Management Kiosk Client is automatically built to the default location of `'C:\Program Files\Gallagher\Command Centre\VMKioskSetup\VMKioskSetup'`. Although we recommend sites leave the Kiosk Client in this default location, it can be built to a different location.

   Do you want to build it to a different location?

   <table><thead><tr><th width="66">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>the Server Installation is complete. Go to the <strong>Visitor Management Kiosk Client Installation</strong> procedure below.</td></tr><tr><td>yes</td><td>go to Step 4.</td></tr></tbody></table>
4. Go to the `'C:\Program Files\Gallagher\Command Centre\VMKioskSetup`' folder and double-click on **ClickOnceBuilder.exe**.

   The Visitor Management Kiosk - ClickOnce Builder screen displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8004a5839061e61aac8768ab06af8347880eeff6%2Fvmkiosk_clientsetup.png?alt=media)
5. Change the 'Deploy To' settings to the required location, and click the **Build** button.

   The Client build may take a few minutes.

   **Note:** ClickOnce supports deployment via HTTP/HTTPS. You can specify a URL instead of a machine name for the **ClickOnce Server** name.
6. Ensure the folder indicated in the **Publish To** field is shared, and the path is set correctly in the **Network Share** field.

   This allows the Visitor Management Kiosk application to be installed on other computers.
7. Click the **Quit** button.

</details>

<details>

<summary>Visitor Management Kiosk Client Installation</summary>

1. Browse to the `'\\[ServerName]\VMKioskSetup'` folder and run the installation executable, (i.e. **ClickOnceVMKioskSetup.exe** ) to initiate the client install.

   The following Application Install Security Warning displays:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3dee1979fe728904f86cae781dec15b69685498b%2Fsecuritywarning.png?alt=media)
2. Click the **Install** button.

   The Visitor Management Kiosk client installs and the logon screen displays:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c29c5a5b71caf6dd5e1c36db345679081c512343%2Fvisitorkiosk_logonscreen.png?alt=media)
3. Type your **Logon Name**.
4. Click in the **Password** field (alternatively, press the **Tab** key), and type your password.
5. Select another language from the **Language** drop-down box if required.
6. Click the **Logon** button (alternatively, press the **Enter** key).

   **Note:** If you enter successive invalid logon name and password combinations equal to the configured 'number of failed attempts before lockout', then you will be locked out for the configured lockout period (or permanently if this option is set). The message *"Operator locked out due to repeat logon failures"* will display on the logon screen.

</details>

<details>

<summary>Card Scan Driver Installation</summary>

Before the card scan drivers are installed, all the necessary Visitor Management Kiosk configuration work in Command Centre should be performed. Once all the components are configured, the card scan drivers need to be installed by a member of the Kiosk Administrator Access Group, as follows:

1. While the 'Welcome screen' is displayed, present your card at the Kiosk Door/Reader.
2. Open the **Tools** screen, if not already open.
3. Click the **Install Card Scan Drivers** button.

   The card scan drivers install.

It may not be possible to install the card scan drivers via the Kiosk application. This could be because the logged in user is not an Administrator or User Account Control is switched on. To install the drivers manually:

1. Browse to the `‘Utilities\Visitor Management Drivers\Card Scan Drivers'` folder of the Command Centre installation files.
2. Copy the drivers folder from the installation files to `'C:\Program Files\Gallagher\Command Centre\VMKioskSetup\VMKioskSetup'` on the server.
3. On the Client PC browse to `'\\[Server_name]\VMKioskSetup\Drivers'`, double click on **dpinst.exe** and follow the on screen prompts.

   **Note:** For 64 bit machines browse to `'\\[Server_name]\VMKioskSetup\Drivers\x64'`.

</details>


---

# 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/visitor-management-kiosk/visitor-management-kiosk-installation-instructions.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.
