MDS 2.0 helps administrators to modernize their workflow and implement Apple hardware and software. This Mac implementation program is also free.
Image: anyaberkut, Getty Images / iStockphoto
A few years ago, when Apple released macOS High Sierra 10.13.4, some changes were built into the operating system that changed how administrators would use macOS in the future. By doubling this major change, macOS Mojave had to reinforce the change in the implementation workflow by using MDM solutions (Mobile Device Management) for the design, configuration and management of Apple devices.
SEE: Cheatsheet: Apple macOS Catalina (free PDF) (TechRepublic)
I previously wrote about Mac Deploy Stick (MDS), the free implementation program developed by Twocanoes Software to help Mac administrators implement macOS on new and existing Apple computers, either independently or over the network. MDS has now been updated to version 2.0, which provides additional support for new deployment features, including an MDM server with a basic feature set to facilitate Mac management.
Organizations that support Apple devices of all shapes and sizes can and must apply for an Apple Business Manager account (or Apple School Manager for education) so that they can fill in the online account with the serial numbers for their device fleet; this connects the devices to the MDM server for an end-to-end solution. MDS 2.0 fits nicely into the MDM role and supports Apple’s frameworks for device provisioning during registration without expensive license fees for devices or subscriptions such as other MDM service providers.
The MDM function in MDS 2.0 is based on MicroMDM and uses Apple Push Notification Services (APNS), Device Enrollment Profile (DEP) and an MDM configuration profile to enroll the device by first communicating with Apple’s servers when a device is at the Setup Assistant screen after it has been deleted or removed from the box. During the activation phase, Apple’s servers will detect the device’s serial number and see that it is linked to the MDM service so that it is passed on to the MDM server for delivery.
From here, MDS 2.0 provides the configuration profile that both registers the device and configures the initial settings for the device, including skipping additional installation screens that can optionally be configured as managed settings. The registration profile also serves as the management profile for the device, allowing future configurations to be trusted during device deployment and life cycle.
Another advantage of MDS 2.0’s vision of the MDM service is that it uses the MicroMDM API to provide command line management through the Terminal. It also includes a simple but effective web-based enrollment page that is linked to the host system’s IP address or fully qualified domain name (FQDN), allowing users to access the website to manually register their devices with the MDM service. This is especially useful during certain types of deployments, such as devices where devices cannot be deleted prior to enrollment, personal devices that are part of a BYOD initiative, or devices that are not physically accessible and need to be remotely arranged.
MDS is already a strong candidate for macOS implementation, and the added support as an MDM server – despite the limited functions – is a welcome addition to your macOS management arsenal. This is especially true for those who may want to gain experience with mobile device management and how they can test deployments with Apple hardware to determine which methods work best for the specific needs of your organization.
Weekly newsletter from Apple
Whether you need iPhone and Mac tips or overviews of company-specific Apple news, we have it for you.
Delivered Tuesday
Register today
