Deploying Viewer — Lumirai Viewer

This page is for clinic IT installing Viewer on shared Windows computers: Citrix or other terminal servers, non-persistent virtual desktops, and imaged reading-room workstations. Clinicians do not need to do any of this.

Standard or managed install

The Windows installer offers Anyone who uses this computer (all users) or Only for me. Only for me is the default.

Install	Folder	Needs admin
Only for me (standard)	`%LOCALAPPDATA%\Programs\Lumirai Viewer`	No
All users (managed)	`C:\Program Files\Lumirai\Lumirai Viewer`	Yes (UAC)

Viewer appears under a Lumirai folder in the Start menu. An install from an earlier version keeps its original folder when it updates, so published application paths keep working.

Managed install

Download the installer from Downloads and run it as an administrator with /allusers. A silent install without it (/S alone) installs only for the account that ran it. Replace the server with your clinic's Lumirai Link hostname.

"Lumirai-Viewer-Setup-x64.exe" /S /allusers /SERVER=lumirai.example.org /SSL=1 /DISABLEUPDATES

Use Lumirai-Viewer-Setup-arm64.exe on Windows on Arm. /D=C:\path sets a different install folder and must be the last argument.

Switch	Effect
`/S`	Silent install, no wizard
`/allusers`	Install for everyone on the computer (required for shared desktops)
`/SERVER=host`	Writes the `ServerHostname` policy below
`/SSL=1` or `/SSL=0`	Writes the `ServerSSL` policy below
`/DISABLEUPDATES`	Writes the `DisableUpdates` policy below

Only the switches you pass are written. Updating or uninstalling Viewer does not remove the policy.

Registry policy

Viewer's own settings (Settings → Lumirai Link and Settings → About → Automatic updates) are saved per user, so changing them while signed in as one account does not affect anyone else. To set them for every user, Viewer reads machine policy at launch from:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Lumirai\Viewer

Value	Type	Effect
`ServerHostname`	REG_SZ	Lumirai Link hostname for users who have not saved one of their own
`ServerSSL`	REG_DWORD	`1` secure connection (default), `0` not secure. Goes with the hostname.
`DisableUpdates`	REG_DWORD	`1` turns off all in-app updates for everyone

The server values are a default. A new user starts at Log In with the server already filled in. A user can still change server in Settings, and their saved choice then wins for that user.
With DisableUpdates=1, Viewer never checks for, downloads, or installs an update, and Check Now is hidden. Settings → About shows Managed by your organization. Update by running the new installer on the image with the same command.
The same key under HKEY_CURRENT_USER also works. A value in HKEY_LOCAL_MACHINE wins.
Changes apply the next time Viewer starts.

Set it with Group Policy, Intune, or a .reg file

Any tool that writes registry policy works. Example .reg file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Lumirai\Viewer]
"ServerHostname"="lumirai.example.org"
"ServerSSL"=dword:00000001
"DisableUpdates"=dword:00000001

To check it:

reg query "HKLM\SOFTWARE\Policies\Lumirai\Viewer"

To remove it:

reg delete "HKLM\SOFTWARE\Policies\Lumirai\Viewer" /f

Citrix and shared desktops

Each user's data lives in their profile under %APPDATA%\Lumirai Viewer: their saved server and display preferences, the saved Link login (encrypted for that Windows user), and Joints cookies.

If that folder roams with the profile (Citrix Profile Management, FSLogix, or roaming profiles), users stay signed in and keep their preferences after the desktop resets. If not, each user signs in again every session. With ServerHostname set, that is only the Log In step.
The Cache, Code Cache, and GPUCache folders inside it are safe to exclude from the profile.
On a desktop that resets from an image, set DisableUpdates=1. An update installed in a session is lost at the next reset, and a user without admin rights cannot update an all-users install anyway.