Search results
Jan 4, 2022 · Blackberry might not have been able to beat the iPhone or Android, but its biggest failing was a failure to recognize a serious competitor, a mistake that likely won’t be repeated anytime soon.
devices connect to your network, what device capabilities are enabled, and what apps are available. Whether devices are owned by your organization or your users, you can provide mobile access to your organization's information while protecting it from anyone who should not have access.
BlackBerry solutions can allow you to deploy MDM securely and in a way that meets your business needs. Support a wide range of mobile devices – iOS, Android™, Windows®, macOS and BlackBerry; Enable multiple ownership models – BYOD, COPE and COBO; Configure rich policy controls with the right security posture for users and groups of devices
Jan 29, 2015 · BlackBerry Classic vs. Apple iPhone 6 (image: Ewan Spence) Value For Money With a SIM-Free price of $450, the BlackBerry Classic is significantly cheaper than the equivalent 16 GB iPhone 6 at...
- Overview
- How devices enroll
- MDM and Stolen Device Protection
- Enrollment profiles
- Configuration profiles
- Profile removal
- MDM communication requirements
- Supported Apple devices
iOS, iPadOS, macOS, tvOS, and watchOS have a built-in framework that supports mobile device management (MDM). MDM lets you securely and wirelessly configure devices by sending profiles and commands to the device, whether they’re owned by the user or your organization. MDM capabilities include updating software and device settings, monitoring compliance with organizational policies, and remotely wiping or locking devices. Users can enroll their own devices in MDM, and organization-owned devices can be enrolled in MDM automatically using Apple School Manager or Apple Business Manager. If you’re using Apple Business Essentials, you can also use the device management that’s built right in.
There are a few concepts to understand if you’re going to use MDM, so read the following sections to understand how MDM uses enrollment and configuration profiles, supervision, and payloads.
Enrollment in MDM involves enrolling client certificate identities using protocols such as Automated Certificate Management Environment (ACME), or Simple Certificate Enrollment Protocol (SCEP). Devices use these protocols to create unique identity certificates for authenticating an organization’s services.
Unless enrollment is automated, users decide whether to enroll in MDM, and they can disassociate their devices from MDM at any time. Therefore, you want to consider incentives for users to remain managed. For example, you can require MDM enrollment for Wi-Fi network access by using MDM to automatically provide the wireless credentials. When a user leaves MDM, their device attempts to notify the MDM solution that it can no longer be managed.
When Stolen Device Protection is turned on, the user receives an error when trying to:
•Manually enroll their device in MDM
•Configure a Microsoft Exchange account
•Install a passcode or Microsoft Exchange profile
•Install a declarative configuration
To perform any of those actions, the user can temporarily turn off Stolen Device Protection. If the device is already enrolled in MDM, they can turn on Stolen Device Protection and MDM operates as usual.
An enrollment profile is one of two main ways users can enroll a personal device into an MDM solution (the other way is to use User Enrollment). With this profile, which contains an MDM payload, the MDM solution sends commands and—if necessary—additional configuration profiles to the device. It can also query the device for information, such as its Activation Lock status, battery level, and name.
When a user removes an enrollment profile, all configuration profiles, their settings, and Managed Apps based on that enrollment profile are removed with it. There can be only one enrollment profile on a device at a time.
A configuration profile is an XML file (ending in .mobileconfig) consisting of payloads that load settings and authorization information onto Apple devices. Configuration profiles automate the configuration of settings, accounts, restrictions, and credentials. These files can be created by an MDM solution or Apple Configurator, or they can be created manually.
Because configuration profiles can be encrypted and signed, you can restrict their use to a specific Apple device and—with the exception of user names and passwords—prevent anyone from changing the settings. You can also mark a configuration profile as being locked to the device.
If your MDM solution supports it, you can distribute configuration profiles as a mail attachment, through a link on your own webpage, or through the MDM solution’s built-in user portal. When users open the mail attachment or download the configuration profile using a web browser, they’re prompted to begin configuration profile installation.
For more information about profile installation and Lockdown Mode, see the Apple Support article, About Lockdown Mode.
Note: You can use Apple Configurator for Mac to add configuration profiles (automatically or manually) to iOS, iPadOS, and Apple TV devices. For more information, see the Apple Configurator User Guide for Mac.
As an administrator, you can deliver a configuration profile that can change settings for an entire device or for a single user:
How you remove profiles depends on how they were installed. The following sequence indicates how a profile can be removed:
1. All profiles can be removed by wiping the device of all data.
2. If the device was enrolled in MDM using Apple School Manager, Apple Business Manager, or Apple Business Essentials, the administrator can choose whether the enrollment profile can be removed by the user or whether it can be removed only by the MDM server itself.
3. If the profile is installed by an MDM solution, it can be removed by that specific MDM solution or by the user unenrolling from MDM by removing the enrollment configuration profile.
4. If the profile is installed on a supervised device using Apple Configurator, that supervising instance of Apple Configurator can remove the profile.
5. If the profile is installed on a supervised device manually or using Apple Configurator and the profile has a removal password payload, the user must enter the removal password to remove the profile.
Third-party MDM communication with Apple devices is most likely to be successful when:
•The MDM solution is set up, successfully tested, and working properly
•The APNs certificate is valid and not expired
•The device is powered on
•The device is currently enrolled into the MDM
•The network the device is connected to has access to the internet (for APNs communication)
The following Apple devices have a built-in framework that supports MDM:
•iPhone with iOS 4 or later
•iPad with iOS 4.3 or later or iPadOS 13.1 or later
•Mac computers with OS X 10.7 or later
•Apple TV with tvOS 9 or later
•Apple Watch with watchOS 10 or later
BlackBerry UEM provides precise management of how iOS and iPadOS devices connect to your network, what device capabilities are enabled, and what apps are available. Whether devices are owned by your organization or
People also ask
Does BlackBerry UEM support supervised iOS devices?
Does BlackBerry UEM support Apple TV?
What is mobile device management (MDM)?
What is a mobile device management strategy?
Does BlackBerry offer MDM solutions?
What happens if a device is activated with BlackBerry UEM?
MDM vs. EMM vs. UEM. Mobile Device Management helps organizations remotely manage mobile devices and enables users to perform authorized tasks. It helps improve productivity by allowing users to have automatic access to the systems they need and reducing downtime with centralized update management.
