InformationWeek.com: News, analysis and research for business technology professionals, plus peer-to-peer knowledge sharing. Engage with our community. UPDATE 7/7: Today we have released Windows 10 Insider Preview Build 16232 for PC to Windows Insiders in the Slow ring. Remember – we are doing a staggered roll-out. Windows 1. 0 Mobile deployment and management guide (Windows 1. Applies to: Windows 1. Mobile, version 1. Windows 1. 0 Mobile, version 1. This guide helps IT professionals plan for and deploy Windows 1. Mobile devices. Employees increasingly depend on smartphones to complete daily work tasks, but these devices introduce unique management and security challenges. Whether providing corporate devices or allowing people to use their personal devices, IT needs to deploy and manage mobile devices and apps quickly to meet business goals. However, they also need to ensure that the apps and data on those mobile devices are protected against cybercrime or loss. Windows 1. 0 Mobile helps organizations directly address these challenges with robust, flexible, built- in mobile device and app management technologies. How do I install my wearable device? Wearable devices are automatically installed after the WebEx Meetings app is installed on your mobile device. The Windows Mobile Device Center enables you to set up new partnerships, synchronize content and manage music, pictures and video with Windows Mobile powered. Requires ActiveSync or Windows Device Center (or you can use IP Connection but it’s slow) File Browsing, you can also use FTP client like FileZilla. However, if the USB device works in another computer system, then the problem lies with the configuration of the computer where the device did not work. ![]() Devices can easily be incorporated into standard lifecycle practices, from device enrollment, configuration, and application management to maintenance, monitoring, and retirement using a comprehensive mobile device management solution. In this article. Deploy. Windows 1. 0 Mobile has a built- in device management client to deploy, configure, maintain, and support smartphones. Common to all editions of the Windows 1. Internet of Things (Io. T), this client provides a single interface through which Mobile Device Management (MDM) solutions can manage any device that runs Windows 1. Because the MDM client integrates with identity management, the effort required to manage devices throughout the lifecycle is greatly reduced. There is no need to install an additional, custom MDM app to enroll devices and bring them under MDM control. All MDM system vendors have equal access to Windows 1. Mobile device management application programming interfaces (APIs), giving IT organizations the freedom to select whichever system best fits their management requirements, whether Microsoft Intune or a third- party MDM product. For more information about Windows 1. Mobile device management APIs, see Mobile device management. Deployment scenarios. Applies to: Corporate and personal devices. The built- in MDM client is common to all editions of the Windows 1. Internet of Things (Io. T). The client provides a single interface through which you can manage any device that runs Windows 1. The client has two important roles: device enrollment in an MDM system and device management. Organizations typically have two scenarios to consider when it comes to device deployment: Bring Your Own (BYO) personal devices and Choose Your Own (CYO) company- owned devices. In both cases, the device must be enrolled in an MDM system, which would configure it with settings appropriate for the organization and the employee. The operating system offers a flexible approach to registering devices with directory services and MDM systems. IT organizations can provision comprehensive device- configuration profiles based on their business needs to control and protect mobile business data. Apps can be provisioned easily to personal or corporate devices through the Windows Store for Business, or by using their MDM system, which can also work with the Windows Store for Business for public store apps. Whether personal devices, corporate devices, or a mixture of the two, deployment processes and configuration policies may differ. For personal devices, companies need to be able to manage corporate apps and data on the device without impeding the employee’s ability to personalize it to meet their individual needs. The employee owns the device and corporate policy allows them to use it for both business and personal purposes, with the ability to add personal apps at their discretion. The main concern with personal devices is how organizations can prevent corporate data from being compromised, while still keeping personal data private and under the sole control of the employee. This requires that the device be able to support separation of apps and data with strict control of business and personal data traffic. For corporate devices, organizations have a lot more control. IT can provide a selected list of supported device models to employees, or they can directly purchase and preconfigure them. Because devices are owned by the company, employees can be limited as to how much they can personalize these devices. Security and privacy concerns may be easier to navigate, because the device falls entirely under existing company policy. Device enrollment. Applies to: Corporate and personal devices. The way in which personal and corporate devices are enrolled into an MDM system differs. Your operations team should consider these differences when determining which approach is best for mobile workers in your organization. Device initialization and enrollment considerations. Personal devices. Corporate devices. Ownership. Employee. Organization. Device Initialization. In the Out- of- the- Box Experience (OOBE), the first time the employee starts the device, they are requested to add a cloud identity to the device. The primary identity on the device is a personal identity. Personal devices are initiated with a Microsoft Account (MSA), which uses a personal email address. The primary identity on the device is an organizational identity. Corporate devices are initialized with an organizational account (account@corporatedomain. No other mobile platform currently offers this capability. The default option is to use an Azure Active Directory organizational identity. The only option to add a cloud account later is to add an MSA, putting this device into a personal device deployment scenario. To start over, the device will have to be reset. Device enrollment can be initiated by employees. They can add an Azure account as a secondary account to the Windows 1. Mobile device. Provided the MDM system is registered with your Azure AD, the device is automatically enrolled in the MDM system when the user adds an Azure AD account as a secondary account (MSA+AAD+MDM). If your organization does not have Azure AD, the employee’s device will automatically be enrolled into your organization’s MDM system (MSA+MDM). This option enables IT to offer easy- to- use self- service enrollment of personal devices. Provisioning is currently only supported for MDM- only enrollment (MSA+MDM). The device is automatically enrolled in the MDM system when the device registers in Azure AD. This requires your MDM system to be registered with your Azure AD (AAD+MDM). Recommendation: Microsoft recommends Azure AD registration and automatic MDM enrollment for corporate devices (AAD+MDM) and personal devices (MSA+AAD+MDM). This requires Azure AD Premium. Identity management. Applies to: Corporate and personal devices. Employees can use only one account to initialize a device so it’s imperative that your organization controls which account is enabled first. The account chosen will determine who controls the device and influence your management capabilities. Note: Why must the user add an account to the device in OOBE? Windows 1. 0 Mobile are single user devices and the user accounts give access to a number of default cloud services that enhance the productivity and entertainment value of the phone for the user. Such services are: Store for downloading apps, Groove for music and entertainment, Xbox for gaming, etc. Both an MSA and an Azure AD account give access to these services. The following table describes the impact of identity choice on device management characteristics of the personal and corporate device scenarios. Identity choice considerations for device management. Personal identity. Work identity. First account on the device. Microsoft Account. Azure AD account. Ease of enrollment. Employees use their Microsoft Account to activate the device. Then, they use their Azure AD account (organizational identity) to register the device in Azure AD and enroll it with the company’s MDM solution (MSA+AAD+MDM).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |