# Legacy client

The previous Windows device client, what only it does, and how to move its devices to the endpoint agent.

Requires: Device Identity (DIAM)

> **Add-on required:** The legacy client is part of the **DIAM** (Device Identity) add-on.

The **legacy client** is the Windows client devices enrolled with before the [endpoint agent](https://dts-identity.com/docs/endpoints/device-client.md). Devices that still run it keep working: they report their posture, take part in [device compliance policies](https://dts-identity.com/docs/security/conditional-access/device-compliance-policies.md) and receive [remote actions](https://dts-identity.com/docs/endpoints/remote-actions.md). New features are built for the endpoint agent only, and the legacy client is replaced by it. Plan the move described [below](#moving-to-the-endpoint-agent).

To see which client a device runs, open it in the [device inventory](https://dts-identity.com/docs/endpoints/device-inventory.md): the **Overview** tab shows **DTS client** (the legacy client) or **Endpoint agent** under **Endpoint client**.

## What differs from the endpoint agent

| | Legacy client | Endpoint agent |
|---|---|---|
| Platforms | Windows on x64 | Windows, macOS and Linux |
| Network isolation | Windows; survives an uninstall | Windows, macOS and Linux; released when the agent is uninstalled |
| Blocking single destinations | Yes | No |
| Second factor at Windows sign-in | Verified on the device | Verified on the device or [by the platform](https://dts-identity.com/docs/endpoints/windows-logon-mfa.md#verified-by-the-platform) |
| Installer | Not code-signed | Code-signed |

A few [remote actions](https://dts-identity.com/docs/endpoints/remote-actions.md) and API methods exist for the legacy client only and are refused for a device with the endpoint agent: running a product executable, changing a product's agent state, the live product queries, and blocking or unblocking destinations.

## What gets installed

| Component | Role |
|---|---|
| **Client service** | A Windows service named `ClientGuard`, started automatically at boot. It holds the connection to the platform, collects posture data, and executes commands. |
| **Desktop app** | A small application in the notification area that shows the device's status and compliance result to the user, and handles [second-factor enrollment](https://dts-identity.com/docs/endpoints/windows-logon-mfa.md). It starts automatically for every user. |

Both are installed into a `ClientGuard` folder under **Program Files**. The client keeps its own state, including its device identity, outside that folder, so an in-place upgrade does not re-enroll the machine.

## Requirements

- **Windows on x64.**
- **Local administrator rights** to install, because the installer registers a Windows service.
- **Outbound connectivity to your platform instance.** The client dials out and keeps the connection open. No inbound firewall rule is needed.
- The installer is **not code-signed**, so Windows SmartScreen warns on first run. Verify the checksums shown next to the download in the console before deploying.

## What the client reports

Posture is collected every five minutes and sent as a difference against the last report, with a complete snapshot at least once a day or whenever the platform asks for one. Between reports the client sends a short check-in every few seconds, which is what makes a device show as connected.

It reports the operating system and hardware, the hostname, domain and signed-in account, the network configuration, volumes and video cards, installed software, the state of security products (firewall, real-time protection, definitions, threats, disk encryption), missing operating-system patches, and its own version, isolation status and MFA enrollment state. It collects no geolocation, browsing history, file contents, keystrokes or screenshots. The **process list** is collected only when an administrator runs that [remote action](https://dts-identity.com/docs/endpoints/remote-actions.md).

## Update

The client does **not** update itself. An update is a new installer, deployed the same way as the first one. The installation upgrades in place and preserves the device identity.

## Uninstall [#uninstall]

Removing the client cleanly takes three steps, and the order matters.

1. **Revert isolation first if the device is isolated.** The isolation rules are local firewall rules that survive uninstallation. A machine uninstalled while isolated stays cut off from the network, and you can no longer reach it to fix that remotely.
2. **Uninstall the client** through **Settings → Apps** in Windows, or through your software-distribution tool. This removes the service, the desktop app and the program files.
3. **Delete the device** in the [inventory](https://dts-identity.com/docs/endpoints/device-inventory.md). Uninstalling does not notify the platform, so the record stays until you remove it.

> **Note:** A standard uninstall leaves the client's local state on the machine, including its enrollment data. If you are decommissioning a device rather than re-imaging it, treat that state as data to be wiped along with the rest of the disk.

If the client is broken so badly that Windows cannot uninstall it, contact support rather than removing services and registry keys by hand. A wrong manual removal can leave a machine isolated with no way back.

## Moving to the endpoint agent [#moving-to-the-endpoint-agent]

Install the endpoint agent's Windows package over the legacy client, the same way you deploy any package (see [Endpoint agent](https://dts-identity.com/docs/endpoints/device-client.md#install-and-enroll)). The installer removes the legacy client's service and registration as part of the installation. Then:

- The device enrolls again with the endpoint agent and appears as a **new device** in the inventory. Delete the legacy record once the new one reports.
- A device the legacy client had **isolated stays isolated**: the endpoint agent takes the isolation over at its first start, and you release it from the device page as usual. It does not need to be released before the upgrade.
- The folder `C:\Program Files\DTS Client` and a few small state files of the legacy client remain on the disk. They are harmless; delete them by hand if you want.
- Second factors enrolled on the device for the Windows sign-in keep working: the endpoint agent takes them over once at its first start and removes the legacy client's copies.

Pilot the move on a few devices you can reach physically, in particular devices with MFA at Windows sign-in.

## Troubleshooting

- **The device never appears in the inventory.** Confirm the service `ClientGuard` is running, and that the endpoint can reach your instance outbound. An installer built for a different instance will never enroll.
- **A device stays isolated after uninstalling the client.** Reinstall the client, revert the isolation, then uninstall in the right order. Or install the endpoint agent, which takes the isolation over and lets you release it.

## See also

- [Endpoint agent](https://dts-identity.com/docs/endpoints/device-client.md) for the client that replaces this one.
- [Device inventory](https://dts-identity.com/docs/endpoints/device-inventory.md) for the enrolled devices and their posture.
- [Remote actions](https://dts-identity.com/docs/endpoints/remote-actions.md) for what you can trigger on an endpoint.
