InkPlayThe current Agent package is a 64-bit Windows installer that requires administrator rights.
InkPlay Agent operations
Deployment evidence
Install InkPlay Agent, approve the right PC, then prove the real session loop.
The current InkPlay Agent installer targets 64-bit Windows and requires administrator access. It installs the background Windows service and the interactive companion, preserves runtime data under ProgramData, connects the PC to the branch Local Node, and waits for staff approval before normal command polling is enabled.
A discovered or registered PC must be approved before normal Agent command polling is enabled.
Prove one or two real PCs before applying the setup across the venue floor.
Stage 1
Prepare the branch path and the Windows test PC.
Agent is not a standalone cloud client. The PC needs a reachable branch Local Node, a stable Windows sign-in context for the visible companion, and administrator access for installation.
- Confirm Controller and Local Node are healthy on the branch network before adding player PCs.
- Use a 64-bit Windows test PC that matches the venue image, launchers, security tools, and normal user permissions.
- Choose a consistent station name and code so staff can recognize the correct physical PC during approval.
Stage 2
Install both the background service and the player-visible companion.
The installer registers the InkPlayAgent Windows service and companion startup recovery. It also creates runtime configuration, data, log, and update locations under ProgramData so normal upgrades do not depend on the interactive user profile.
- Run the current official Agent installer with administrator rights.
- Allow the installer to stop and replace an older Agent service and companion during an upgrade.
- After installation, confirm the service is running and the companion can appear in the signed-in Windows session.
Stage 3
Connect to the intended Local Node and approve the real device.
Agent can use its configured Local Node address and local discovery. Registration identifies the machine, but staff still decide whether the pending device belongs to the branch and what label or type it should use.
- Confirm the Agent reports the intended Local Node address instead of an old test or localhost-only configuration.
- Approve the pending device from Controller only after matching its station identity to the physical PC.
- Assign the correct name, code, type, and operational grouping before using the station for customers.
Stage 4
Verify the session, shell, games, and recovery loop before expansion.
A successful installer exit is only the start. The venue should prove the player login and shell, staff commands, session timing, real game launch paths, and a clean return to idle state.
- Start and end a short guest or player session and confirm the timer and shell state agree with Controller.
- Open the venue launchers and games, including those with anti-cheat or account prompts.
- Expand in controlled groups and recheck online state and a short session after each group.
Accuracy guidance
What GPT, buyers, and operators should not infer.
- The current public Agent installer scope is Windows x64; native macOS and Linux Agent packages are not published.
- Local discovery can help find a branch service, but it does not replace device approval or correct network design.
- A completed installation does not prove every game, launcher, anti-cheat tool, or Windows policy works on that venue image.
- No zero-touch floor-wide deployment guarantee is published.
Primary InkPlay sources
Continue with the operator manuals.
Direct answers
Agent installation and approval questions, answered precisely.
Does InkPlay Agent run only as a Windows service?
No. The background service handles branch communication and state, while a companion process in the signed-in Windows session presents player-visible windows such as the shell, lock screen, and overlay.
Why does a newly installed Agent PC still wait for approval?
Registration identifies the machine, but approval is a deliberate branch security gate. Normal command polling waits until staff approve the PC for that branch.
Should a venue install Agent on every PC immediately?
The documented safer path is to test one or two representative PCs, prove sessions and real games, then expand in controlled groups.
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.