mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Update metadata seo marvel 4_14 1
This commit is contained in:
1justingilmore
parent
fc8d5d8f70
commit
7e8f5e1aae
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
title: Add drivers to Windows 10 with Windows PE using Configuration Manager
|
||||
description: Learn how to configure the Windows Preinstallation Environment (Windows PE) to include required network and storage drivers.
|
||||
ms.assetid: 97b3ea46-28d9-407e-8c42-ded2e45e8d5c
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Enabling and Disabling Compatibility Fixes in Compatibility Administrator (Windows 10)
|
||||
title: Enabling and Disabling Compatibility Fixes in Compatibility Administrator
|
||||
description: You can disable and enable individual compatibility fixes in your customized databases for testing and troubleshooting purposes.
|
||||
ms.assetid: 6bd4a7c5-0ed9-4a35-948c-c438aa4d6cb6
|
||||
ms.reviewer:
|
||||
@ -12,6 +12,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Enabling and Disabling Compatibility Fixes in Compatibility Administrator
|
||||
|
||||
@ -1,113 +1,115 @@
|
||||
---
|
||||
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](https://docs.microsoft.com/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 (app whitelisting) with MDM, verify that system applications are whitelisted before you upgrade to Windows 10 Mobile. Also, be aware that there are [known issues](https://msdn.microsoft.com/library/windows/hardware/mt299056.aspx#whitelist) with app whitelisting 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 blacklist the Upgrade Advisor app to prevent their users from upgrading prematurely. For more information about how to blacklist the Upgrade Advisor app, see the [How to blacklist the Upgrade Advisor app](#howto-blacklist) section in this article. Enterprises that have blacklisted 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 blacklist the Upgrade Advisor app <a id="howto-blacklist"></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](https://technet.microsoft.com/windows/dn771706.aspx).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 Mobile and mobile device management](/windows/client-management/windows-10-mobile-and-mdm)
|
||||
---
|
||||
title: Upgrade Windows Phone 8.1 to Windows 10 Mobile in an MDM environment
|
||||
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
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# 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](https://docs.microsoft.com/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 (app whitelisting) with MDM, verify that system applications are whitelisted before you upgrade to Windows 10 Mobile. Also, be aware that there are [known issues](https://msdn.microsoft.com/library/windows/hardware/mt299056.aspx#whitelist) with app whitelisting 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 blacklist the Upgrade Advisor app to prevent their users from upgrading prematurely. For more information about how to blacklist the Upgrade Advisor app, see the [How to blacklist the Upgrade Advisor app](#howto-blacklist) section in this article. Enterprises that have blacklisted 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 blacklist the Upgrade Advisor app <a id="howto-blacklist"></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](https://technet.microsoft.com/windows/dn771706.aspx).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 Mobile and mobile device management](/windows/client-management/windows-10-mobile-and-mdm)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Step by step - Deploy Windows 10 using Microsoft Endpoint Configuration Manager
|
||||
title: Steps to deploy Windows 10 with Microsoft Endpoint Configuration Manager
|
||||
description: Deploy Windows 10 in a test lab using Microsoft Endpoint Configuration Manager
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,6 +14,7 @@ author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deploy Windows 10 in a test lab using Microsoft Endpoint Configuration Manager
|
||||
@ -108,11 +109,11 @@ Topics and procedures in this guide are summarized in the following table. An es
|
||||
5. Type the following commands at an elevated Windows PowerShell prompt on SRV1:
|
||||
|
||||
```
|
||||
New-NetFirewallRule -DisplayName “SQL Server” -Direction Inbound –Protocol TCP –LocalPort 1433 -Action allow
|
||||
New-NetFirewallRule -DisplayName “SQL Admin Connection” -Direction Inbound –Protocol TCP –LocalPort 1434 -Action allow
|
||||
New-NetFirewallRule -DisplayName “SQL Database Management” -Direction Inbound –Protocol UDP –LocalPort 1434 -Action allow
|
||||
New-NetFirewallRule -DisplayName “SQL Service Broker” -Direction Inbound –Protocol TCP –LocalPort 4022 -Action allow
|
||||
New-NetFirewallRule -DisplayName “SQL Debugger/RPC” -Direction Inbound –Protocol TCP –LocalPort 135 -Action allow
|
||||
New-NetFirewallRule -DisplayName "SQL Server" -Direction Inbound –Protocol TCP –LocalPort 1433 -Action allow
|
||||
New-NetFirewallRule -DisplayName "SQL Admin Connection" -Direction Inbound –Protocol TCP –LocalPort 1434 -Action allow
|
||||
New-NetFirewallRule -DisplayName "SQL Database Management" -Direction Inbound –Protocol UDP –LocalPort 1434 -Action allow
|
||||
New-NetFirewallRule -DisplayName "SQL Service Broker" -Direction Inbound –Protocol TCP –LocalPort 4022 -Action allow
|
||||
New-NetFirewallRule -DisplayName "SQL Debugger/RPC" -Direction Inbound –Protocol TCP –LocalPort 135 -Action allow
|
||||
```
|
||||
|
||||
7. Download and install the latest [Windows Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) on SRV1 using the default installation settings. The current version is the ADK for Windows 10, version 1703. Installation might require several minutes to acquire all components.
|
||||
@ -123,7 +124,7 @@ Topics and procedures in this guide are summarized in the following table. An es
|
||||
|
||||
```
|
||||
$AdminKey = "HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{A509B1A7-37EF-4b3f-8CFC-4F3A74704073}"
|
||||
Set-ItemProperty -Path $AdminKey -Name “IsInstalled” -Value 0
|
||||
Set-ItemProperty -Path $AdminKey -Name "IsInstalled" -Value 0
|
||||
Stop-Process -Name Explorer
|
||||
```
|
||||
|
||||
@ -207,7 +208,7 @@ Topics and procedures in this guide are summarized in the following table. An es
|
||||
19. If desired, re-enable IE Enhanced Security Configuration at this time on SRV1:
|
||||
|
||||
```
|
||||
Set-ItemProperty -Path $AdminKey -Name “IsInstalled” -Value 1
|
||||
Set-ItemProperty -Path $AdminKey -Name "IsInstalled" -Value 1
|
||||
Stop-Process -Name Explorer
|
||||
```
|
||||
|
||||
@ -387,7 +388,7 @@ WDSUTIL /Set-Server /AnswerClients:None
|
||||
In the trace tool, click **Tools** on the menu and choose **Find**. Search for "**STATMSG: ID=2301**". For example:
|
||||
|
||||
```
|
||||
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SRV1.CONTOSO.COM SITE=PS1 PID=924 TID=1424 GMTDATE=Tue Oct 09 22:36:30.986 2018 ISTR0="Zero Touch WinPE x64" ISTR1="PS10000A" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PS10000A" SMS_DISTRIBUTION_MANAGER 10/9/2018 3:36:30 PM 1424 (0x0590)
|
||||
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SRV1.CONTOSO.COM SITE=PS1 PID=924 TID=1424 GMTDATE=Tue Oct 09 22:36:30.986 2018 ISTR0="Zero Touch WinPE x64" ISTR1="PS10000A" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PS10000A" SMS_DISTRIBUTION_MANAGER 10/9/2018 3:36:30 PM 1424 (0x0590)
|
||||
```
|
||||
|
||||
11. You can also review status by clicking the **Zero Touch WinPE x64** image, and then clicking **Content Status** under **Related Objects** in the bottom right-hand corner of the console, or by entering **\Monitoring\Overview\Distribution Status\Content Status** on the location bar in the console. Double-click **Zero Touch WinPE x64** under **Content Status** in the console tree and verify that a status of **Successfully distributed content** is displayed on the **Success** tab.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user