Services

Services organized around a complete rollout.

Each item maps to a step the customer actually has to cross, not a generic product catalog. Typical scope is adjusted for the project; the lists below describe the work we most often cover in a Jamf Pro rollout.

01

Requirements and solution assessment

We help evaluate a suitable Jamf approach and implementation path, and align scope, goals, and the direction of acceptance first, so the trial and delivery sit on a shared foundation. Drawing on practical project experience in Mac and Apple device management, we agree what should be validated and delivered before environments and configuration begin.

Typical scope

  • Understand fleet size, use cases, and the current environment
  • Discuss a suitable approach and implementation path, and align scope
  • Form a shared starting point for the subsequent trial and implementation
02

Proof of concept and trial

We provision and configure a Jamf Cloud trial, and plan a testable scope so decisions are based on real use. Proof of concept is treated as formal work: an environment, a defined scope, and a written record, not a single demonstration.

Typical scope

  • Provision the trial tenant and complete basic preparation
  • Agree the scenarios to validate and what success looks like
  • Run enrollment and priority capabilities on test devices, and keep a record
03

Implementation and ABM

We guide Apple Business Manager enrollment, Jamf ID creation, device enrollment, and directory integration so new devices can be managed. In education environments that use Apple School Manager, the same principle applies: connect the organizational portal to Jamf Pro first, then define Automated Device Enrollment and PreStage settings.

Typical scope

  • Assist with connecting ABM or ASM to Jamf Pro
  • Configure Automated Device Enrollment and a PreStage for testing
  • Set up agreed device grouping, and directory or identity integration where it is in scope
04

Security baseline and policy

We implement disk encryption, Recovery Lock, restrictions, passcode policy, and remote management as a workable security baseline. The aim is not to turn on every control at once, but to make the protections the organization actually requires verifiable and ready to hand over.

Typical scope

  • Plan and validate FileVault, including recovery-key escrow
  • Configure Recovery Lock on applicable Mac computers
  • Apply restriction, passcode, and peripheral policies, and confirm that remote lock and wipe are available
05

App distribution and OS updates

This covers package deployment, distribution of third-party security tools, operating-system update management, and day-to-day use of Self Service. Required apps can be delivered automatically when conditions are met; optional tools can live in Self Service, so the first day does not become an installation bottleneck for IT.

Typical scope

  • Plan distribution for App Store apps, internal packages, or third-party tools
  • Configure optional content for users in Self Service
  • Plan update cadence against current OS capabilities, and validate it on test devices
06

Training, SOP, and support

Workshops, operating documents, and ongoing support leave capability with the customer team, rather than ending at a one-time deployment visit. Administrators should be able to read their own environment, handle routine work from an SOP, and know how to get help when a policy needs to change or something fails.

Typical scope

  • Workshops and walkthroughs of the operating path for administrators
  • Enrollment notes, testing standards, and operational handover documents
  • Support after go-live for policy changes and troubleshooting