> 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/snapper/install-snapper.md). # Install Snapper Install Snapper for Microsoft Teams in Dialogue Cloud Neo (Connect). Install Snapper on Windows devices for existing Dialogue Cloud Neo (Connect) customers who use Microsoft Teams. Snapper is not a standalone contact center component; it must be connected to a configured UCC (Unified Contact Center). {% hint style="warning" %} **End of Support Maintenance (EoSM)** Snapper reached End of Support Maintenance in October 2023. No new features or integration updates will be added. {% endhint %} {% hint style="warning" %} **Unsupported SharePoint uploads** Snapper screen recording does not support Microsoft Entra ID app + certificate authentication for SharePoint connections. Microsoft retired legacy Client ID/Secret authentication in April 2026. Therefore, affected Snapper-to-SharePoint upload scenarios are not supported. Because Call Property Service is being deprecated alongside Snapper, screen recording links should no longer be expected to appear in the contact timeline, reporting data, or contact center history. {% endhint %} {% hint style="info" %} User first-run and sign-in steps are documented in the Snapper user guidance. This page covers administrator deployment and initial configuration only. {% endhint %} {% hint style="warning" %} Snapper is in maintenance mode and no longer receives new feature development. Existing deployments remain supported for maintenance and critical/security fixes. Snapper is not available for Dialogue Cloud Neo (Unify). Replace Snapper with [WebAgent](/use/handle-conversations/webagent.md) for agent interactions and [Dialogue Workspace](/use/monitor-and-report/dialogue-workspace.md) for real-time supervision and dashboards. {% endhint %} ## Before you begin Make sure the device has: * A supported Snapper installer from your partner or regular AnywhereNow contact. * Microsoft Office and Microsoft Teams installed. * Latest Windows updates installed. * Microsoft Teams registered as the chat app for Office: in Microsoft Teams, go to **Settings** > **General** > **Register Teams as the chat app for Office**. * Latest .NET Framework 4.x, with minimum version 4.6.2. * Microsoft ASP.NET Core Runtime and .NET Desktop Runtime versions required by the selected Snapper build. * Both runtimes installed with the architecture matching the Snapper installer: `x64` or `x86`. * A signed-in Windows user. * Minimum screen resolution `1920 x 1080`, with scaling not higher than `150%`. {% hint style="warning" %} .NET 6.0 is end of life. Microsoft .NET 8.0 is nearing end of life, which will affect support for Snapper builds that use it. See [Microsoft .NET downloads](https://dotnet.microsoft.com/en-us/download/dotnet). {% endhint %} Snapper running on .NET 10.0 is available on request through [AnywhereNow Support](https://support.anywhere.now/csm). This does not mean every bundled Snapper installer uses .NET 10.0. For the requested .NET 10.0 build, download and install both **ASP.NET Core Runtime 10.0** and **.NET Desktop Runtime 10.0** from [Microsoft .NET 10.0 downloads](https://dotnet.microsoft.com/en-us/download/dotnet/10.0). Select `x64` for an `x64` Snapper installer or `x86` for an `x86` installer. If the installer is delivered as a `.zip` file, check the file properties and unblock the file before extracting it. ## Install Snapper {% hint style="info" %} The Snapper installer must match the Microsoft Teams client bit level: 32-bit or 64-bit. {% endhint %} 1. Run `Setup.msi`. 2. Select **Next**. 3. Read and accept the license agreement. 4. In available features, install **Anywhere365 Snapper (xx bit)**. 5. Select **Next**. 6. Select the client type. Use one of these supported values: | Client type | Use when | | ---------------------------- | --------------------------------------------------------------------------------------------------------------------- | | **Teams** | The customer environment still uses the Microsoft Teams client path represented by this Snapper value. | | **Teams Direct Routing** | The customer environment still uses the Microsoft Teams Direct Routing client path represented by this Snapper value. | | **New Teams** | The customer environment uses the New Microsoft Teams client. Introduced in DC2024.01. | | **New Teams Direct Routing** | The customer environment uses the New Microsoft Teams client with Direct Routing. Introduced in DC2024.01. | 7. Optional: enter the Microsoft Teams client ID. If no custom ID is entered, Snapper uses the global Microsoft Entra enterprise application for Snapper. 8. Select **Install**. 9. Wait for the installation to finish. 10. Select **Finish**. 11. Start Snapper from the shortcut. ## Configure the client type after installation If Snapper was not configured during installation: 1. Start Snapper. 2. Open the menu. 3. Change **Client Type** to the correct Microsoft Teams value: * **Teams** * **Teams Direct Routing** * **New Teams** * **New Teams Direct Routing** 4. Optional: enter the Microsoft Teams client ID. 5. Restart Snapper. ## Configure the first UCC If the installer did not configure a UCC, add the UCC after installation: 1. Start Snapper. 2. Open **Settings**. 3. Open **UCC Config**. 4. Add the UCC name supplied for the customer environment. 5. For install and settings-reference contexts, use the **UCC Host** value supplied for the environment. 6. Set **Secure** according to the environment configuration. 7. Save the configuration. 8. Restart Snapper if prompted. {% hint style="warning" %} Some UCC configuration references use **UCC Host** and others use **UCC Url**. Use the environment-provided value, and do not treat one label as a global product label until the UI label is confirmed. {% endhint %} ## Expected result Snapper starts on the device, uses the selected Microsoft Teams client type, and can connect to the configured UCC after the user signs in. ## Related tasks * [Update Snapper](/platform-administration/maintenance-mode-applications/snapper/update-snapper.md) * [Unattended installation](/platform-administration/maintenance-mode-applications/snapper/unattended-install-snapper.md) * [Configure Snapper authentication](/platform-administration/maintenance-mode-applications/snapper/configure-snapper-authentication.md) * [Create the Snapper Teams app](/platform-administration/maintenance-mode-applications/snapper/create-snapper-teams-app.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/snapper/install-snapper.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.