> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/wallboard/unattended-install-wallboard.md).

# Install Wallboard unattended

Deploy Wallboard silently by using the Wallboard MSI property names.

Use unattended installation when you need to deploy the local Wallboard client silently to a workstation.

The installer uses legacy MSI property names. Keep the property names exactly as required by the MSI package, and supply customer-specific values for the deployment.

## Before you begin

Confirm the following before unattended installation:

* You have the current Wallboard MSI package from AnywhereNow or an authorized AnywhereNow partner.
* The workstation meets the prerequisites in [Install Wallboard](/platform-administration/maintenance-mode-applications/wallboard/install-wallboard.md).
* You have the UCC name and the Dashboard Service host or URL provided for the customer's Dialogue Cloud Neo (Connect) UCC.
* You know the local installation folder required for the workstation.

## MSI properties

Use the following properties with the Wallboard MSI package.

| MSI property       | Purpose                                                                                                                                |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| `UCCNAME`          | UCC name or contact-center identifier.                                                                                                 |
| `PROTOCOL`         | Connection protocol. Use the secure protocol value supplied for the deployment.                                                        |
| `UCCHOST`          | Dashboard Service host or URL supplied for the customer's Dialogue Cloud Neo (Connect) UCC. The exact value is customer-specific.      |
| `INSTALLFOLDER`    | Local installation folder.                                                                                                             |
| `LYNCVERSIONVALUE` | Legacy MSI property name. Keep the value supplied with the current deployment package; do not invent a Microsoft Teams-specific value. |

{% hint style="warning" %}
Do not reuse endpoint examples from another customer or region. Use only the Dashboard Service host or URL supplied for the customer's Dialogue Cloud Neo (Connect) UCC.
{% endhint %}

## Validate the unattended installation

After deployment:

1. Start Wallboard from the installed shortcut.
2. Confirm that Wallboard connects to the configured UCC.
3. Confirm that the expected default view loads.
4. If authentication is enabled, confirm that the user can sign in through the configured authentication URL.

If Wallboard does not connect or does not show expected data, use [Troubleshoot Wallboard](/use/existing-dialogue-cloud-neo-connect-apps/wallboard/troubleshooting.md).


---

# 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://atlas.anywhere.now/platform-administration/maintenance-mode-applications/wallboard/unattended-install-wallboard.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.