How to build a repeatable check for office PCs

When office computers behave differently, it is hard to tell whether one has a real fault or the tests were run under different conditions. A repeatable check gives you a consistent way to spot problems before rollout, after repairs, or when a staff member reports an issue.

Use Test Everything to run the available browser tests on each computer and get a report. Then record the conditions and results in the same format each time, so you can compare like with like.

Run the same check on each PC

1. Open Test Everything on the computer you are checking. It guides you through available tests step by step and produces a report. Run the check on the actual PC, not a different computer used for remote access.
2. Set a consistent starting condition. Use the same browser where possible, connect laptops to power, close ordinary work apps, and let the computer sit idle for a few minutes. Do not change power, security, or performance settings just to get a better result.
3. Decide which accessories are part of the standard setup. For a docked workstation, use the same dock, monitor, keyboard, mouse, and network connection for each check. If you are checking the PC itself, test once without optional accessories, then test the docked setup separately.
4. Follow the test sequence and respond to permission prompts when a camera or microphone check needs access. If a prompt is denied or a test is unavailable, record that separately from a test that runs and shows a problem.
5. Make a record for each computer. Note its asset label, date, operating system, browser, power state, connected accessories, network type, and any unexpected result or symptom. Keep the notes in your approved internal system, and include only details your team needs.

Use the same sequence on every machine. If a test fails, note what happened before changing settings, then troubleshoot and repeat that test under the original conditions.

What the results mean

The same problem appears on repeated checks

A result that repeats under the same conditions is more useful than a single unusual reading. For example, if the same key fails every time or the same screen area shows a defect in repeated checks, record the symptom and the test conditions. Move on to an isolated check of that device or component.

A result changes from one run to the next

Variation can come from background work, heat, power mode, a loose cable, or a connection that drops briefly. Repeat the check after returning the computer to the standard starting condition. If the issue occurs only while a particular accessory or network connection is in use, include that condition in your notes.

A test is unavailable or cannot get permission

This does not prove that the hardware is broken. The browser may not support the feature, the computer may not have that hardware, or a browser or operating-system permission may block access. Record it as unavailable or blocked, then check the relevant settings before treating it as a fault.

Two PCs have different scores

A difference is not automatically a defect. Computer models, power limits, connected displays, browser versions, and background activity can all affect results. Compare a PC with its own earlier baseline first. Use comparisons between different models as clues, not as proof that the slower computer is faulty.

How to fix a result that does not look right

1. Check the physical setup. Confirm that cables are fully seated, the monitor is on the correct input, and any headset, keyboard, or mouse is connected to the intended port. If a test involves an accessory, connect it directly to the PC to see whether a dock or hub changes the result.
2. Close other apps and restart. A meeting app, recording program, or background update can use a camera, microphone, or system resources. Close ordinary apps, restart the computer, and repeat the check before changing drivers or settings.
3. Allow the browser to use the device. Check the site permission from the icon beside the browser address bar. On Windows 11, open Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone for the relevant device. On macOS, open System Settings › Privacy & Security › Camera or System Settings › Privacy & Security › Microphone, then allow the browser if it is listed.
4. Check the selected sound device. If an audio test uses the wrong input or output, select the intended device in system sound settings. On Windows 11, go to Settings › System › Sound. On macOS, go to System Settings › Sound. Then run the test again and note which device was selected.
5. Repeat once in the standard browser. Keep the same accessories and power state. If a test works in another browser but not the standard one, check browser updates, permissions, and extensions before assuming there is a hardware fault. Keep the original browser in your routine so later checks remain comparable.
6. Update or escalate the affected device. If the fault remains, install approved operating-system and device updates, then repeat the relevant test. If it still fails, send your support team the repeatable symptom, the conditions, and the checks already tried.

When it may be a hardware fault

A problem is more likely to be physical when it repeats after a restart and permission checks, follows the same device across connections, or changes when a cable or port is moved. Where practical, connect the accessory to another known-good computer or substitute a known-good accessory. Change one thing at a time so you can identify what affects the result.

If the issue follows a keyboard, mouse, headset, or cable to another computer, replace it or use the warranty process. If it stays with one PC when known-good accessories are connected, document the test results and arrange hardware service. A browser check can identify a symptom, but it cannot inspect internal components or confirm the cause.

Keep the check comparable over time

Save a simple checklist with the order of tests and the starting conditions. Use it for the same milestones, such as before deployment and after a repair, rather than rerunning every test whenever a minor issue occurs. A baseline is a record of results from a known, repeatable condition. It helps you notice change on one computer without expecting every PC to produce identical scores.

Some checks measure the computer locally, while network speed checks exchange test data with our server to measure the connection. Run those network checks on the same type of connection when comparing results, and note whether the PC was on Wi-Fi or Ethernet. A network difference may be caused by the connection or office traffic, not by the computer itself.