Planning for MDM

- [Instructor] There are three core phases required for planning mobile device management deployments. First, defining the goals and objectives for the deployment. Second, identifying users, groups, and department scenarios. And then third, developing the rollout plan which will also include communication and support, which is often left out of these types of deployments. We'll now talk about planning for mobile device management and talk in more detail about the goals, objectives, and challenges you may face. Before any mobile device management configuration is completed, deployment goals, objectives, and challenges are required. These become the basis for the success of the deployment. Goals are the long-term objectives that need to be met by the deployment. Objectives are specific actions to reach the goals. And then challenges are recognized issues or blockers that will impact the deployment if not addressed. Some examples of deployment goals could be: Enable access to internal applications within the corporate network on the deployed and protected mobile devices. Provide data protection and encryption on mobile devices. Integrate the mobile devices with Office 365 and support the use of the Office 365 mobile applications. And then, reduce the overall management cost of managing mobile devices. When documenting the goals, a detailed description and a business value should be listed. For example, if we use the goal provide data protection and encryption on mobile devices, the detail description could be, when data is stored on a mobile device it should be protected from malicious and accidental loss or sharing. The business value could then be, data protection is vital to ensure that we remain competitive and that we treat our clients and their data with the utmost diligence. So, you can see that we are mapping a specific goal with extra pieces, such as the objective to complete that and any risks that may come with that. Some other examples of deployment could be: Provide capability of wiping all corporate data from the device. Prevent corporate data from being stored or forwarded to non-corporate services on the mobile device. Reduce the number of device management solutions. Or provide secure access to SharePoint Online. When documenting the objectives, an idea of what the implementation should be needs defining. For example, if we use the objective provide secure access to SharePoint Online, the implementation approach could be, apply conditional access for SharePoint Online. Some examples of deployment challenges could be: Support readiness and end-user experiences are not included in an initial project scope. This leads to poor end-user adoption and challenges for your support organization. A second one could be lack of clearly defined goals and success metrics leads to intangible results. It may also shift your organization into reactive mode when issues arise. When documenting the challenges, an idea of a mitigation needs defining. For example, if we use the objective support readiness and end-user experiences are not included in our initial project scope, the mitigation approach could be, incorporate support training, validate the end-user experience with success metrics in your deployment plan. Defining goals, objectives, and challenges is the first step in a successful mobile device management deployment.