Ryan explores various mobility programs in this video. Determine the difference between Corporate-Owned, Bring-Your-Own (BYO), and Corporate-Owned, Personally- Enabled (COPE) programs. Compare these programs with your organization's goals. Identify the types of mobile users in your workforce to determine the best MDM solution.
- It's important to determine the job to be done by the devices that will be managed. Determining what the device accomplishes is the essence of mobility management. It's critical to build a support structure that is robust enough to accomplish not only the job at hand, but also flexible enough to change as the job itself changes. I'll start by defining the question of the jobs to be done with the big bucket. The big bucket is where most mobility programs originated. It represents the fleet of devices being deployed in order to provide email, contacts and calendars to a workforce, providing the mobile worker with internal communication and scheduling.
The big bucket is the simplest definition of the job to be done by a mobile fleet. Big bucket deployments can have looser compliance, quicker support and deployment, and cost effective management structures. Devices that only need basic resources are big bucket devices. Big bucket deployments can have looser compliance, quicker support and deployment, and cost effective management structures. Devices that only need basic resources are big bucket devices. Frequently, big bucket design captures a majority of the defined needs of a mobile fleet.
However, the larger my bucket is, the fewer options I have for flexibility when the job and workforces change. It's also critical to consider the salesforce. The second most popular mobile program target. Most people working in sales are by definition mobile. What they need to get their job done is not only email, contacts and calendars, but also content. They need access to the most recent sales collateral and the applications that track their efforts in the field.
In this scenario, I need to provide the device with the identity of the user, their email, contacts and calendar, access to company content, and business critical applications, all in a secure manner. In order to equip the salesforce with devices that empower their work and secure the organization's data, I will need to build a unique set of configurations, policies, compliance rules, and integration points inside of Intune. The sales group can be thought of as medium bucket.
We're still considering a large portion of the organization but it isn't as big a division as the big bucket group. Once I have my large and medium buckets laid out, I turn to the small bucket. My small bucket design will define the devices' job to be done, down to the finest detail. For example, if I have a warehouse team that needs to have iPads that perform a single function, the iPads must be able to used by multiple people to perform the same job. These devices don't need any of the tools or functionality of the big and medium bucket groups, and these users should not be able to make any changes to the device.
For the small bucket group, I will need to define every thing on the device. I will need to provide identity, strict compliance, and strong lock-down measures. Mobility management design requires a strong concept of the job to be done by each device. In order to facilitate a flexible management platform, I must know the inverse relationship between highly defined mobility needs, such as the small bucket group, and the loosely defined mobility needs of the big bucket group. The ability to scale support and provide job success depends on how well administrators understand these design groups.
Ryan is the director of enterprise mobility management at MOBI and supports Fortune 100 clients around the world. Here he shares the key components of any enterprise mobility management (EMM) strategy, focusing on Microsoft Intune. Learn what's different about the Windows 10 mobile operating system and why and how businesses manage Windows devices with Intune. Explore Intune infrastructure management and best practices pertaining to design, identity, security, updates, applications, content, and more. Along the way, he'll help you design and implement smart security policies, configure monitoring and services like Windows To Go, and provisioning user accounts.
Note: This course maps to the Plan and Implement a Microsoft Intune device management solution domain of the Microsoft exam 70-697: Configuring Windows Devices.
- Preparing for a mobile program
- Managing mobile devices, users, and data
- Building mobile user awareness
- Understanding mobile security issues
- Activating Enterprise Mobility Suite (EMS)
- Configuring and deploying device policies
- Configuring monitoring and alerts
- Designing file and power policies
- Configuring Windows To Go, Windows sync, Wi-Fi direct, and device encryption
- Supporting Intune deployments
- Provisioning user accounts
- Managing Intune groups
Skill Level Intermediate
Q: This course was updated on 03/30/2018. What changed?
A: New videos were added that cover mobile device and application management, the Azure AD interface, app management without device enrollment, and Intune and eBook deployment. In addition, the following topic was updated: mobile security.