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

# Visitor Management Application Installation Instructions

### Introduction

Initial installation of the Visitor Management application should be performed by a user who has administrative rights on both the server and client PC.

The Visitor Management client 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 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`).

**Notes:**

* This procedure is for a clean install of Visitor Management **only**. If you are upgrading from a previous version, refer to the Command Centre Release Note provided with the installation files for the upgrading instructions.
* It is recommended that you run the Visitor Management Server Installer locally, (i.e. not across the network).

***

### Before you begin

Before installing the Visitor Management Application log on to the server machine as an Administrator.

***

### Procedure

The procedure for installing the Visitor Management application has been split into two parts:

<details>

<summary>Server Installation</summary>

1. Install Gallagher Command Centre.

   Refer to the appropriate release note provided with the Gallagher Command Centre installation files, (i.e. either the "New Installations" release note or the "Upgrade Procedures" release note), for the procedure.
2. At the time Command Centre is installed, the Visitor Management Client is automatically built to the default location of `'C:\Program Files\Gallagher\Command Centre\VMClient\VMClientUpdate'`. Although we recommend sites leave the Visitor Management Client in this default location with the default TCP port, it can be built to a different location and/or run on a different TCP port. Do you want to build it to a different location or change the TCP port?

   <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>Client Installation</strong> procedure below.</td></tr><tr><td>yes</td><td>go to Step 3.</td></tr></tbody></table>
3. If you would like to change the TCP port, complete the following steps:

   1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
   2. Click the **Web Services** tab.
   3. Change the port in the **Server Base Port** field.
   4. Click **OK** to exit and save your changes.

   **IMPORTANT:** If the TCP port is changed, The Visitor Management - ClickOnce Builder configuration file will also need to be modified, as follows:

   1. Go to the `'C:\Program Files\Gallagher\Command Centre\VMClient\Files'` folder.
   2. Open the **VMCABClient.exe.config** file, in the \<appSettings> section, modify the port value to match the Server Base Port:

      \<add key="Port" value="4243"/>
   3. Save the file and proceed to Step 4.
4. Go to the `'C:\Program Files\Gallagher\Command Centre\VMClient`' folder and double-click on **ClickOnceBuilder.exe**.

   The Visitor Management - ClickOnce Builder screen displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-aa726b547ac728e8ed989a97f1ad220108a3edef%2Fvm_clientsetup.png?alt=media)
5. Change the 'Deploy To' settings to the required location if the location has changed, 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 application to be installed on other computers.
7. Click the **Quit** button.

</details>

<details>

<summary>Client Installation</summary>

1. Browse to the `VMClientUpdate` shared folder on the server, (i.e. `\\[ServerName]\VMClientUpdate`).
2. Run the Visitor Management installation executable, (i.e. **ClickOnceVisitorManagementSetup.exe** ).

   The following Open File Security Warning displays:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5dcad5f9629c9f87dac27de07192702572f62fea%2Fappinstall_openfile_securitywarning.png?alt=media)
3. Click the **Run** button.
4. Does the following Application Install - Security Warning screen display?

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ebefbe755092c589fa5239c762657572fb2242d0%2Fappinstall_securitywarning.png?alt=media)

   <table><thead><tr><th width="72">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>go to Step 6.</td></tr><tr><td>no</td><td><p>Microsoft.NET Framework 4.5 is not installed on the PC, which is needed for Visitor Management.</p><p>A License Agreement dialog displays for the application(s) which is not installed.</p><p><strong>Note:</strong> If only one License Agreement dialog displays, then the other application is already installed.</p></td></tr></tbody></table>
5. Click the **Accept** button to accept the license agreement.

   A series of dialog boxes display indicating which application(s) is being installed, followed by the Application Install Security Warning screen displaying (shown at Step 4).
6. Click the **Install** button.

   The Visitor Management application installs, and launches automatically.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-60760707c37e2279105700d2a725b24aae67631f%2Fvm_logonscreen.png?alt=media)

</details>

**Notes:**

* Command Centre needs to be configured before any users can log on to the Visitor Management application.
* It is recommended that you create a shortcut on your desktop for the Visitor Management application.


---

# 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/visitor-management-application-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.
