LINUX DESKTOP PILOT WORKSHEET — Yenra, September 5, 2026
https://yenra.com/linux-enterprise-desktop/

SCOPE
User role / pilot participants / duration / representative tasks:
Distribution and release / hardware configurations / firmware / accessories:
Application support sources / operating-system support / internal support owner:
Critical workflows that must pass before rollout:
Accepted workarounds and who can approve them:
Provisioning, identity, encryption, management, update, and recovery baseline:

TEST RECORD — repeat for each workflow and relevant configuration
Task / owner / frequency / business consequence if unavailable:
Applications, versions, integrations, document formats, and peripherals:
Test data approved and sensitive details removed:
Expected result and acceptance criterion:
Steps performed and evidence:
Actual result / elapsed time / support time:
Pass / blocker / workaround / unresolved:
Issue, reproducibility, responsible person, and due date:
Retest and acceptance authority:

INCLUDE THESE TESTS
Representative document round-trip including required macros/formulas/layout.
Meeting service: camera, microphone, audio, screen sharing, reconnect.
Dock, displays, printer/scanner, wireless, Bluetooth, suspend/resume.
Disconnected work, reconnect, policy refresh, credential changes, account removal.
Update deployment, remote support, rebuild, data restore, lost-device response.

FICTIONAL EXAMPLE
Six users, two laptop configurations, three weeks. Fourteen of fifteen required
workflows pass: 14/15 = 93.3%. Label printing fails and blocks dispatch.
Decision: do not expand until a supported fix or accepted alternative passes.
The overall percentage does not override a critical unmet requirement.

ROLLOUT DECISION
Passes / blockers / unresolved risks / accepted workarounds:
Training, support, migration time, accessories, continuing remote-app costs:
Approval / next group / fallback / review date: