Managing hundreds of devices is a juggling act every IT team is familiar with. You need to keep equipment up to date and secure, but updates and patches have to be rolled out in phases to avoid disrupting critical business operations.
Apple introduced Declarative Device Management (DDM) for OS patching around three years ago, giving companies the ability to enforce OS update compliance. But our mobile device management (MDM) provider made it practically unusable at scale and only released DDM patching functionality earlier this year. It had no real dashboard, no deadline visibility, and no native notifications beyond easily-missed system notification pop-ups.
Using Tines 3B, our organization’s secure environment for building with AI, we created a custom patch management platform that gives us greater visibility, reduces the time we spend searching for details, and helps us make necessary updates as pain-free as possible for our team and end users.
This project sat in the backlog for two years — the team knew which build additions they wanted to make but didn't have the bandwidth to tackle them. With Tines 3B, it took less than two days to bridge the product feature gap that kept us from wider adoption. Now, we can see, manage, and troubleshoot patches from one simple platform, without needing to totally overhaul our legacy MDM.
The impact this build had on the business is easy to see — employees now easily understand when their devices need to be updated, and our IT team doesn't get inundated with a bunch of manual work to make it happen. It saves everyone time and energy to maintain security and compliance.
Christina Troy, Senior Manager, IT
Alexis’ patch management tool has given us a centralized, unified space to administer our device fleet. Our old patch management process meant digging through multiple dashboards just to confirm a device’s status. Now we get those answers in a couple of clicks.
Des Corr, Senior IT Operations Technician
The problem: manual patching, poor visibility, and missed opportunities to move faster
Our old way of applying patches was manual and inconsistent, relying on users to go through updates themselves. We set enforced policy deadlines for major macOS updates — the ones with all the fancy new features — but the smaller updates in between could easily get missed, increasing the risk of security vulnerabilities on our laptops.
Our MDM’s native dashboard offered only a vague “patched/not patched” pie chart, and lacked visibility into target versions, group policies, deadlines, and notification history. Key information, like which deadline updates applied to which users, wasn’t available at a glance, so we’d have to manually click in and investigate. There was no API to programmatically pull rolling deadline data either. This made it really difficult to track updates across rolling patches.
If you’re trying to keep 500+ MacBooks consistently up to date, you need a useful dashboard. This wasn’t.
We also wanted to improve notifications. Apple’s own system OS notifications are easy to ignore. Even with the best of intentions, many users struggle with notification fatigue: they see another pop-up, think “I’ll deal with this later,” and then get distracted by another notification, task, or meeting.
We had access to Apple’s enterprise patch enforcement feature, DDM, but we just couldn’t close the gaps in our MDM to make it usable.
The solution: a custom patch management platform built with Tines 3B
To solve these problems, we created our own patch management platform using Tines 3B.
It pulls device data from our MDM, calculates each device’s current and target OS version, and surfaces group policy deadlines automatically. Previously, we had to manually cross-reference release dates and grace periods to get those deadlines. This does it all for us, and everything we need is presented in a comprehensive, easy-to-use dashboard. And we can filter down into any part of the data set — the device’s patch group, the device’s eligibility, and the device patch status — to drill into the details we need to be effective at rolling out patching with very little pain.
Then, the platform triggers dynamic Slack notifications, including daily reminders in the final days before a deadline and letting people know when their device has a new patch they can download. We know that people tend to pay more attention to notifications when they’re in Slack and they can add them to their task list, so adding this functionality has been a game changer.
The platform’s smart logic is what really makes it powerful for us. It checks eligibility by matching inventory records to the assigned user and confirming they’ve logged in within the past 30 days, ensuring people on extended leave aren’t bugged unnecessarily. And because it draws on real-time device data, notifications stop automatically once the MDM detects the device has been updated — no manual tracking needed.
It’s closed the gaps we had with our MDM tool. The extra notification feature and logic to help us figure out deadlines provide a lot of clarity, not just for our team, but ultimately for end users, too.
The impact: greater oversight, less manual work, and improved historical logging
Full visibility at a glance
Now, we can see exactly where everything stands: which versions are running on which devices, who needs to update and when, and any patches that are overdue. Instead of wading through a sea of data, cross-referencing dates, and clicking into multiple areas of our MDM, everything we need is on one screen, so we can spot issues and prioritize what needs attention first.
Checking a single device used to take 10 clicks. Now it takes two or three — and covers multiple devices at once. Multiply that across hundreds of devices, and the time savings add up fast.
Easy logging of the entire cycle
If a user tells us they couldn’t update their device, never got a notification, or doesn’t know why their device restarted, we can check the platform to confirm everything was working as intended. It gives us the proof we need — a record of the policy applied to their device, the deadlines, and the notifications they received — so we can be confident the user was informed.
Enhanced capabilities, extensible to any team
The platform has made a recent MDM capability actually usable across more than 500 devices. With our MDM alone, this just wasn’t possible: without solving the deadline date logic and notification problems first, deploying DDM would only have created more work for us and our end users.
It isn’t just the IT systems team that uses this app, folks across the IT and security team can use the platform to self-serve, too. For example, security can check whether users with known vulnerabilities on their devices are due to upgrade soon anyway or track deployment of an ad-hoc OS enforcement deadline to address a critical OS vulnerability.
And IT ops can identify whether any users need specialized comms as deadlines approach. No one wants the C-suite’s laptops force-restarting in the middle of a big meeting.
What’s next?
Now that we've rolled out this new process, the next step is measuring impact, adjusting, and improving self-service beta testing. We'll be tracking new metrics, like how early people update their devices compared to the deadlines. This should give us some interesting insights that will help us improve the entire process. If people have 20 days to do an OS update, why aren't they doing it earlier? Are there better ways we can reach out to people? We're using this data to help us understand what people need to be notified about, and how we can improve education, too.
We’re also looking at an automated limited membership opt-in for folks around the business to be the first to receive OS patches and submit feedback or issues if they run into problems. This can help us address issues that the IT team themselves may not find, but we want to do this with limited manual work and allow folks to opt-in and out as desired.
We would love to have a more proactive feedback loop, rather than a reactive one.
Final thoughts
Moving MDMs is a huge hassle for everyone. It’s always on our radar if we need to replace a tool or system, but having a dashboard of patch info and custom notifications isn’t a good enough reason.
Building in Tines 3B means we don’t have to settle: we can unlock Apple’s DDM capability, improve patch management, and get greater visibility without needing to uproot our whole system. And it took me a couple of hours over the course of two days to greatly improve our existing tool capabilities.
When you can build a platform like this in a day or two, you no longer have to wait for more team bandwidth to improve your processes.
