At my current employer, we have been moving from a traditional MDM to a hybrid approach, with a focus on dynamic configuration management and desired state using Chef as the primary mechanism.
Last night I announced that as of AirWatch 9.1, macadmins now have the ability to begin work on custom MDM.
Last month I outlined an upcoming feature for a major MDM vendor. In this time, I have received a lot of amazing feedback, but there have also been some questions that have come up.
For the past five months, I have been working tirelessly on this feature. I must commend this MDM vendor as they are legitimately excited for this new future. I cannot wait for others to try this out and I genuinely hope it will help with their future deployments of macOS.
In part 2, I showed you how to build a standard munki package and then how you could extend this concept and create a completely custom package. But with great power, comes great responsibility. Here are some best practices for using a custom DEP configuration, some ideas to try and things to watch out for.