Topic 1 of 6

#Before using a remote tool

Topic 2 of 6

#Status, clock and storage

BrightBridge remote player status summary with refresh, health and uptime indicators
Start with the read-only rDWS summary. Refresh once, then use Health and Uptime to decide whether a deeper check is justified.
ToolUse it to
StatusRefresh the available player summary
ClockCompare player time with the expected local time
TimezoneReview or apply the approved timezone
StorageCheck whether limited device space may affect playback

A timezone change may require a reboot before every application reflects it. Schedule that reboot rather than surprising viewers.

Topic 3 of 6

#Snapshot and ping

Click-by-clickRun one safe ping check
PlayersChoose one playerPlayer ToolsPing
  1. 1
    Player heading

    Read the player name again. This check runs on that player only.

  2. 2
    Ping 8.8.8.8

    Press the button once. Do not click repeatedly while it is working.

  3. 3
    Result

    Wait for success, failure or timeout. Copy the exact result and time if it fails.

You are finished when you have one finished result for the correct player and know whether to continue or escalate.

A failed ping does not prove the player itself is broken; it is one clue.

BrightBridge Ping panel with a Ping 8.8.8.8 button
Ping is a lightweight connectivity check. Press it once, wait for the returned result and record the exact message if it fails.
  • Use a snapshot to confirm visible output without starting continuous video.
  • Treat an old or blank snapshot as evidence to investigate, not proof of a single cause.
  • Use ping or a lightweight status refresh to test responsiveness before rebooting.
  • Capture only what is required for support and follow your organisation's screen-content privacy rules.
Topic 4 of 6

#Player logs

  1. 1
    Reproduce the issue once if doing so is safe.
  2. 2
    Refresh the player log view.
  3. 3
    Match messages to the reproduction time.
  4. 4
    Copy only the minimal relevant, non-sensitive lines into an escalation.
  5. 5
    Record the player label and the time separately.
Topic 5 of 6

#Liveview

Click-by-clickLook at one screen remotely
PlayersChoose one playerLiveview
  1. 1
    Player heading

    Confirm the player name before opening the viewer.

  2. 2
    Balanced

    Choose Balanced first. Use Sharp only when you must read small detail.

  3. 3
    Start Liveview

    Press once, then wait. Starting can take a moment.

  4. 4
    Viewer

    Check only what the task requires. Do not copy private screen content.

  5. 5
    Stop

    End the session when the visual check is complete.

You are finished when you have confirmed the intended screen and the Liveview session is stopped.

Liveview is continuous. Prefer a single snapshot when a still image answers the question.

Liveview provides a continuous remote view when the player and organisation support it. Start one session, wait for its connection state and close it when the check is complete.

BrightBridge Liveview controls showing quality choices and Start Liveview
Choose the lowest quality that answers the question, select Start Liveview once and wait inside the viewer. Use Sharp only when small on-screen detail matters.
StateOperator response
StartingWait; do not click repeatedly
ConnectedConfirm the intended screen and complete the visual check
DirectThe viewing path connected without a relay
RelayThe viewing path connected through an approved relay
FailedCapture the message and try a snapshot before escalating
Topic 6 of 6

#Reboot only when justified

  1. 1
    Record the pre-reboot symptom and time.
  2. 2
    Confirm the player identity and location.
  3. 3
    Issue one reboot and wait for the player to return.
  4. 4
    Verify fresh activity and expected playback.
  5. 5
    Escalate if it does not return within the normal site window.