Endpoint

Onboarding a New Technician Laptop in 30 Minutes: A Runbook

By BP Tech Support · Feb 3, 2026 · 3 min read

Every dealership we have ever onboarded had its own folklore for setting up a new technician laptop. Most of it took 4 to 8 hours per machine, and most of it produced a slightly different result every time. Here is the runbook we use, in order, that turns a fresh laptop into a working tech bay machine in under 30 minutes — and produces an identical result every time.

Pre-stage (do this once, save for every laptop)

Windows 11 Pro image with the dealer baseline (Group Policy, registry tweaks, default browser, default PDF viewer)
Intune or Autopilot enrollment profile pre-staged for the device serial number
Network share or Cloud OneDrive folder with: latest OEM diagnostic apps, RP1210 drivers, label printer drivers, Wi-Fi cert profile

Step 1 (5 minutes): Out-of-box

Power on. Connect to the dealer Wi-Fi using the pre-staged profile. The Autopilot enrollment runs and pulls down: domain join, EDR, M365, Adobe Reader, the dealer printer drivers, and the corporate Edge profile. Walk away while it does this.

Step 2 (5 minutes): OEM diagnostic stack

Run the OEM installer pack from the network share. For a multi-line shop, this includes: Paccar EST + PSI + KW Service Connect, Cummins INSITE, Detroit Diesel DDDL, Volvo PTT, Mack Premium Tech Tool, Allison DOC. Each installer takes 1 to 3 minutes. Run them sequentially, not in parallel — they fight for the same RP1210 driver layer if you do not.

Step 3 (3 minutes): Service tooling

Install Decisiv SRM client, Mitchell 1 HD, and any in-house service apps. These are usually web-based now, so this step is mostly browser bookmarks and SSO certificates.

Step 4 (3 minutes): Adapter validation

Plug in a Nexiq USB-Link 3 or Noregon adapter. Verify Windows recognizes it. Open the OEM tool of the brand the tech most often works on (e.g., Paccar EST for Kenworth shops) and verify a test connection to a parked truck. If the connection fails, fix it now — not at 7:30 AM Monday when the tech needs to clock a job.

Step 5 (3 minutes): Printer mapping

Map the service drive printer, the parts counter printer, and the label printer. Print a test page to each. The first print job is always slightly delayed; do not assume "it will work later."

Step 6 (3 minutes): VPN and remote access

Install the corporate VPN client (FortiClient, GlobalProtect, or AnyConnect). Verify a test connection. Install the remote support agent (ScreenConnect, ConnectWise Control) and verify it appears in your dashboard.

Step 7 (3 minutes): MFA and password handoff

Enroll the technician hardware key (Yubikey or fob) for both Microsoft 365 and the DMS. Confirm SSPR (self-service password reset) is enrolled. Print a one-pager with the help-desk number and tape it to the laptop lid.

Step 8 (5 minutes): Final validation

Log in as the technician. Open Outlook, the DMS thin client, the OEM tool, and the service portal. Print a test repair order. Verify the laptop screen mirrors to the bay TV if you use that workflow. Sign off.

What this looks like as a saved package

Most of this can be reduced to a single PowerShell script that runs after Autopilot completes. Steps 2 through 6 are scriptable end-to-end with Chocolatey or Winget plus a couple of MSI exec lines. The only manual steps that remain are adapter validation (someone must physically plug in a USB-Link) and the technician-specific MFA enrollment.

At the dealerships where we run this fully, a new tech laptop is provisioned in 25 to 35 minutes by a non-IT staff member following the runbook. Every machine produces an identical result. Tickets in the first 30 days drop to almost zero.

This runbook is the kind of thing we hand the dealer in week two of onboarding. It is not proprietary; we just want it documented somewhere that you can find without us.