Tiaris guide
Network boot problems
Diagnose a computer that cannot find Nest, load installation files, or reach its pairing screen.
Use this guide before approving installation. Network boot, pairing, preparation, and disk authorization are separate steps.
The computer cannot find a network boot option
Section titled “The computer cannot find a network boot option”Confirm x86-64 UEFI boot, a supported wired adapter, and the approved firmware configuration. Choose the adapter from the firmware’s boot menu. Legacy BIOS and other unadvertised architectures do not use the automatic discovery path documented here.
Ask your hardware/network operator for the appropriate firmware settings. The Nest appliance’s ISO is not a workstation installer.
DHCP works but no Nest menu appears
Section titled “DHCP works but no Nest menu appears”- Confirm the computer and Nest are on the intended wired VLAN.
- Check Nest’s current health and setup-file readiness from Home > Open Nest.
- Have the network administrator check DHCP guard/snooping, relay configuration, UDP 67/4011, TFTP, and HTTP delivery against network requirements.
- Check for another PXE service. Coordinate its authoritative boot setup with the operator.
Do not replace the DHCP server or disable network protections simply to make a boot menu appear. Routed VLANs need an approved boot-discovery/relay arrangement.
A boot file loads but installation stops before pairing
Section titled “A boot file loads but installation stops before pairing”Record the exact screen and approximate time. Verify that the boot path uses the organization’s intended Nest and current signed setup files. Check the Tiaris address’s DNS/HTTPS reachability from the installation network.
A working cached file alone does not establish that current enrollment authority and management connectivity are available. Ask the operator to inspect the retained boot/session evidence when the computer cannot proceed.
The Console cannot check setup-file readiness
Section titled “The Console cannot check setup-file readiness”Getting ready describes ordinary reconciliation. Needs attention identifies a reported problem. Could not be checked means current evidence is unavailable. Keep those states separate.
A failed candidate update can leave verified active setup files available. Use the actual readiness shown for installation rather than assuming every historical failure disables booting.
Pairing appears, but the computer is absent
Section titled “Pairing appears, but the computer is absent”Check the selected organization and open Computers > Add computers. Refresh once after the new boot. Compare the physical pairing code with the pending entry.
If another organization or unknown Nest is involved, leave the computer unapproved and contact the operator. Never use a similar name or a different pairing code as a substitute for the matching identity.
Exact installation preparation is taking time
Section titled “Exact installation preparation is taking time”Keep the computer online and follow Preparing exact installation on Nest. Preparation can be reused for equivalent hardware/configuration after it has been verified. A new hardware/configuration combination can require fresh work.
Read the current stage and blocker. Restart only when the operation permits it. Use the support checklist when progress does not converge, including the pairing code, machine identity, Nest name, time, and visible stage.