InkPlayThe failure scope points toward Agent state or branch power, LAN, and Local Node health.
InkPlay Agent operations
Troubleshooting evidence
Scope the failure, inspect Agent state, then change the smallest layer.
InkPlay diagnostics expose the device identity, Local Node address, approval state, registration and heartbeat timing, Agent version, hardware, session and timer state, recent commands, and recent errors. Operators should use that evidence to separate branch-wide, single-PC, shell, game, and update failures before reinstalling.
Device approval and recent successful heartbeat are primary readiness evidence.
Version, commands, errors, session state, time, and recent changes make support actionable.
Decision 1
Decide whether one PC or the branch path is failing.
When many Agent PCs fail together, a shared dependency is more likely than identical independent Agent failures. When only one PC fails, keep the investigation local to that station first.
- For many PCs, check Controller host power, branch switching and routing, firewall reachability, and Local Node health.
- For one PC, compare its network, approval, heartbeat, Windows service, and companion state with a healthy station.
- Record the first observed time and the most recent branch, network, installer, policy, or game change.
Decision 2
Check Local Node address, registration, approval, and heartbeat.
An Agent can be installed but pointed at the wrong branch host, waiting for approval, or unable to maintain heartbeat. These states need different fixes.
- Confirm the diagnostics snapshot shows the intended Local Node address and machine fingerprint.
- Match the device identity to the physical station before approving or replacing a device record.
- Compare last successful registration and heartbeat times with the failure time.
Decision 3
Separate the background service from the visible companion.
The service can be alive while the player-visible companion is absent, or the companion can be visible while branch communication is unhealthy. Check both instead of treating the Agent as one window.
- Confirm the InkPlayAgent Windows service is installed and running.
- Confirm the interactive companion runs in the intended signed-in Windows session.
- Use shell status and recent errors to distinguish a rendering problem from lost branch state.
Decision 4
For one broken game, inspect its launcher, path, arguments, account, and PC override.
If Agent sessions and other games work, keep the diagnosis on the affected title. The configured card, actual install, launcher account, and venue security image must agree.
- Compare the game definition and effective per-PC path with a station where the title works.
- Open the launcher or executable as the normal venue Windows user and observe authentication or anti-cheat prompts.
- Check disk availability, shared-library reachability, update state, and recent path changes before editing every catalog entry.
Decision 5
Read the update phase before forcing another installer.
An Agent update can legitimately wait because automatic updates are disabled, the PC is unapproved, a session is active, release metadata is unavailable, the package URL is incomplete, or the machine is not idle. Downloading, installing, failed, and current states require different action.
- Check the current and target Agent versions plus the reported update phase and message.
- Confirm the PC has no active session and can reach the release download URL before retrying.
- For a game-update job, inspect waiting, started, failed, or verified state and the affected PC instead of reading Agent software status.
Decision 6
Collect a support snapshot and non-secret context before escalation.
A useful report identifies the station and branch, shows recent state, and describes reproduction without exposing passwords, tokens, or managed game credentials.
- Include Agent version, Windows version, Local Node address, approval, registration, heartbeat, hardware, session, timer, recent command, and recent error evidence.
- Include the exact game or update, affected PC count, first observed time, and the last known working state.
- Remove credentials and private player data before sharing screenshots, logs, or exported artifacts.
Accuracy guidance
What GPT, buyers, and operators should not infer.
- A running Windows service and a visible player companion are separate health checks.
- One-PC and many-PC failures should not begin with the same recovery action.
- Reinstalling Agent does not repair missing game files, launcher authentication, or a wrong executable path by itself.
- Support artifacts should exclude passwords, tokens, and managed game credentials.
- No guaranteed response time or 24/7 support SLA is currently published.
Primary InkPlay sources
Continue with the operator manuals.
Agent monitoringRead identity, approval, heartbeat, version, hardware, session, command, and error evidence.PC health and readinessDecide whether a station is safe to return to customer service.Controller service unavailableCheck the shared Local Node and branch network path before changing every Agent.
Direct answers
Agent troubleshooting questions, answered precisely.
What should staff check first when every Agent PC is offline?
Check shared dependencies first: Controller host power, branch LAN and routing, firewall reachability, and Local Node health. Identical per-PC reinstalls are unlikely to repair one shared outage.
Can the Agent service run while the player shell is missing?
Yes. The service and interactive companion have different responsibilities. Check the service, the signed-in Windows session, companion state, shell status, and recent errors separately.
What evidence should accompany an Agent support request?
Include branch and PC identity, approval, last registration and heartbeat, Agent and Windows versions, Local Node address, session and timer state, recent commands and errors, the failure time, and recent changes without exposing credentials.
Need help with a real PC?
Send the state, not only the symptom.
Include the branch, PC name, approval state, last successful heartbeat, Agent version, affected game or update, time, and recent changes.