deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 19:03:46 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

formatting fixes

Browse Source
This commit is contained in:
Greg Lindsay
2016-05-31 13:14:07 -07:00
parent 04380fad15
commit fb0f31b3d8
2 changed files with 19 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
windows/deploy/TOC.md
View File

@ -21,7 +21,6 @@
#### [Assign applications using roles in MDT](assign-applications-using-roles-in-mdt-2013.md)
#### [Use web services in MDT](use-web-services-in-mdt-2013.md)
#### [Use Orchestrator runbooks with MDT](use-orchestrator-runbooks-with-mdt-2013.md)
### [Upgrade Windows Phone 8.1 to Windows 10](upgrade-windows-phone-8-1-to-10.md)
## [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md)
### [Integrate Configuration Manager with MDT 2013 Update 2](integrate-configuration-manager-with-mdt-2013.md)
### [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)

27
windows/deploy/upgrade-windows-phone-8-1-to-10.md
View File

@ -1,6 +1,6 @@
---
title: Deploy Windows 10 using PXE (Windows 10)
description: PXE-initiated operating system deployments in System Center Configuration Manager let client computers request and deploy operating systems over the network. In this operating system deployment scenario, the operating system image and both the x86 and x64 Windows PE boot images are sent to a distribution point that is configured to accept PXE boot requests.
title: Upgrade Windows Phone 8.1 to Windows 10 Mobile in an MDM environment (Windows 10)
description: This article describes how to upgrade eligible Windows Phone 8.1 devices to Windows 10 Mobile using MDM.
keywords: upgrade, update, windows, phone, windows 10, mdm, mobile
ms.prod: W10
ms.mktglfcycl: deploy
@ -14,7 +14,7 @@ author: greg-lindsay
## Summary
This article describes how to upgrade eligible Windows Phone 8.1 devices to Windows 10 Mobile. See the How to determine whether an upgrade is available for a device section to determine whether your device is eligible for the update.
The Windows Phone 8.1 to Windows 10 Mobile upgrade uses an "opt-in" or "seeker" model. An eligible device must "opt-in" to be offered the upgrade.
The Windows Phone 8.1 to Windows 10 Mobile upgrade uses an "opt-in" or "seeker" model. An eligible device must opt-in to be offered the upgrade.
For consumers, the Windows 10 Mobile Upgrade Advisor app is available from the Windows Store to perform the opt-in.
@ -30,23 +30,27 @@ To provide enterprises with a solution that's independent of the Upgrade Advisor
### Prerequisites
•Windows Phone 8.1 device with an available upgrade to Windows 10 Mobile.
•Device connected to Wi-Fi or cellular network to perform scan for upgrade.
•Device is already enrolled with a MDM session.
•Device is able to receive the management policy.
•MDM is capable of pushing the management policy to devices. (The minimum version for popular MDM providers that support the solution in this article are: InTune: 5.0.5565, AirWatch: 8.2, Mobile Iron: 9.0.)
- Windows Phone 8.1 device with an available upgrade to Windows 10 Mobile.
- Device connected to Wi-Fi or cellular network to perform scan for upgrade.
- Device is already enrolled with a MDM session.
- Device is able to receive the management policy.
- MDM is capable of pushing the management policy to devices. (The minimum version for popular MDM providers that support the solution in this article are: InTune: 5.0.5565, AirWatch: 8.2, Mobile Iron: 9.0.)
### Instructions for the MDM server
The registry CSP is used to push the GUID value to the following registry key for which the Open Mobile Alliance (OMA) Device Management (DM) client has Read/Write access and for which the Device Update service has Read access.
```
[HKLM\Software\Microsoft\Provisioning\OMADM]
"EnterpriseUpgrade"="d369c9b6-2379-466d-9162-afc53361e3c2”
```
The complete SyncML command for the solution is as follows.
Note The SyncML may vary, depending on your MDM solution.
```
SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Add>
@ -64,12 +68,19 @@ SyncML xmlns="SYNCML:SYNCML1.1">
<Final/>
</SyncBody>
</SyncML>
```
The OMA DM server policy description is provided in the following table:
```
OMA-URI ./Vendor/MSFT/Registry/HKLM/SOFTWARE/Microsoft/Provisioning/OMADM/EnterpriseUpgrade
```
Data Type String
```
Value d369c9b6-2379-466d-9162-afc53361e3c2
```
After the device consumes the policy, it will be able to receive an available upgrade.
To disable the policy, either delete the OMADM registry key or set the EnterpriseUpgrade string value to anything other than the GUID.