· managed it · 4 min read
Patch Management: When Two Teams Share the Job
Patching spans workstations, third-party apps, servers, network gear, and line-of-business software the vendor controls. Here is how co-managed IT splits each layer so nothing sits in the gap between two teams.

Patching is the chore everyone agrees on and nobody has time for. In an organization with an in-house IT person and an outside MSP (managed service provider), it gets worse in one specific way: each side assumes the other one has it.
Say your IT manager is out for a week and a browser update fails on six laptops in the accounting department. Does the MSP’s console show it? Does anyone look? This post lays out who owns which layer so the answer is written down before that week arrives.
Patching has more layers than Windows Update
Most people picture operating system updates. Those are the easiest layer, because the tooling is mature. Others take more care:
- Windows and macOS updates on workstations and laptops
- Third-party apps: browsers, PDF readers, Java, remote access tools
- Server operating systems and the software on them
- Firmware on firewalls, switches, and wireless access points
- Line-of-business software (an ERP, a CRM, engineering or imaging tools) where the vendor sets the supported versions
The third-party layer is where many organizations get hurt. Attackers go after outdated browsers and PDF readers because those are everywhere and often skipped.
Who owns which layer in co-managed IT
A reasonable starting split:
- The MSP patches workstation and server operating systems through its RMM (remote monitoring and management) platform, patches the common third-party apps the same way, and reports failures.
- Your internal IT team knows which machines cannot restart during the day, which have special software, and which belong to a vendor relationship. They approve exceptions.
- Firmware on the firewall and network gear is shared. The MSP schedules and performs it. Your IT manager approves the window, since a firewall reboot takes the whole office offline for a few minutes.
- Vendor-controlled software goes to your IT manager, who talks to the vendor. The MSP tests whether operating system updates break it.
Put names next to each line. A role that says “IT” covers two teams and means neither.
When the vendor dictates the version
Plenty of specialized software supports only certain Windows versions. A design tool for an engineering firm, a payroll package, or a dental imaging system can all come with a vendor note saying to hold an update until they certify it.
Sometimes that advice is right. Sometimes it has been sitting there for two years. Handle exceptions with a short routine:
- Get the vendor’s requirement in writing
- Record the exception with an owner and a review date
- Ask the vendor every quarter whether it still applies
- Add protections around the machine while it waits, such as limiting what it can reach on the network
An exception with no review date is just an unpatched computer with a story attached. Our remote monitoring and management tooling can list every exception so none gets forgotten.
Maintenance windows around the business calendar
Updates that restart machines need a schedule that respects how people work. An accounting firm in tax season cannot lose a morning, and a contact center cannot restart machines mid-shift. Windows that work for many organizations:
- Workstations install after hours and restart before the first shift, with a catch-up rule for laptops that were off overnight
- Servers update in a weekend window with a person on call
- Firewall and switch firmware goes in early morning, when someone can confirm that phones, VPN, and core applications come back
Decide who is on call when a patch breaks something. If the answer is “whoever notices,” you have not decided. The 2 a.m. call should go to a named person, with the MSP as backup, and the order should be on paper.
Reporting on what failed
A report that says 97 percent of machines are patched hides the three that matter. Ask for a list instead:
- Devices missing patches past the agreed deadline
- Devices that have not checked in for a set number of days
- Install failures, with the reason
- The exception list, with owners and review dates
Your IT manager should see this weekly and spend ten minutes on it. Leadership should get a one-page summary monthly. If the same device fails twice, someone opens a ticket and finds out why.
Try this test this week. Pick five machines at random, including one from a department that rarely calls IT, and check the date of the last update and the version of the browser. If the dates are far apart, your process has a hole worth finding.
In a co-managed IT arrangement we handle automated patching and failure reporting, and we pair it with vulnerability scanning of every device so missed updates show up as findings with an owner. Your IT manager keeps the exceptions and the vendor relationships. See how our managed IT services split the work.
Call us at 405-253-5101 or schedule a discovery call to get on the calendar.
- co-managed-it
- patch-management
- rmm
