Tiaris guide
Troubleshoot common problems
Choose the right checks for sign-in, installation, computer health, deployment, and Nest problems.
Start with the selected organization, exact resource, and visible instruction. Different problems can share a warning badge while requiring different recovery actions.
A computer is waiting for approval
Section titled “A computer is waiting for approval”- Open Computers > Add computers.
- Match the pairing code with the physical computer.
- Review its Blueprint, hardware, and exact disk.
- Approve only the matching computer and intended action.
If the pairing screen never appears, follow Network boot problems. If the codes do not match, leave the computer unapproved.
A computer is not checking in
Section titled “A computer is not checking in”Check power, Ethernet/network access, and Last seen. Allow a recently restarted computer to reconnect. Confirm that it can resolve and reach the organization’s Tiaris address.
An offline target retains its current system. Queued work is not proof that it has applied a change. Inspect its current operation and diagnostics after contact returns.
A Blueprint change is not reaching computers
Section titled “A Blueprint change is not reaching computers”Open Deploy. Confirm that you prepared and released the intended version, created the plan, and chose Approve and start. Saving a draft, preparing files, or releasing a version alone does not update computers.
Check exact assignment and scope. Offline targets wait safely; a runtime, Nest, or delivery prerequisite can block later stages. Read Deployment and desktop problems for the next action.
A setting is missing or looks unchanged
Section titled “A setting is missing or looks unchanged”Check whether it belongs to the Policy or Blueprint, whether the selected desktop supports it, and whether the installed runtime supports its capability.
Verify the system configuration separately from the visible desktop. Pending sign-in asks for a new workstation sign-in. Unobservable means the session helper could not observe that desktop; it does not establish drift. See the settings reference and diagnostic checks.
Nest is offline or needs attention
Section titled “Nest is offline or needs attention”Open Nest from its card on Home. For an offline server, check power and the approved wired connection. For another issue, follow Needs attention and its offered action when present.
Nest handles normal runtime synchronization, preparation, cache recovery, and local-service repair automatically. Record a persistent issue and its time for support. A connected Nest can still have a degraded capability; check Computer setup files before an installation.
Console sign-in or email verification fails
Section titled “Console sign-in or email verification fails”Confirm the account email, use a fresh reset/verification link, and check mail delivery with your administrator. For two-step sign-in, use an unused recovery code when email is unavailable. Missing membership requires an Owner/Manager’s help.
Follow Sign in securely for recovery. Workstation directory sign-in is a separate configuration: use the directory guide and its provider-specific tests.
A wireless connection fails
Section titled “A wireless connection fails”Review the deployed network version, SSID, security/EAP method, identity, trusted CA, and RADIUS name constraint with the network administrator. Keep a working connection while collecting evidence. See Wi-Fi and certificates.
Escalate with evidence
Section titled “Escalate with evidence”Record the affected resource, time, expected result, actual result, and visible reason. Use the relevant diagnostics and support checklist. Keep the original failure distinct from any subsequent rollback or recovery failure.