> 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/install-wallboard.md). # Install Wallboard Install the local Wallboard client for existing Dialogue Cloud Neo (Connect) customers. Wallboard is available for existing customers who use Dialogue Cloud Neo (Connect). Use this page to install the local Wallboard client on a workstation and connect it to the customer's UCC. {% hint style="info" %} Wallboard is in maintenance mode and no longer receives new feature development. Existing deployments remain supported for maintenance and critical/security fixes. Wallboard is not available for Dialogue Cloud Neo (Unify). Use [Dialogue Workspace](/use/monitor-and-report/dialogue-workspace.md) for Unify. {% endhint %} For user-facing view descriptions and troubleshooting, see [Wallboard](/use/existing-dialogue-cloud-neo-connect-apps/wallboard.md). ## Before you begin Confirm the following before you install Wallboard: * The workstation is assigned to an existing Dialogue Cloud Neo (Connect) customer. * You have the current Wallboard MSI package. Obtain the package from AnywhereNow or an authorized AnywhereNow partner. * The Microsoft Teams client is installed and patched. * Windows is fully patched. * The 32-bit or 64-bit Windows, Microsoft 365, Microsoft Teams, and Microsoft Office bitness is matched where applicable. * Only one Microsoft Office installation is present. * .NET Framework 4.6.2 or a later 4.x version is installed. * A Windows user is signed in before Wallboard starts. * You have the UCC name and the Dashboard Service host or URL provided for the customer's Dialogue Cloud Neo (Connect) UCC. {% hint style="warning" %} When Wallboard uses the local Microsoft Teams client, Microsoft Teams does not provide Presence, display name, and photo information to local applications through the legacy local-client mechanism. Do not rely on those local-client values being available in Wallboard. {% endhint %} ## Install the client 1. Run the current Wallboard MSI package on the workstation. 2. Follow the installer prompts. 3. Enter the values supplied for the customer's UCC. 4. Finish the installation. 5. Start Wallboard from the installed shortcut. 6. Confirm that Wallboard opens the expected default view and can connect to the configured UCC. Use the following installer fields as a configuration checklist. | Installer field | How to configure it | | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **UCC Name** | Enter the UCC application or contact-center identifier provided for the customer. | | **UCC Host / Dashboard Service host** | Use the Dashboard Service host or URL provided for your Dialogue Cloud Neo (Connect) UCC by AnywhereNow or your partner. Do not substitute a regional or example endpoint. | | **Lync client** | Treat this as a legacy installer field name. Do not use it as a Microsoft Teams version selector. | | **Secure address** | Use the secure address option for Dialogue Cloud connections. | | **Wallboard view** | Select the default view that Wallboard should show when it starts. | ## Validate the installation After installation: 1. Start Wallboard from the installed shortcut. 2. Confirm that the expected default view loads. 3. Confirm that Wallboard connects to the configured UCC. 4. Confirm that queue, skill, agent, and reason-code information appears according to the selected view and the customer's configuration. 5. If authentication is enabled for the UCC service, continue with [Configure Wallboard authentication](/platform-administration/maintenance-mode-applications/wallboard/configure-wallboard-authentication.md). 6. If the page does not show expected data, use [Troubleshoot Wallboard](/use/existing-dialogue-cloud-neo-connect-apps/wallboard/troubleshooting.md). ## Related Wallboard administration * [Update Wallboard](/platform-administration/maintenance-mode-applications/wallboard/update-wallboard.md) * [Unattended installation](/platform-administration/maintenance-mode-applications/wallboard/unattended-install-wallboard.md) * [Configure Wallboard authentication](/platform-administration/maintenance-mode-applications/wallboard/configure-wallboard-authentication.md) * [Configure Wallboard views](/platform-administration/maintenance-mode-applications/wallboard/configure-wallboard-views.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/install-wallboard.md?ask=&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.