NFG Connect 0.6
Attended remote test guide

General installation and management tests · Dashboard

Experimental implementation — native Windows validation pending.

This build adds a real HTTPS relay and Windows capture/input code. It is not a certified TeamViewer replacement. Test with harmless files and Notepad only. Do not use vehicle programming, passwords, customer records or payment data. USB-over-IP/J1939 is still unavailable. No administrator elevation or firewall changes are requested.

Prepare two endpoints

  1. Customer: a Windows 10/11 Intel/AMD PC with .NET Framework 4.8, v0.6 installed, enrolled, syncing and awake. Close sensitive windows. Open Notepad before starting.
  2. Operator: another computer with a browser, signed in as the technician/admin who issues the code. Test on different internet connections after the first basic test succeeds. No VPN or inbound ports are needed for this HTTPS test relay.
  3. Both accounts must already have site-sharing access and an activated Connect role. The existing site remains private. A SESSION code does not grant site access. Create a disposable customer request, assign the technician, and pair the customer PC. Never copy one enrollment to two machines.
  4. Create a harmless small text file on each endpoint. Each must be no larger than 128 KiB (131,072 bytes). Use names such as customer-test.txt and operator-test.txt.

Start a fresh live test

  1. Operator: open Session permissions. Choose the active request and requested features, then generate a new SESSION code.
  2. Customer: open Session permissions in Windows, review the code and operator, choose only the permissions to grant, and approve. Approval by itself is still just a plan.
  3. Customer: read the second LIVE access confirmation. Choose Yes to start. The app generates a new in-memory session secret; old plans and old app approvals do not automatically start sessions.
  4. Operator: refresh Permission history and click Open live test, then Connect to customer-approved live test. Connect within 50 seconds of the customer's confirmation.
  5. Keep the customer present. Only the issuing operator can view or operate this session. An unrelated administrator cannot take it over. New sessions require a new code and local confirmation.

Emergency stop: customer presses Ctrl+Shift+F12 or clicks STOP SESSION. When input is blocked, press Ctrl+Alt+Delete to release it. Then return and stop. If the emergency shortcut cannot register, the app refuses the live test.

Run and record R01–R07

IDAction and expected result
R01
View / control
Verify the operator sees the customer's primary display. Click Notepad and send harmless text, Enter and Backspace. Right-click once. Expect low-frame-rate images and basic input, not video streaming. No dragging, scrolling, clipboard, shortcut chords, UAC or secure-desktop control. NFG's own consent controls must reject remote input. Record errors rather than elevating the app.
R02
Files
Operator offers a small file. Customer chooses a NEW destination. Compare content; the receiver verifies SHA-256. Decline a second offer. Try an oversized file: it must fail. Try an existing destination: it must not overwrite. Customer clicks Choose a file to send; operator downloads it and verifies content. No directory browsing or arbitrary remote file paths are exposed. Never execute a received file during this test.
R03
Privacy
Requires Windows 10 build 19041+ or Windows 11. Operator enables privacy; customer confirms EVERY connected display has the black NFG overlay. Verify the operator still sees the desktop, not a black frame. Turn privacy off before input tests. Stop and network-loss tests must remove overlays. This is an experimental overlay, not a hardware display-off or secure-desktop privacy guarantee. Hot-plug, multiple monitors, mixed DPI and fullscreen apps need separate qualification.
R04
Input blocking
Request one 10-second input-block test. If Windows denies BlockInput, record BLOCKED and the message; do not disable Windows protection. If accepted, local input must resume within 10 seconds. In a NEW session repeat and press Ctrl+Alt+Delete early: input must release. A second block command in the same session must be refused. The input worker releases independently of the UI timer and on worker exit.
R05
Stop / loss
Test local Stop, Ctrl+Shift+F12, operator Stop and closing the operator tab in separate sessions. Disconnect the customer's network: local display/input must restore after at most 10 seconds without a successful relay response (input block is independently capped at 10 seconds). Closing the operator tab stops the session after about 20 seconds without its heartbeat. No session resumes automatically. Record actual timings.
R06
Limits / isolation
Approve screen viewing only: control/files/privacy/block must be absent and refused by the API. Approve a subset of a larger request. Let a session expire: v0.17 sessions have no fixed duration; disconnect either endpoint to check heartbeat cleanup. Old codes/consents cannot restart it. Reassign/close the ticket or revoke enrollment during a disposable test: operations must stop on the next check. An unrelated operator must receive an access error.
R07
Lifecycle
Test Windows lock, sleep/wake and exiting NFG Connect. Session must end and displays/input restore, with fresh consent needed to reconnect. Repeat privacy with each monitor configuration. A hung process is not a passing test: use Ctrl+Alt+Delete / Task Manager, record it as FAIL, and send the observed behavior.

Limits and data handling

Report back

Run Run-Tests.cmd and complete Test-Results.csv. Send Report.txt and the completed CSV from Documents → NFG-Connect-Test-Reports. For each failure, include the test ID, Windows build, what happened, exact message and time. Do not send enrollment files, passwords, device keys, session secrets or unused access codes.