Getting started

Install the suite,
then open the room.

Put the Controller on the operator PC. Put the Client on every classroom machine. One site activation code covers cloned images.

Downloads Update feed

Windows

Run the suite installer.

Nexus-Suite-Setup-windows-amd64.exe installs to C:\Program Files\Nexus\Nexus Suite. Choose Controller, Client, or both.

Interactive

Pick components

Run the installer and select Controller for the console, Client for classroom PCs, or both on a lab image.

Silent

Scripted install

Quiet suite install uses /S. Client-only: /S /CLIENT. Uninstall with Uninstall Nexus Suite.exe /S.

Linux

Extract and run install.sh.

Unpack Nexus-Suite-linux-amd64.tar.gz, then install as root. GTK/WebKit packages must be present for the UI.

Commands

Component flags

sudo ./install.sh --all (default), --controller, or --client. Optional --prefix PATH.

Service

Client systemd unit

The Client option installs the UI and enables the Nexus service. Controller is the console only.

Network

Allow the LAN ports.

Discovery uses UDP 47831. The client API is TCP 47832. Windows Firewall on the Client must allow both. Broadcast does not cross routers; Tools → Connect to Address adds a PC by IP or hostname.

Activation

Site code

Set one alphanumeric site code in the Controller (Help → License Information), or read how licenses work. Clients store only the hash. Clones keep the code and get a new device ID. How to use a license.

Updates

Portal feed

The console downloads the latest suite from this portal and can push it to selected clients. Failed binary updates restore the previous file.

Activation does not phone home. Desktop apps can send crash reports to this portal when it is reachable. Operators manage licenses, installers, and those reports from Admin.

Install the suite,then open the room.