mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
Merge branch 'master' into v-gmoor-add-periods-alt-text
This commit is contained in:
Rebecca Agiewich
GitHub
@ -29,10 +29,10 @@ ms.topic: article
|
||||
|
||||
## About SetupDiag
|
||||
|
||||
<I>Current downloadable version of SetupDiag: 1.6.2107.27002</I>
|
||||
>Always be sure to run the most recent version of SetupDiag, so that can access new functionality and fixes to known issues.
|
||||
<I>Current downloadable version of SetupDiag: 1.6.2107.27002.</I>
|
||||
> Always be sure to run the most recent version of SetupDiag, so that can access new functionality and fixes to known issues.
|
||||
|
||||
SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
|
||||
SetupDiag is a diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
|
||||
|
||||
SetupDiag works by examining Windows Setup log files. It attempts to parse these log files to determine the root cause of a failure to update or upgrade the computer to Windows 10. SetupDiag can be run on the computer that failed to update, or you can export logs from the computer to another location and run SetupDiag in offline mode.
|
||||
|
||||
@ -344,6 +344,10 @@ Each rule name and its associated unique rule identifier are listed with a descr
|
||||
|
||||
## Release notes
|
||||
|
||||
07/27/2021 - SetupDiag v1.6.2107.27002 is released with 61 rules, as a standalone tool available in the Download Center.
|
||||
- This version contains compliance updates and minor bug fixes.
|
||||
- With this release and subsequent releases, the version number of the downloadable SetupDiag tool is different from the one included with Windows Setup.
|
||||
|
||||
05/06/2021 - SetupDiag v1.6.1.0 is released with 61 rules, as a standalone tool available in the Download Center.
|
||||
- This version of SetupDiag is included with Windows 10, version 21H1.
|
||||
- A new rule is added: UserProfileSuffixMismatch.
|
||||
|
||||
@ -32,7 +32,7 @@ This topic describes how to submit problems with a Windows 10 upgrade to Microso
|
||||
|
||||
The Feedback Hub app lets you tell Microsoft about any problems you run in to while using Windows 10 and send suggestions to help us improve your Windows experience. Previously, you could only use the Feedback Hub if you were in the Windows Insider Program. Now anyone can use this tool. You can download the Feedback Hub app from the Microsoft Store [here](https://www.microsoft.com/store/p/feedback-hub/9nblggh4r32n?SilentAuth=1&wa=wsignin1.0).
|
||||
|
||||
The Feedback Hub requires Windows 10 or Windows 10 mobile. If you are having problems upgrading from an older version of Windows to Windows 10, you can use the Feedback Hub to submit this information, but you must collect the log files from the legacy operating system and then attach these files to your feedback using a device that is running Windows 10. If you are upgrading to Windows 10 from a previous verion of Windows 10, the Feedback Hub will collect log files automatically.
|
||||
The Feedback Hub requires Windows 10. If you are having problems upgrading from an older version of Windows to Windows 10, you can use the Feedback Hub to submit this information, but you must collect the log files from the legacy operating system and then attach these files to your feedback using a device that is running Windows 10. If you are upgrading to Windows 10 from a previous version of Windows 10, the Feedback Hub will collect log files automatically.
|
||||
|
||||
## Submit feedback
|
||||
|
||||
|
||||
@ -1,110 +0,0 @@
|
||||
---
|
||||
title: Upgrade Windows Phone 8.1 to Windows 10 Mobile in an MDM environment (Windows 10)
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
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
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdm
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management (MDM)
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 Mobile
|
||||
|
||||
## Summary
|
||||
|
||||
This article describes how system administrators can upgrade eligible Windows Phone 8.1 devices to Windows 10 Mobile using [Mobile Device Management](/windows/client-management/mdm/) (MDM).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you are not a system administrator, see the [Windows 10 Mobile Upgrade & Updates](https://www.microsoft.com/windows/windows-10-mobile-upgrade) page for details about updating your Windows 8.1 Mobile device to Windows 10 Mobile using the [Upgrade Advisor](https://www.microsoft.com/store/p/upgrade-advisor/9nblggh0f5g4).
|
||||
|
||||
## Upgrading with MDM
|
||||
|
||||
The Windows Phone 8.1 to Windows 10 Mobile upgrade uses an "opt-in" or "seeker" model. To determine if the device is eligible for an upgrade with MDM, see the [How to determine whether an upgrade is available for a device](#howto-upgrade-available) topic in this article. 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. For Enterprises, Microsoft is offering a centralized management solution through MDM that can push a management policy to each eligible device to perform the opt-in.
|
||||
|
||||
If you use a list of allowed applications (an app allowlist) with MDM, verify that system applications are allow-listed before you upgrade to Windows 10 Mobile. Also, be aware that there are [known issues](/windows/client-management/mdm/new-in-windows-mdm-enrollment-management) with app allowlists that could adversely affect the device after you upgrade.
|
||||
|
||||
Some enterprises might want to control the availability of the Windows 10 Mobile upgrade to their users. With the opt-in model, the enterprise can block the Upgrade Advisor app to prevent their users from upgrading prematurely. For more information about how to restrict the Upgrade Advisor app, see the [How to restrict the Upgrade Advisor app](#howto-restrict) section in this article. Enterprises that have restricted the Upgrade Advisor app can use the solution described in this article to select the upgrade timing on a per-device basis.
|
||||
|
||||
## More information
|
||||
|
||||
To provide enterprises with a solution that's independent of the Upgrade Advisor, a new registry key in the registry configuration service provider (CSP) is available. A special GUID key value is defined. When Microsoft Update (MU) detects the presence of the registry key value on a device, any available upgrade will be made available to the device.
|
||||
|
||||
### 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 an MDM session.
|
||||
- Device is able to receive the management policy.
|
||||
- MDM is capable of pushing the management policy to devices. Minimum version numbers for some popular MDM providers that support this solution 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>
|
||||
<CmdID>250</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Vendor/MSFT/Registry/HKLM/SOFTWARE/Microsoft/Provisioning/OMADM/EnterpriseUpgrade</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns=”syncml:metinf”>chr</Format>
|
||||
</Meta>
|
||||
<Data>d369c9b6-2379-466d-9162-afc53361e3c2</Data>
|
||||
</Item>
|
||||
</Add>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
The OMA DM server policy description is provided in the following table:
|
||||
|
||||
|Item |Setting |
|
||||
|------|------------|
|
||||
| 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, delete the **OMADM** registry key or set the **EnterpriseUpgrade** string value to anything other than the GUID.
|
||||
|
||||
### How to determine whether an upgrade is available for a device <a id="howto-upgrade-available"></a>
|
||||
|
||||
The Windows 10 Mobile Upgrade Advisor app is not designed or intended for Enterprise customers who want to automate the upgrade process. However, the Windows 10 Mobile Upgrade Advisor app is the best mechanism to determine when an upgrade is available. The app dynamically queries whether the upgrade is released for this device model and associated mobile operator (MO).
|
||||
|
||||
We recommend that enterprises use a pilot device with the Windows 10 Mobile Upgrade Advisor app installed. The pilot device provides the device model and MO used by the enterprise. When you run the app on the pilot device, it will tell you that either an upgrade is available, that the device is eligible for upgrade, or that an upgrade is not available for this device.
|
||||
|
||||
Note: The availability of Windows 10 Mobile as an update for existing Windows Phone 8.1 devices varies by device manufacturer, device model, country or region, mobile operator or service provider, hardware limitations, and other factors. To check for compatibility and other important installation information, see the [Windows 10 Mobile FAQ](https://support.microsoft.com/help/10599/windows-10-mobile-how-to-get) page.
|
||||
|
||||
### How to restrict the Upgrade Advisor app <a id="howto-restrict"></a>
|
||||
|
||||
Some enterprises may want to block their users from installing the Windows 10 Mobile Upgrade Advisor app. With Windows Phone 8.1, you can allow or deny individual apps by adding specific app publishers or the app globally unique identifier (GUID) from the Window Phone Store to an allow or deny XML list. The GUID for a particular application can be found in the URL for the app in the phone store. For example, the GUID to the Windows 10 Mobile Upgrade Adviser (fbe47e4f-7769-4103-910e-dca8c43e0b07) is displayed in the following URL:
|
||||
|
||||
http://windowsphone.com/s?appid=fbe47e4f-7769-4103-910e-dca8c43e0b07
|
||||
|
||||
For more information about how to do this, see [Try it out: restrict Windows Phone 8.1 apps](/previous-versions/windows/it-pro/windows-phone/cc182269(v=technet.10)).
|
||||
@ -20,7 +20,6 @@ ms.topic: article
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
With Windows 10, you can quickly upgrade from one edition of Windows 10 to another, provided the upgrade path is supported. For information on what edition of Windows 10 is right for you, see [Compare Windows 10 Editions](https://go.microsoft.com/fwlink/p/?LinkID=690882). For a comprehensive list of all possible upgrade paths to Windows 10, see [Windows 10 upgrade paths](windows-10-upgrade-paths.md). Downgrading the edition of Windows is discussed in the [License expiration](#license-expiration) section on this page.
|
||||
|
||||
@ -77,15 +76,12 @@ X = unsupported <BR>
|
||||
## Upgrade using mobile device management (MDM)
|
||||
- To upgrade desktop editions of Windows 10 using MDM, you'll need to enter the product key for the upgraded edition in the **UpgradeEditionWithProductKey** policy setting of the **WindowsLicensing** CSP. For more info, see [WindowsLicensing CSP](/windows/client-management/mdm/windowslicensing-csp).
|
||||
|
||||
- To upgrade mobile editions of Windows 10 using MDM, you'll need to enter the product key for the upgraded edition in the **UpgradeEditionWithLicense** policy setting of the **WindowsLicensing** CSP. For more info, see [WindowsLicensing CSP](/windows/client-management/mdm/windowslicensing-csp).
|
||||
|
||||
## Upgrade using a provisioning package
|
||||
Use Windows Configuration Designer to create a provisioning package to upgrade a desktop edition or mobile edition of Windows 10. To get started, [install Windows Configuration Designer from the Microsoft Store](https://www.microsoft.com/store/apps/9nblggh4tx22).
|
||||
Use Windows Configuration Designer to create a provisioning package to upgrade a desktop edition. To get started, [install Windows Configuration Designer from the Microsoft Store](https://www.microsoft.com/store/apps/9nblggh4tx22).
|
||||
|
||||
- To create a provisioning package for upgrading desktop editions of Windows 10, go to **Runtime settings > EditionUpgrade > UpgradeEditionWithProductKey** in the **Available customizations** panel in Windows ICD and enter the product key for the upgraded edition.
|
||||
|
||||
- To create a provisioning package for upgrading mobile editions of Windows 10, go to **Runtime settings > EditionUpgrade > UpgradeEditionWithLicense** in the **Available customizations** panel in Windows ICD and enter the product key for the upgraded edition.
|
||||
|
||||
For more info about Windows Configuration Designer, see these topics:
|
||||
- [Create a provisioning package for Windows 10](/windows/configuration/provisioning-packages/provisioning-create-package)
|
||||
- [Apply a provisioning package](/windows/configuration/provisioning-packages/provisioning-apply-package)
|
||||
@ -169,7 +165,7 @@ You can move directly from Enterprise to any valid destination edition. In this
|
||||
<th>Enterprise</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<th rowspan="9" nowrap="nowrap" valign="middle">Starting edition</th>
|
||||
<th rowspan="9" valign="middle">Starting edition</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Home</td>
|
||||
|
||||
@ -18,7 +18,6 @@ ms.topic: article
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
## Upgrade paths
|
||||
|
||||
@ -49,11 +48,9 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<th>Windows 10 Pro Education</th>
|
||||
<th>Windows 10 Education</th>
|
||||
<th>Windows 10 Enterprise</th>
|
||||
<th>Windows 10 Mobile</th>
|
||||
<th>Windows 10 Mobile Enterprise</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<th rowspan="7" nowrap="nowrap">Windows 7</th>
|
||||
<th rowspan="7">Windows 7</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Starter</td>
|
||||
@ -62,8 +59,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Home Basic</td>
|
||||
@ -72,8 +67,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Home Premium</td>
|
||||
@ -82,8 +75,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Professional</td>
|
||||
@ -92,8 +83,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Ultimate</td>
|
||||
@ -102,8 +91,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
@ -112,11 +99,9 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th rowspan="10" nowrap="nowrap">Windows 8.1</th>
|
||||
<th rowspan="10">Windows 8.1</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>(Core)</td>
|
||||
@ -125,8 +110,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Connected</td>
|
||||
@ -135,8 +118,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
@ -145,8 +126,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro Student</td>
|
||||
@ -155,8 +134,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro WMC</td>
|
||||
@ -165,8 +142,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
@ -175,8 +150,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Embedded Industry</td>
|
||||
@ -185,8 +158,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Windows RT</td>
|
||||
@ -195,8 +166,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Windows Phone 8.1</td>
|
||||
@ -205,11 +174,9 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td>✔</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th rowspan="8" nowrap="nowrap">Windows 10</th>
|
||||
<th rowspan="8">Windows 10</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Home</td>
|
||||
@ -218,8 +185,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
@ -228,8 +193,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
@ -238,8 +201,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td>D</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
@ -248,20 +209,8 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td></td>
|
||||
<td>✔</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Mobile</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td>✔</td>
|
||||
</tr>
|
||||
</table>
|
||||
</table>
|
||||
|
||||
|
||||
## Related Topics
|
||||
|
||||
Reference in New Issue
Block a user