Installing with winget

Terminal Services Manager is in the Microsoft winget repository. The moniker is tsmanager and the full identifier is LizardSystems.TerminalServicesManager. Examples below use the moniker; the full identifier works wherever the moniker does and is less ambiguous in scripts.

Make sure winget is available

Windows 10 / 11 desktop

Winget ships as part of the App Installer component and is usually already there. If winget is not recognized, install App Installer from the Microsoft Store, or register it from PowerShell:

Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe

Windows Server 2025

Winget arrives through Windows Update. Install the latest cumulative updates.

Windows Server 2019 / 2022

Not pre-installed. Bootstrap it through the Microsoft WinGet PowerShell module:

Install-PackageProvider -Name NuGet -Force
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery
Repair-WinGetPackageManager -AllUsers

Open a new terminal session afterward and verify:

winget --version

Install

winget install tsmanager

Terminal Services Manager appears in the Start menu when the installer finishes.

Upgrade an existing manual installation

If you previously installed Terminal Services Manager from the website, winget can still take over upgrades. It identifies the package by the product code in the Windows registry, so a manually installed copy is recognized as already-present.

winget upgrade tsmanager

Settings, computer lists, message presets, and custom commands are kept.

Silent install for deployment

For setup scripts, Intune, SCCM, or any other automation:

winget install tsmanager --silent --accept-package-agreements --accept-source-agreements

--silent suppresses installer UI. The --accept-* flags skip the interactive prompts that block unattended runs.

Roll out across a fleet from a PowerShell session:

$computers = Get-Content ".\server-list.txt"
foreach ($computer in $computers) {
    Invoke-Command -ComputerName $computer -ScriptBlock {
        winget install tsmanager --silent --accept-package-agreements --accept-source-agreements
    }
}

To replicate a full toolset of admin packages across machines, export from a reference workstation and import on each new machine:

winget export -o admin-tools.json
winget import -i admin-tools.json --accept-package-agreements --accept-source-agreements

Update

Check whether a new version is available:

winget show tsmanager

Update only Terminal Services Manager:

winget upgrade tsmanager

Or update everything winget manages on the machine:

winget upgrade --all

The program's built-in update checker does not conflict with winget. Use whichever you prefer.

Pin a version

During a change freeze, or to stay on a known-good version:

winget pin add tsmanager

winget upgrade --all then skips Terminal Services Manager. Remove the pin when you are ready:

winget pin remove tsmanager

Pin to a version range to allow patch updates but block major changes:

winget pin add tsmanager --version 26.*

Uninstall

winget uninstall tsmanager

Troubleshooting

• winget is not recognized. Winget needs Windows 10 build 1809 or later. On older builds it is unavailable. On Server 2019 / 2022 use the PowerShell setup above.
• No applicable installer found. Terminal Services Manager is 64-bit only.
• Package not found. Refresh the source index: winget source update.
• Installation requires elevation. The installer writes to Program Files. Run the terminal as Administrator, or accept the UAC prompt.
• Upgrade does not detect an existing install. Happens when the existing copy was installed under a different user account or with a non-standard product code. Uninstall manually, then install through winget.