Tiaris guide
Requirements and networking
Check accounts, hardware, installation media, and network access before setting up computers.
Tiaris manages NixOS workstations. The Console is a web application; a workstation’s managed operating system and runtime are separate from the browser you use for administration.
Accounts and access
Section titled “Accounts and access”Use the Tiaris HTTPS address supplied by your administrator and a current browser. Your membership in the selected organization determines what you can read or change. See roles and permissions.
Have access to the email address associated with your account for invitations, email verification, password recovery, and email-based two-step verification.
Workstation hardware
Section titled “Workstation hardware”For the documented network-installation path, use a computer with x86-64 UEFI network boot and a wired network adapter supported by the signed workstation runtime. Automatic boot discovery covers IPv4 UEFI x86-64; it does not advertise legacy BIOS, ARM, IA32, or IPv6 boot support.
Your operator should confirm memory, storage, GPU, and application requirements for the selected Desktop Experience. Tiaris detects hardware and may offer a driver choice during approval. Review that choice rather than assuming every computer uses the same driver.
Keep the computer connected to power throughout installation. Identify the intended internal disk and disconnect unrelated removable storage where practical. Installation replaces the selected disk’s contents.
When Nest is needed
Section titled “When Nest is needed”Nest is a local installation and software-delivery appliance. The normal new-workstation installation described here requires a ready Nest. Existing managed computers can operate without a local Nest where the organization’s delivery policy permits it. Adoption of an already-installed system is a separate approval choice; it is not a general installer for another operating system.
The Nest appliance ISO installs Nest itself. It cannot install an ordinary workstation. Workstation files are supplied by Nest over the network; there is no workstation USB or ISO download in this workflow.
For Nest installation, use the approved appliance hardware, wired Ethernet, and the firmware configuration in Downloads, including disabling Secure Boot for that appliance installation. Confirm the installation disk before erasing it.
Network checklist
Section titled “Network checklist”For a straightforward first installation, put Nest and the computer on the same wired VLAN with working IPv4 DHCP. Nest supplies boot discovery while the existing DHCP server continues assigning addresses.
Ask your network administrator to check:
| Requirement | What to check |
|---|---|
| Address assignment | The existing DHCP service gives both machines suitable IPv4 addresses. |
| Local boot discovery | UDP 67 and 4011 can reach Nest’s approved interface. DHCP guard or snooping trusts the appropriate Nest switch port. |
| Boot files | TFTP starts on UDP 69 and uses negotiated transfer ports; HTTP boot delivery uses TCP 80. |
| Management connection | Nest and workstations can resolve and reach your Tiaris HTTPS address. |
| Software sources | The allowed sources match the organization’s delivery policy. Ask the operator which endpoints are required. |
| Directory sign-in | The selected identity provider is reachable, and any LDAP, certificate, or DNS requirements are satisfied. |
These ports describe the local boot path; they are not instructions to expose Nest publicly.
Other VLANs and existing PXE services
Section titled “Other VLANs and existing PXE services”Routed VLANs require an appropriate local Nest, relay configuration, or explicit DHCP boot options. A matching IP prefix alone does not prove that two machines share a VLAN.
Coordinate any existing PXE service with your operator. Nest can coexist with an externally managed boot setup, but unrelated boot responders must not compete for the same computers. Do not replace the organization’s DHCP configuration simply to try an installation.
What happens during an outage
Section titled “What happens during an outage”An installed workstation keeps its activated system when Tiaris or Nest is unreachable. Offline sign-in depends on the deployed Policy and sign-in source. New installations and updates need their required services and verified files; cached software does not guarantee that every network-boot or sign-in step works offline.
Read network boot troubleshooting if a computer never reaches the pairing screen.