Skip down to the research record

Rep laptop checks before corporate access: 3 tests

Quota Forecast Editorial Team · Published · 13 min read

Why the laptop check belongs before the call

Before a forecast call, check three device facts on each rep's laptop: OS version, access client version, and hardware key protection. A forecast call is where a revenue leader needs pipeline numbers that are current and that people trust. Reps often open the CRM, a shared forecast sheet, or a deal review tool during the call itself.

Key takeaways

  • Check the operating system version against the vendor's supported list and the access client's minimum.
  • Read the access client version from the device and compare it with the minimum for that platform.
  • Confirm that a Windows laptop has a TPM at version 2.0 or later, or that a Mac has Apple silicon or a T2 chip.
  • Date each result, and rerun the checks after updates.

If one of those sessions starts from an out-of-date laptop, the problem is bigger than a slow connection. The device may be missing security fixes, or it may run an access client too old to enforce your company's rules.

This post walks through the three checks and explains how to run them before a rep's laptop reaches corporate systems. We follow one example through the operating system, access client, and hardware sections. The rep is hypothetical, but the situation is common. The rep uses a Mac for travel, has not thought much about updates, and wants to join Monday's forecast call from that laptop. Nobody has asked whether the laptop still meets the bar.

Each check asks a yes-or-no question, and each can be tied to a published source. The sources give minimum versions and named features. Your company's policy decides what happens to a laptop that fails. This post does not replace that policy. It gives a revenue leader a short list of questions to ask before the call, and a way to get clear answers.

The operating system check

Start with the operating system, because the other checks depend on it. The UK National Cyber Security Centre's guidance for Windows says that "Windows devices receive software updates regularly, and major updates once or twice a year." (NCSC device guidance for Windows) A device that has skipped several of those updates carries known gaps, and a forecast call is a poor time to find out what they are.

The same guidance advises organisations to "use Microsoft's Windows lifecycle fact sheet to plan upgrades and ensure devices remain on supported versions of Windows." For a Windows laptop, that turns a vague worry into a concrete question: is this exact version still on the vendor's supported list? If it is not, the laptop fails, and the rep needs an upgrade or a replacement before the call.

The same page also says the guidance does not apply to any specific version of Windows, but was last tested on Windows 11 25H2 Enterprise, which has more features than some other versions. Two things follow. The guidance was tested against a specific recent build, so it is a fair reference point. Releases also differ, so note the release name as well as the version number. A less complete release may lack features the guidance assumes are present.

Collecting this information rarely needs special tools. Ask the rep to read the exact name and version from the screen, then compare that with what IT's management records show for the same device.

Write down the full version string, not a rounded label such as "recent." A rounded label cannot be compared with a minimum, and the later checks depend on that comparison. "Recent" can describe a laptop that is three releases behind, and it can describe one that passed yesterday.

Macs need the same discipline, even though the Windows guidance does not cover them. Note the macOS version, then compare it with the minimum the access client requires, covered in the next section. Do not assume an older release is fine because the laptop starts and loads a browser. Check the lifecycle information the vendor publishes for that release, and treat an unsupported macOS release the same way you treat an unsupported Windows build.

In our example, the Mac runs an older macOS release. The minimum in the next section is macOS 12, and the laptop's release is below that, so this check fails. If the Mac supports a newer release, the rep can update before the call. If it does not, the laptop needs replacing, and that conversation should start now, not on the morning of the call.

The access client check

Next, check the software that decides whether a device can reach corporate resources at all. In this example we use Duo Desktop. The Duo Desktop user guide says the product "reduces risk by ensuring compliance of corporate devices to business standards and provides visibility into personal devices before granting them access to corporate resources." (Duo Desktop user guide) That is the job this check protects. A device that misses the standard should not get through just because the rep knows the right password.

The guide sets the minimum operating systems in one line: "Your device must be running macOS 12+ or Windows 10 build 1803+." This is an additional floor for the operating system check, applied on top of the supported-list test. A Windows laptop on Windows 10 must be at build 1803 or later. A Mac must run macOS 12 or later. Either way, the test is a number you can read off the device, which is why the exact version string matters.

The same guide sets the minimum client version: "Duo Desktop 6.12.0+ installed on Windows or Duo Desktop 6.12.0.0+ installed on macOS." The two minimums use different formats, one with three parts and one with four. Copy the format exactly as the vendor writes it into your record. A checker who rounds, retypes, or drops a digit can pass a laptop that should fail. Compare the installed version only with the minimum for that platform, never with the Windows figure when the device is a Mac.

Keep the client's name exactly as the vendor writes it, too. Similar tools have similar names, and a record that says only "the VPN app" invites a mix-up.

The guide also excludes two kinds of software. It says that "Duo Desktop does not support earlier versions of Windows or macOS beta versions." For your check, a Windows release older than the minimum fails, even if the rep prefers that laptop and says it works. Beta builds of macOS fail too, even when the version number looks new. If a rep has joined a beta program on the laptop meant for the call, move that laptop to a release build before the call rather than debating the version number.

The client needs a check of its own, separate from the operating system. Installed software is easy to forget. A rep may have installed the client years ago and never updated it, or may still have a copy left from an older setup. Check the version on the device itself, not the version the rep remembers, and not the version IT last pushed to a different machine.

In our example, the Mac already fails the operating system check. Even after the rep moves to a supported release, the client version still has to be read from the device. The check is complete only when both the operating system and the client pass on the same laptop, on the same day.

Pay attention to what happens after an update. An operating system upgrade can change which client version is compatible, and a client update can leave older settings in a state nobody has reviewed. After any upgrade, read the installed client version again and confirm it still meets the minimum. A pass recorded before an upgrade does not carry forward.

The hardware key check

The third check asks whether the laptop protects its encryption keys in hardware, not only in software. The UK National Cyber Security Centre's device security principles for manufacturers explain why this matters. Storing cryptographic roots of trust "in a secure component, such as a TPM (trusted platform module, at least version 2.0) or a trusted execution environment with hardware-enforced isolation, can protect cryptographic secret keys from an attacker by ensuring they remain encrypted until required by an authorised entity with the proper authentication." (NCSC device security principles for manufacturers) In plain words, the key stays locked inside a chip and is released only when the right person authenticates.

The same page gives a concrete example: "Keys required for disk encryption are generated using a TPM 2.0 cryptoprocessor." For a Windows laptop, the check becomes a pair of questions. Is there a TPM, and is it at least version 2.0? IT can also read it from management records. Record the result as a version number, not as "yes, we have a TPM," because the version is the part the guidance specifies.

This page is written for device makers. It describes what a well-built device should do, which makes it a useful reference here. It does not describe how your laptop model is configured, and it is not a fleet checklist. Do not assume a model name guarantees the feature. The hardware and its settings on each machine are what count.

For Macs, the check is simpler to read. The Apple guidance on FileVault says: "If you have a Mac with Apple silicon or an Apple T2 Security Chip, your data is encrypted automatically." (Apple FileVault guide) For a Mac, the check becomes whether automatic encryption applies, which the guidance ties to Apple silicon or a T2 chip. If the machine has neither, that page does not settle the check, and the device needs a hands-on review before anyone approves it.

In our example, the rep's Mac has Apple silicon, so this check passes. The problems are the operating system and possibly the client version. Passing the hardware check means the chip is not the blocker. Whether a software fix is enough still depends on whether this Mac can run a supported release, as the operating system check shows. That matters for planning, because a software fix is usually quicker to arrange than a replacement.

Running the three checks in one pass

Put the three checks into one routine so the same steps run each time. For each laptop a rep wants to use for corporate access during the call, work through the table below.

CheckWhat to recordTest to applyResult
Operating systemName, exact version, and full release label on WindowsOn the vendor's supported list, and at or above the access client minimumPass / Fail
Access clientName and exact installed version, in the vendor's formatAt or above the minimum for that platform, and a release build rather than a betaPass / Fail
Hardware securityTPM and its version on Windows, or Apple silicon or T2 chip on a MacTPM at least 2.0 on Windows, or Apple silicon or T2 present on a MacPass / Fail

For each of the three items, mark the item pass or fail. A laptop goes on the approved list only when all three items pass. One fail is enough.

Give each check a named owner. The revenue leader should not be the one reading version strings off a rep's screen. A useful split works like this. The rep reports the device details. IT checks those details against its records. The revenue leader signs off only when every item passes. That keeps the person who wants the call to go ahead away from the decision about whether the device is safe, and it adds a second look before the call.

Timing matters. A failed check usually needs an update, a reinstall, or a replacement, and each can take longer than expected. Run the checks well ahead of the call, alongside the forecast call setup checklist, and agree a lead time with IT. A check run on the morning of the call leaves no room to fix anything, and it creates pressure to waive a rule that exists for good reason.

Date every result. A check from last quarter shows what the laptop looked like then, not what it looks like now. Run the operating system and access client checks again after a major operating system update or an access client update. Run all three when the rep changes laptops. The Windows guidance notes that major updates arrive once or twice a year, so a Windows result can go stale faster than most people expect.

Illustrative example: one rep, three checks

Imagine 10 reps who each need a laptop approved before Monday's call. Nine pass all three checks on the first run. The tenth fails the operating system check, so the rep and IT agree an update 2 days ahead. After the rerun, it passes all three and joins the approved list.

When a laptop fails

A fail is information, not a verdict on the rep. Tell the rep which check failed and what the fix is. Be specific. Something like this works: "Your Mac is below the macOS minimum our access client needs. IT will help you update it, or we will arrange a device for the call."

For our example, the sequence runs like this. The operating system check fails because the macOS release is too old. The rep updates the Mac to a supported release, if the hardware allows it. The access client check comes next, because the update may change the client's status. The hardware check has already passed on the Apple silicon Mac, so it does not need repeating after the update.

If the Mac cannot run a supported release, arrange a replacement or a loaner for the call. Decide that before the call, not during it. Do not let a rep join corporate systems from an unchecked personal device as a workaround. One unchecked device on the call is the gap the checks exist to close.

Some teams let a rep take part without corporate access. The rep might review a shared summary, or join by phone while a colleague with an approved device shares the screen. Whether that is allowed depends on your policy, so settle it before you offer it.

If a rep asks for an exception, send the request to whoever owns the access policy, with the three check results attached. A revenue leader should not decide an exception alone, because it affects what the device can reach. That is a security question as well as a sales one.

Track failures as well as passes. If the same check fails for several reps, the problem is probably a rollout or policy issue rather than one rep's habit. A short log of the failed check, the platform, and how long the fix took shows where to act. If most Mac failures trace back to one operating system release, the fix is an update reminder for every Mac owner, not a separate conversation with each rep.

What these checks leave out

These checks confirm device facts. They do not show who is using the laptop, what the rep does once connected, or whether every setting matches your policy. For reviewing access after a shared login changes, see access log checks. The device guidance and the desktop client guide cited here do not set your identity checks or access rules, so keep those decisions in your policy document, where they can be reviewed and changed.

Guidance changes over time. The Windows guidance was last tested on one specific build, and the minimum versions printed on each vendor page may change. Before relying on a number, open the page and check that it still matches. Give the refresh to a named person and date each check of a page, so readers know how old a number is.

A forecast is only as reliable as the data behind it, and that data is only as safe as the devices that reach it. Three checks, run early and dated clearly, will not solve every problem. They will catch the common gap between a laptop that looks fine and one that is ready for corporate access. They also give a revenue leader a clear answer before the call starts.

Related guides: AE capacity planning: 4 checks before a review · AI call scorecard checks: 5 rules before the forecast.

Sources