Diagnose Google Workspace, Windows, Microsoft Office, school networks and interactive displays. Find practical guides for device management, update failures, shared systems, technical escalation and IT knowledge workflows.
Diagnose sign-in, permissions, browsers, shared devices and school-wide Workspace problems.
↓Work through failed updates, repair tools, Windows services and Office installation problems.
↓Investigate filtering, proxy behaviour, school networks and shared classroom computers.
↓Identify panels, configure EDLA, manage permissions, firmware and myViewBoard Manager.
↓Use Gemini, Gemini Notebook and Gems for documentation, support and repeatable IT workflows.
↓Capture useful technical information before involving Google, Microsoft or another support team.
↓Diagnose account, browser, permissions, performance and device issues before deciding whether a Workspace problem is local or school-wide.
Work through Windows Update failures, repair components and services, then handle common Microsoft Office update and installation problems.
Use these guides when a problem appears to be linked to the school network, web filtering, shared computers or shared classroom panels.
Configure ViewSonic panels, manage EDLA permissions and firmware, and prepare classroom displays for reliable school use.
Use AI to organise technical knowledge, turn troubleshooting notes into reusable guidance and create repeatable support workflows.
Collect enough information to make the next support conversation useful instead of starting the investigation again from the beginning.
Good troubleshooting starts by identifying whether the failure belongs to the user, device, application, network or wider school environment.
Confirm whether the issue affects one user, one device, one classroom or multiple users across the school.
Record the exact error message, error code, device model, operating system and application version where relevant.
Check whether account policies, proxy settings, firewall rules, web filtering or device-management settings could be controlling the behaviour.
Before making a wider change, test the proposed fix on a limited number of devices and keep a record of what was changed.
Send us the affected system, device or application, the scope of the issue, exact error details and the troubleshooting already completed.