Common questions
FAQ
Q
Do we need to already use Jamf?
No. We work with teams who already have Jamf Pro, teams migrating from Intune, Kandji, Mosyle and similar, and teams starting from scratch. Our most common first engagement is a clean Jamf Pro deployment alongside a legacy MDM wind-down.
Q
What size fleets do you support?
Anywhere from 20 Macs to 20,000. The tools and techniques change at scale, but the principles don't. Smaller fleets often benefit the most from a tight initial design because there's nobody in-house dedicated to managing it.
Q
Do you handle iOS and iPadOS as well?
Yes. Jamf Pro is the same platform for macOS, iOS, iPadOS, and tvOS. If you manage Apple devices of any kind, we can help. We've deployed shared iPad environments, supervised corporate iPhones, and kiosk iPads for retail and hospitality.
Q
What about Jamf Protect, Connect, and School?
We work across the full Jamf product suite. Jamf Protect for endpoint security, Jamf Connect for identity, Jamf School for education deployments. Tell us what you're running and we'll scope accordingly.
Q
How long does a typical engagement take?
It depends on scope. A fresh Jamf Pro deployment for a 200-device fleet usually runs 2 to 4 weeks. A health check and punch list is typically 3 to 5 days. Migrations from another MDM vary hugely based on the complexity of existing policies and the appetite for parallel running.
Got a question we haven't answered?
Every environment is different. If you're unsure whether Jamf is the right tool for your situation, or you just want to get a sense of whether we're the right fit, drop us a line.