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.
Time to get your hands dirty
For the better part of six months, macadmins across the world have been worried about the future of macOS. Whether it’s the rumblings people have heard about imaging being killed or that DEP/MDM could possibly be the only way to manage macOS devices moving forward, it has definitely made for an interesting time.
In my last post I talked about Cacher 3.0. In the past month and a half I have been extraordinarily busy and unfortunately had some outstanding issues on my GitHub. After working on the issues, I realized that documentation on LogClientIdentity is very poor.
I recently took part in the macadmins podcast and had a great time, but there was one comment that struck a chord with me - Marcus Ransom thanked me for writing Cacher. Cacher is my most popular github repo and while I get thanked often for creating it, my reaction usually goes something like this: