speedsiteshine.blogg.se - Mdm solutions for windows and mac

MDM SOLUTIONS FOR WINDOWS AND MAC INSTALL
MDM SOLUTIONS FOR WINDOWS AND MAC ANDROID

Open source tooling like Chef, munki, and Puppet currently only supports device-based, local profiles.

User-level profiles: Because this digital workspace solution was so closely coupled with enrolled users, we could implement both device-based MDM profiles and user-based MDM profiles.

Moving our custom tooling behind MDM meant that employees must be enrolled into MDM in order to obtain access to other tools.

MDM SOLUTIONS FOR WINDOWS AND MAC INSTALL

Powerful APIs : We could leverage both the InstallApplication and InstallEnterpriseApplication APIs to install our custom tooling.

MDM SOLUTIONS FOR WINDOWS AND MAC ANDROID

Strength in numbers: We could leverage our mobility engineers during the implementation and design stages as this digital workspace solution was already being used for devices with iOS and Android operating systems.

We came to this decision for the following reasons: Mobile Device Management (MDM) at UberĪlthough we use Chef as our primary management tool, in the past few years - especially with regards to macOS - we needed to adopt an MDM system to supplement our workflows.Īfter looking at many open source and third-party MDM solutions, we decided to extend our partnership with a third-party vendor and add macOS endpoints into its digital workspace platform. In this article, we discuss how the CPE team scaled MDM on macOS at Uber through the standardization of user enrollment and versioning, as well as by leveraging API-driven Chef cookbooks to orchestrate and configure services for users across the company. While Chef continues to be the primary management tool at Uber, Apple’s implementation of new security features, such as Device Enrollment, Secure Kernel Extensions, and Privacy Preferences Policy Control, gated some portions of administration behind mobile device management (MDM). Unlike traditional GUI-based management platforms, Chef allowed the team to create deterministic workflows based on Uber’s unique requirements.

Over the past few years, the Uber CPE team deployed Chef, a singular system that could scale to multiple operating systems while also requiring code review for all deployed changes as the primary endpoint management platform. With over 20,000 global employees, hundreds of offices, and an ever-growing number of device types, we need to build flexible pipelines that allow us to easily inject new management workflows without slowing us down or causing technical debt. At Uber, the Client Platform Engineering (CPE) team is responsible for building both our IT infrastructure and advancing how we think about managing endpoints for workplace productivity.