Skip to main content

Installing the Windows Endpoint Client

The Endpoint Client is what makes an endpoint's local printers available inside remote sessions — the endpoint half of printer redirection. Install it on Windows workstations and laptops whose users connect to ScrewDrivers-equipped session hosts. (Installing where applications run locally instead? That machine needs the session agent, not the Endpoint Client.)

Before you install​

  • Windows 10 or newer, 64-bit. Endpoints that must stay on 32-bit or older Windows can continue using the v6 client, which connects to v7 servers.
  • A supported remote desktop client installed first — Citrix Workspace, the Windows RDP client, or Omnissa Horizon — since the Endpoint Client integrates with it.
  • The installer: ScrewDriversClient_<version>_x64.msi, from the Tricerat downloads share (your account team or Tricerat Support provides the link). Use the latest release, run it locally, and unblock the downloaded file first.

Installing on one machine​

  1. Run ScrewDriversClient_<version>_x64.msi as administrator and accept the license agreement.
  2. Follow the wizard — defaults are right for almost everyone. Enter your License Server address if prompted for licensing.
  3. Reboot when the installer asks — the client's integration with the remote desktop software isn't complete until then.

Verify: the ScrewDrivers client icon appears in the system tray; right-click it and choose About to confirm the version. Then connect to a session and check that your local printers appear — the Endpoint Client reference tours every tab if you want to explore.

Installing on a fleet​

For more than a handful of machines, deploy the MSI silently:

  • Silent install switches — the full property reference; a minimal example: msiexec.exe /i ScrewDriversClient_<version>_x64.msi /qn ADDLOCAL=MainFeature, EndpointClient
  • Intune deployment — packaging and assignment through Microsoft Endpoint Manager. Group Policy, SCCM, and PDQ-style tools work the same way with the silent switches.

Staying current​

Once installed, the client largely maintains itself: on each connection it downloads the plugin matching the server's version, so server upgrades don't require a client rollout. Track what's actually connecting with Monitoring Client Versions.

Other platforms​

macOS, Linux, and IGEL endpoints have their own guides — see the installation hub.