Preview · This help is still growing and will be extended over time.

Windows client · Administrator

Deploy the Windows client

Rolling out the echo Windows client to your organization's computers, with a focus on Microsoft Intune

Updated: October 2026

The echo Windows client – the echo desktop app for Windows – is required for live caller recognition. It is delivered as a signed MSIX package (.appxbundle for x86 and x64) together with an App Installer file (.appinstaller). Both are published by Snapbean Software AG at a fixed address:

https://sateamsmateclientprod.blob.core.windows.net/windows-client/installer/Snapbean.TeamsMate.Client.Windows.Package.appinstaller

The App Installer file always points to the latest version of the package. How you install the client decides whether it keeps itself up to date:

Option A: App Installer (recommended)Option B: App package (.appxbundle)
Automatic updatesYes – the client checks for a new version on every start and updates itselfNo – every new version must be deployed again
Microsoft IntuneVia a small PowerShell script (the .appinstaller file cannot be uploaded to Intune directly)Directly as a line-of-business app
Effort for ITOne-timeWith every release
Typical useMost organizationsOrganizations that must approve every software version before rollout
Who is this page for?IT administrators who distribute the echo Windows client to their users, in particular with Microsoft Intune. For security software and EDR allowlisting see Security and endpoint protection.

Prerequisites

The client is installed per user. After installation, each user signs in once with their Microsoft account. The client then runs in the background and starts automatically with Windows.

When the client is installed via the App Installer file, Windows remembers where the package came from. On every start, the client checks this address for a newer version and installs it automatically. You never have to deploy an update yourself.

Install manually (single computers)

Open the App Installer link above in a browser on the computer, or download the .appinstaller file and double-click it. Windows shows the App Installer dialog; click Install.

Deploy with Microsoft Intune

Microsoft Intune cannot deploy an .appinstaller file as an app. Instead, you deploy a short PowerShell script that runs in the context of the signed-in user and installs the client with the Add-AppxPackage command from the App Installer file.

1

Create the PowerShell script

Save the following script as Install-EchoClient.ps1:

$appInstallerUri = 'https://sateamsmateclientprod.blob.core.windows.net/windows-client/installer/Snapbean.TeamsMate.Client.Windows.Package.appinstaller'
$packageName = 'd10d600d-78e9-4853-aecc-84552804a53a'

if (Get-AppxPackage -Name $packageName) {
    Write-Output 'echo Windows client is already installed.'
    exit 0
}

try {
    Add-AppxPackage -AppInstallerFile $appInstallerUri -ErrorAction Stop
    Write-Output 'echo Windows client installed.'
    exit 0
} catch {
    Write-Error "Installation of the echo Windows client failed: $_"
    exit 1
}

The script only installs the client if it is not yet present. All later updates come in automatically through the App Installer.

2

Add the script in Intune

In the Microsoft Intune admin center (opens in a new tab), go to Devices → Scripts and remediations → Platform scripts and click Add → Windows 10 and later. Give it a name (e.g. echo Windows client) and upload Install-EchoClient.ps1.

Use these settings:

SettingValue
Run this script using the logged on credentialsYes – the client is installed per user, so the script must run as the user, not as SYSTEM
Enforce script signature checkNo (unless you sign the script with your own certificate)
Run script in 64 bit PowerShell HostYes
3

Assign the script

Assign the script to the user or device groups that should use echo and save. The script runs at the next Intune check-in of the device while a user is signed in.

Alternative: Win32 appIf you prefer to manage the client as an app in Intune (e.g. to see the installation status per device or make it available in the Company Portal), you can wrap the same script as a Win32 app (.intunewin) with install behavior User and use a custom detection script based on Get-AppxPackage -Name d10d600d-78e9-4853-aecc-84552804a53a. Automatic updates work the same way.
When are updates installed?The client checks for a new version every time it is started (e.g. after signing in to Windows). If a newer version is available, it is installed in the background and used from the next start of the client.

Option B: App package without automatic updates

Alternatively, you can deploy the .appxbundle file directly as a managed app in Intune. Intune then installs exactly this version. The client does not update itself in this case: for every new version you must upload the new package to Intune and deploy it again.

1

Download the current package

Open the App Installer link above in a browser. The .appinstaller file is a small XML file; the Uri attribute of the MainBundle element contains the download address of the current .appxbundle file. Download that file.

2

Add a line-of-business app

In the Microsoft Intune admin center (opens in a new tab), go to Apps → Windows → Add, select the app type Line-of-business app and upload the .appxbundle file. Intune reads the name, publisher and version from the package. Under App package context we recommend User.

3

Assign the app

Assign the app as Required to the desired user or device groups (or as Available to offer it in the Company Portal).

4

Deploy updates

When a new version of the echo Windows client is released, download the new package (see Download the current package) and replace the package of the existing app in Intune under Properties → App information → Edit with the new .appxbundle file.

Keep the client up to dateOlder client versions may stop working when the echo service changes. With option B, check regularly for new versions and deploy them promptly. If you do not need to approve every version, we recommend option A.

Choose one option per computer

Do not combine both options on the same computers. A client that was installed from the .appxbundle via Intune is not linked to the App Installer and therefore does not update itself, and Intune may reinstall or overwrite a version that was updated through the App Installer. If you switch from option B to option A, first remove the line-of-business app assignment (or assign it as Uninstall), then deploy the script from option A.

Troubleshooting