mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 03:43:39 +00:00
Merge branch 'master' into 19h1
This commit is contained in:
Dani Halfin
@ -14,12 +14,15 @@ ms.topic: article
|
||||
|
||||
# Deploy Windows 10 Enterprise licenses
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Office 365 Enterprise E3 and Office 365 Enterprise E5 include a Windows 10 Enterprise license. This article is about the use and implementation of these licenses in a on-premises Active Directory environment.
|
||||
|
||||
This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md) or [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD).
|
||||
|
||||
>[!NOTE]
|
||||
>Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.<BR>
|
||||
>Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.<BR>
|
||||
>Automatic, non-KMS activation requires Windows 10, version 1803 or later on a device with a firmware-embedded activation key.<BR>
|
||||
>* Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.
|
||||
>* Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.
|
||||
>* Automatic, non-KMS activation requires Windows 10, version 1803 or later, on a device with a firmware-embedded activation key.
|
||||
|
||||
## Firmware-embedded activation key
|
||||
|
||||
@ -35,9 +38,9 @@ If the device has a firmware-embedded activation key, it will be displayed in th
|
||||
|
||||
If you are an EA customer with an existing Office 365 tenant, use the following steps to enable Windows 10 Subscription licenses on your existing tenant:
|
||||
|
||||
1. Work with your reseller to place an order for one $0 SKU per user. There are two SKUs available, depending on their current Windows Enterprise SA license:<BR>
|
||||
a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3<BR>
|
||||
b. **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5<BR>
|
||||
1. Work with your reseller to place an order for one $0 SKU per user. There are two SKUs available, depending on their current Windows Enterprise SA license:
|
||||
- **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3
|
||||
- **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5
|
||||
2. After placing an order, the OLS admin on the agreement will receive a service activation email, indicating their subscription licenses have been provisioned on the tenant.
|
||||
3. The admin can now assign subscription licenses to users.
|
||||
|
||||
@ -59,7 +62,7 @@ Also in this article:
|
||||
|
||||
You probably have on-premises Active Directory Domain Services (AD DS) domains. Users will use their domain-based credentials to sign in to the AD DS domain. Before you start deploying Windows 10 Enterprise E3 or E5 licenses to users, you need to synchronize the identities in the on-premises ADDS domain with Azure AD.
|
||||
|
||||
You might ask why you need to synchronize these identities. The answer is so that users will have a *single identity* that they can use to access their on-premises apps and cloud services that use Azure AD (such as Windows 10 Enterprise E3 or E5). This means that users can use their existing credentials to sign in to Azure AD and access the cloud services that you provide and manage for them.
|
||||
You might ask why you need to synchronize these identities. The answer is so that users will have a *single identity* that they can use to access their on-premises apps and cloud services that use Azure AD (such as Windows 10 Enterprise E3 or E5). This means that users can use their existing credentials to sign in to Azure AD and access the cloud services that you provide and manage for them.
|
||||
|
||||
**Figure 1** illustrates the integration between the on-premises AD DS domain with Azure AD. [Microsoft Azure Active Directory Connect](https://www.microsoft.com/en-us/download/details.aspx?id=47594) (Azure AD Connect) is responsible for synchronization of identities between the on-premises AD DS domain and Azure AD. Azure AD Connect is a service that you can install on-premises or in a virtual machine in Azure.
|
||||
|
||||
@ -72,6 +75,9 @@ For more information about integrating on-premises AD DS domains with Azure AD,
|
||||
- [Integrating your on-premises identities with Azure Active Directory](https://azure.microsoft.com/documentation/articles/active-directory-aadconnect/)
|
||||
- [Azure AD + Domain Join + Windows 10](https://blogs.technet.microsoft.com/enterprisemobility/2016/02/17/azure-ad-domain-join-windows-10/)
|
||||
|
||||
>[!NOTE]
|
||||
>If you are implementing Azure AD, and you already have an on-premises domain, you don't need to integrate with Azure AD, since your main authentication method is your internal AD. If you want to manage all your infrastructure in the cloud, you can safely configure your domain controller remotely to integrate your computers with Azure AD, but you won't be able to apply fine controls using GPO. Azure AD is best suited for the global administration of devices when you don't have any on-premises servers.
|
||||
|
||||
## Preparing for deployment: reviewing requirements
|
||||
|
||||
Devices must be running Windows 10 Pro, version 1703, and be Azure Active Directory joined, or hybrid domain joined with Azure AD Connect. Customers who are federated with Azure Active Directory are also eligible. For more information, see [Review requirements on devices](#review-requirements-on-devices), later in this topic.
|
||||
@ -151,12 +157,12 @@ Now the device is Azure AD joined to the company’s subscription.
|
||||
### Step 2: Pro edition activation
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If the device is running Windows 10, version 1803 or later, this step is no longer necessary when there is a firmware-embedded activation key on the device. Starting with Windows 10, version 1803 the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key.<br>
|
||||
>If your device is running Windows 10, version 1803 or later, this step is not needed. From Windows 10, version 1803, the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key.
|
||||
>If the device is running Windows 10, version 1703 or 1709, then Windows 10 Pro must be successfully activated in **Settings > Update & Security > Activation**, as illustrated in **Figure 7a**.
|
||||
|
||||
<span id="win-10-pro-activated"/>
|
||||
<img src="images/sa-pro-activation.png" alt="Windows 10 Pro activated" width="710" height="440" />
|
||||
<BR>**Figure 7a - Windows 10 Pro activation in Settings** <BR>
|
||||
**Figure 7a - Windows 10 Pro activation in Settings**
|
||||
|
||||
Windows 10 Pro activation is required before Enterprise E3 or E5 can be enabled (Windows 10, versions 1703 and 1709 only).
|
||||
|
||||
@ -176,16 +182,16 @@ You can verify the Windows 10 Enterprise E3 or E5 subscription in **Settings &g
|
||||
<span id="win-10-activated-subscription-active"/>
|
||||
<img src="images/enterprise-e3-win-10-activated-enterprise-subscription-active.png" alt="Windows 10 activated and subscription active" width="624" height="407" />
|
||||
|
||||
<BR>**Figure 9 - Windows 10 Enterprise subscription in Settings** <BR>
|
||||
**Figure 9 - Windows 10 Enterprise subscription in Settings**
|
||||
|
||||
|
||||
If there are any problems with the Windows 10 Enterprise E3 or E5 license or the activation of the license, the **Activation** panel will display the appropriate error message or status. You can use this information to help you diagnose the licensing and activation process.
|
||||
|
||||
>[!NOTE]
|
||||
>If you use slmgr /dli or /dlv commands to retrieve the activation information for the Windows 10 E3 or E5 license, the license information displayed will be the following:<BR>
|
||||
>Name: Windows(R), Professional edition<BR>
|
||||
>Description: Windows(R) Operating System, RETAIL channel<BR>
|
||||
>Partial Product Key: 3V66T<BR>
|
||||
>If you use slmgr /dli or /dlv commands to retrieve the activation information for the Windows 10 E3 or E5 license, the license information displayed will be the following:
|
||||
>Name: Windows(R), Professional edition
|
||||
>Description: Windows(R) Operating System, RETAIL channel
|
||||
>Partial Product Key: 3V66T
|
||||
|
||||
## Virtual Desktop Access (VDA)
|
||||
|
||||
@ -211,23 +217,20 @@ Use the following figures to help you troubleshoot when users experience these c
|
||||
|
||||
- [Figure 12](#win-10-not-activated-subscription-not-active) (below) illustrates a device on which Windows 10 Pro license is not activated and the Windows 10 Enterprise subscription is lapsed or removed.
|
||||
|
||||
<BR>
|
||||
|
||||
<span id="win-10-not-activated"/>
|
||||
<img src="images/enterprise-e3-win-10-not-activated-enterprise-subscription-active.png" alt="Windows 10 not activated and subscription active" width="624" height="407" />
|
||||
<BR>**Figure 10 - Windows 10 Pro, version 1703 edition not activated in Settings**<BR>
|
||||
**Figure 10 - Windows 10 Pro, version 1703 edition not activated in Settings**
|
||||
|
||||
<BR>
|
||||
|
||||
<span id="subscription-not-active"/>
|
||||
<img src="images/enterprise-e3-win-10-activated-enterprise-subscription-not-active.png" alt="Windows 10 activated and subscription not active" width="624" height="407" />
|
||||
<BR>**Figure 11 - Windows 10 Enterprise subscription lapsed or removed in Settings**<BR>
|
||||
**Figure 11 - Windows 10 Enterprise subscription lapsed or removed in Settings**
|
||||
|
||||
<BR>
|
||||
|
||||
<span id="win-10-not-activated-subscription-not-active"/>
|
||||
<img src="images/enterprise-e3-win-10-not-activated-enterprise-subscription-not-active.png" alt="Windows 10 not activated and subscription not active" width="624" height="407" />
|
||||
<BR>**Figure 12 - Windows 10 Pro, version 1703 edition not activated and Windows 10 Enterprise subscription lapsed or removed in Settings**<BR>
|
||||
**Figure 12 - Windows 10 Pro, version 1703 edition not activated and Windows 10 Enterprise subscription lapsed or removed in Settings**
|
||||
|
||||
|
||||
### Review requirements on devices
|
||||
|
||||
@ -111,7 +111,7 @@ In either of these scenarios, you can make a variety of configuration changes to
|
||||
## Stay up to date
|
||||
|
||||
|
||||
For computers already running Windows 10 on the Current Branch or Current Branch for Business, new upgrades will periodically be deployed, approximately two to three times per year. You can deploy these upgrades by using a variety of methods:
|
||||
For computers already running Windows 10 on the Semi-Annual Channel, new upgrades will periodically be deployed, approximately two to three times per year. You can deploy these upgrades by using a variety of methods:
|
||||
|
||||
- Windows Update or Windows Update for Business, for devices where you want to receive updates directly from the Internet.
|
||||
|
||||
|
||||
@ -18,6 +18,13 @@ The Update Compliance solution of Windows Analytics provides you with informatio
|
||||
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> There are currently two known issues affecting the Delivery Optimization status displayed in these blades:
|
||||
>- Devices running Windows 10, version 1803 or older versions are not sending the correct configuration profile. As a result, the information in the Device Configuration blade might not accurately reflect the settings in your environment.
|
||||
>- Some devices running Windows 10, version 1809 report the Delivery Optimization DownloadMode configuration value as the sequential value in the list of possible configurations rather than the actual configured value. For example, a device that is configured as HTTP + Group (2), will be shown as HTTP + Internet (3) in Update Compliance.
|
||||
>
|
||||
>Look for fixes for both of these issues in a forthcoming update.
|
||||
|
||||
## Delivery Optimization Status
|
||||
|
||||
The Delivery Optimization Status section includes three blades:
|
||||
|
||||
@ -5,9 +5,9 @@ keywords: oms, operations management suite, wdav, updates, downloads, log analyt
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: JaimeO
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
@ -37,7 +37,7 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz
|
||||
| --- | --- | --- |
|
||||
| [Download mode](#download-mode) | DODownloadMode | 1511 |
|
||||
| [Group ID](#group-id) | DOGroupID | 1511 |
|
||||
| [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | 1703 |
|
||||
| [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | 1703 |
|
||||
| [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) | DOMinDiskSizeAllowedToPeer | 1703 |
|
||||
| [Max Cache Age](#max-cache-age) | DOMaxCacheAge | 1511 |
|
||||
| [Max Cache Size](#max-cache-size) | DOMaxCacheSize | 1511 |
|
||||
@ -70,7 +70,7 @@ Delivery Optimization uses locally cached updates. In cases where devices have a
|
||||
- The system drive is the default location for the Delivery Optimization cache. [Modify Cache Drive](#modify-cache-drive) allows administrators to change that location.
|
||||
|
||||
>[!NOTE]
|
||||
>It is possible to configure preferred cache devices. For more information, see [Set “preferred” cache devices for Delivery Optimization](#set-preferred-cache-devices).
|
||||
>It is possible to configure preferred cache devices. For more information, see [Group ID](#group-id).
|
||||
|
||||
All cached files have to be above a set minimum size. This size is automatically set by the Delivery Optimization cloud services, but when local storage is sufficient and the network isn't strained or congested, administrators might choose to change it to obtain increased performance. You can set the minimum size of files to cache by adjusting [Minimum Peer Caching Content File Size](#minimum-peer-caching-content-file-size).
|
||||
|
||||
@ -79,7 +79,7 @@ Additional options available that control the impact Delivery Optimization has o
|
||||
- [Max Upload Bandwidth](#max-upload-bandwidth) controls the Delivery Optimization upload bandwidth usage.
|
||||
- [Monthly Upload Data Cap](#monthly-upload-data-cap) controls the amount of data a client can upload to peers each month.
|
||||
- [Minimum Background QoS](#minimum-background-qos) lets administrators guarantee a minimum download speed for Windows updates. This is achieved by adjusting the amount of data downloaded directly from Windows Update or WSUS servers, rather than other peers in the network.
|
||||
- [Maximum Foreground Download Bandwidth](#maximum-foreground-download-bandwidth) specifies the maximum background download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.
|
||||
- [Maximum Foreground Download Bandwidth](#maximum-foreground-download-bandwidth) specifies the maximum foreground download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.
|
||||
- [Maximum Background Download Bandwidth](#maximum-background-download-bandwidth) specifies the maximum background download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.
|
||||
- [Set Business Hours to Limit Background Download Bandwidth](#set-business-hours-to-limit-background-download-bandwidth) specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
|
||||
- [Set Business Hours to Limit Foreground Download Bandwidth](#set-business-hours-to-limit-foreground-download-bandwidth) specifies the maximum foreground download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
|
||||
@ -89,7 +89,7 @@ Additional options available that control the impact Delivery Optimization has o
|
||||
- [Delay foreground download from http (in secs)](#delay-foreground-download-from-http-in-secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use P2P.
|
||||
|
||||
Administrators can further customize scenarios where Delivery Optimization will be used with the following settings:
|
||||
- [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) sets the minimum RAM required for peer caching to be enabled.
|
||||
- [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) sets the minimum RAM required for peer caching to be enabled.
|
||||
- [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) sets the minimum disk size required for peer caching to be enabled.
|
||||
- [Enable Peer Caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) allows clients connected through VPN to use peer caching.
|
||||
- [Allow uploads while the device is on battery while under set Battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) controls the minimum battery level required for uploads to occur. You must enable this policy to allow upload while on battery.
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: oms, operations management suite, wdav, updates, downloads, log analyt
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: JaimeO
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-modern-desktop
|
||||
@ -110,8 +110,46 @@ For the payloads (optional):
|
||||
|
||||
**Does Delivery Optimization use multicast?**: No. It relies on the cloud service for peer discovery, resulting in a list of peers and their IP addresses. Client devices then connect to their peers to obtain download files over TCP/IP.
|
||||
|
||||
[//]: # (**What data does Delivery Optimization send to the service?**)
|
||||
[//]: # (??????????????? I'm not sure we can avoid sharing this, per GDPR guidelines)
|
||||
## Troubleshooting
|
||||
|
||||
This section summarizes common problems and some solutions to try.
|
||||
|
||||
### If you don't see any bytes from peers
|
||||
|
||||
If you don’t see any bytes coming from peers the cause might be one of the following issues:
|
||||
|
||||
- Clients aren’t able to reach the Delivery Optimization cloud services.
|
||||
- The cloud service doesn’t see other peers on the network.
|
||||
- Clients aren’t able to connect to peers that are offered back from the cloud service.
|
||||
|
||||
|
||||
### Clients aren't able to reach the Delivery Optimization cloud services.
|
||||
|
||||
If you suspect this is the problem, try these steps:
|
||||
|
||||
1. Start a download of an app that is larger than 50 MB from the Store (for example "Candy Crush Saga").
|
||||
2. Run `Get-DeliveryOptimizationStatus` from an elevated Powershell window and observe the DownloadMode setting. For peering to work, DownloadMode should be 1, 2, or 3.
|
||||
3. If **DownloadMode** is 99 it could indicate your device is unable to reach the Delivery Optimization cloud services. Ensure that the Delivery Optimization hostnames are allowed access: most importantly **\*.do.dsp.mp.microsoft.com**.
|
||||
|
||||
|
||||
|
||||
### The cloud service doesn't see other peers on the network.
|
||||
|
||||
If you suspect this is the problem, try these steps:
|
||||
|
||||
1. Download the same app on two different devices on the same network, waiting 10 – 15 minutes between downloads.
|
||||
2. Run `Get-DeliveryOptimizationStatus` from an elevated Powershell window and ensure that **DownloadMode** is 1 or 2 on both devices.
|
||||
3. Run `Get-DeliveryOptimizationPerfSnap` from an elevated Powershell window on the second device. The **NumberOfPeers** field should be non-zero.
|
||||
4. If the number of peers is zero and you have **DownloadMode** = 1, ensure that both devices are using the same public IP address to reach the internet. To do this, open a browser Windows and search for “what is my IP”. You can **DownloadMode 2** (Group) and a custom GroupID (Guid) to fix this if the devices aren’t reporting the same public IP address.
|
||||
|
||||
|
||||
### Clients aren't able to connect to peers offered by the cloud service
|
||||
|
||||
If you suspect this is the problem, try a Telnet test between two devices on the network to ensure they can connect using port 7680. To do this, follow these steps:
|
||||
|
||||
1. Install Telnet by running **dism /online /Enable-Feature /FeatureName:TelnetClient** from an elevated command prompt.
|
||||
2. Run the test. For example, if you are on device with IP 192.168.8.12 and you are trying to test the connection to 192.168.9.17 run **telnet 192.168.9.17 7680** (the syntax is *telnet [destination IP] [port]*. You will either see a connection error or a blinking cursor like this /_. The blinking cursor means success.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -85,13 +85,13 @@ Starting with Windows 10, version 1709, the Windows Update for Business settings
|
||||
| Manage Windows Insider Preview builds | System/AllowBuildPreview | Update/ManagePreviewBuilds |
|
||||
| Manage when updates are received | Select when Feature Updates are received | Select when Preview Builds and Feature Updates are received (Update/BranchReadinessLevel) |
|
||||
|
||||
## Managing Windows Update for Business with Software Center Configuration Manager
|
||||
## Managing Windows Update for Business with System Center Configuration Manager
|
||||
|
||||
Starting with Windows 10, version 1709, you can assign a collection of devices to have dual scan enabled and manage that collection with Windows Update for Business policies. Starting with Windows 10, version 1809, you can set a collection of devices to receive the Windows Insider Preview Feature Updates from Windows Update from within Software Center Configuration Manager.
|
||||
Starting with Windows 10, version 1709, you can assign a collection of devices to have dual scan enabled and manage that collection with Windows Update for Business policies. Starting with Windows 10, version 1809, you can set a collection of devices to receive the Windows Insider Preview Feature Updates from Windows Update from within System Center Configuration Manager.
|
||||
|
||||
| Action | Windows 10 versions between 1709 and 1809 | Windows 10 versions after 1809 |
|
||||
| --- | --- | --- |
|
||||
| Manage Windows Update for Business in Configuration Manager | Manage Feature or Quality Updates with Windows Update for Business via Dual Scan | Manage Insider pre-release builds with Windows Update for Business within Software Center Configuration Manager |
|
||||
| Manage Windows Update for Business in Configuration Manager | Manage Feature or Quality Updates with Windows Update for Business via Dual Scan | Manage Insider pre-release builds with Windows Update for Business within System Center Configuration Manager |
|
||||
|
||||
## Managing Windows Update for Business with Windows Settings options
|
||||
Windows Settings includes options to control certain Windows Update for Business features:
|
||||
|
||||
@ -69,8 +69,8 @@ Click the following Microsoft Mechanics video for an overview of the updated rel
|
||||
|
||||
## Learn more
|
||||
|
||||
[Adopting Windows as a service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft)
|
||||
|
||||
- [Adopting Windows as a service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft)
|
||||
- [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet)
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -42,6 +42,9 @@ When **Configure Automatic Updates** is enabled in Group Policy, you can enable
|
||||
- **Turn off auto-restart for updates during active hours** prevents automatic restart during active hours.
|
||||
- **No auto-restart with logged on users for scheduled automatic updates installations** prevents automatic restart when a user is signed in. If a user schedules the restart in the update notification, the device will restart at the time the user specifies even if a user is signed in at the time. This policy only applies when **Configure Automatic Updates** is set to option **4-Auto download and schedule the install**.
|
||||
|
||||
> [!NOTE]
|
||||
> When using Remote Desktop Protocol connections, only active RDP sessions are considered as logged on users. Devices that do not have locally logged on users, or active RDP sessions, will be restarted.
|
||||
|
||||
You can also use Registry, to prevent automatic restarts when a user is signed in. Under **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU**, set **AuOptions** to **4** and enable **NoAutoRebootWithLoggedOnUsers**. As with Group Policy, if a user schedules the restart in the update notification, it will override this setting.
|
||||
|
||||
For a detailed description of these registry keys, see [Registry keys used to manage restart](#registry-keys-used-to-manage-restart).
|
||||
@ -159,8 +162,9 @@ In the Group Policy editor, you will see a number of policy settings that pertai
|
||||
|
||||
>[!NOTE]
|
||||
>You can only choose one path for restart behavior.
|
||||
>
|
||||
>If you set conflicting restart policies, the actual restart behavior may not be what you expected.
|
||||
>When using RDP, only active RDP sessions are considered as logged on users.
|
||||
|
||||
|
||||
## Registry keys used to manage restart
|
||||
The following tables list registry values that correspond to the Group Policy settings for controlling restarts after updates in Windows 10.
|
||||
|
||||
@ -86,7 +86,7 @@ If you have devices that appear in other solutions, but not Device Health (the D
|
||||
3. Verify that the Commercial ID is present in the device's registry. For details see [https://gpsearch.azurewebsites.net/#13551](https://gpsearch.azurewebsites.net/#13551).
|
||||
4. Confirm that devices have opted in to provide diagnostic data by checking in the registry that **AllowTelemetry** is set to 2 (Enhanced) or 3 (Full) in **HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\DataCollection** (or **HKLM\Software\Policies\Microsoft\Windows\DataCollection**, which takes precedence if set).
|
||||
5. Verify that devices can reach the endpoints specified in [Enrolling devices in Windows Analytics](windows-analytics-get-started.md). Also check settings for SSL inspection and proxy authentication; see [Configuring endpoint access with SSL inspection](https://docs.microsoft.com/windows/deployment/update/windows-analytics-get-started#configuring-endpoint-access-with-ssl-inspection) for more information.
|
||||
6. Remove the Device Health (appears as DeviceHealthProd on some pages) from your Log Analytics workspace
|
||||
6. Add the Device Health solution back to your Log Analytics workspace.
|
||||
7. Wait 48 hours for activity to appear in the reports.
|
||||
8. If you need additional troubleshooting, contact Microsoft Support.
|
||||
|
||||
|
||||
@ -12,16 +12,7 @@ ms.collection: M365-analytics
|
||||
|
||||
# Upgrade Readiness data sharing
|
||||
|
||||
To enable data sharing with the Upgrade Readiness solution, the following endpoints must be accessible:
|
||||
|
||||
|
||||
| **Endpoint** | **Function** |
|
||||
|---------------------------------------------------------|-----------|
|
||||
| `https://v10.vortex-win.data.microsoft.com/collect/v1`<br>`https://Vortex-win.data.microsoft.com/health/keepalive` | Connected User Experiences and Telemetry component endpoint. User computers send data to Microsoft through this endpoint. |
|
||||
| `https://settings.data.microsoft.com/qos` | Enables the compatibility update KB to send data to Microsoft. |
|
||||
| `https://go.microsoft.com/fwlink/?LinkID=544713`<br>`https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc` | This service provides driver information about whether there will be a driver available post-upgrade for the hardware on the system. |
|
||||
|
||||
Whitelist these endpoints on your network. This might require working with your organizations's network security group.
|
||||
To enable data sharing with the Upgrade Readiness solution, double-check the endpoints list in [Enrolling devices in Windows Analytics](../update/windows-analytics-get-started.md#enable-data-sharing) to be sure they are whitelisted.
|
||||
|
||||
## Connectivity to the Internet
|
||||
|
||||
@ -38,10 +29,10 @@ In order to use the direct connection scenario, set the parameter **ClientProxy=
|
||||
This is the first and most simple proxy scenario. The WinHTTP stack was designed for use in services and does not support proxy autodetection, PAC scripts or authentication.
|
||||
|
||||
In order to set the WinHTTP proxy system-wide on your computers, you need to
|
||||
•Use the command netsh winhttp set proxy \<server\>:\<port\>
|
||||
•Set ClientProxy=System in runconfig.bat
|
||||
- Use the command netsh winhttp set proxy \<server\>:\<port\>
|
||||
- Set ClientProxy=System in runconfig.bat
|
||||
|
||||
The WinHTTP scenario is most appropriate for customers who use a single proxy or f. If you have more advanced proxy requirements, refer to Scenario 3.
|
||||
The WinHTTP scenario is most appropriate for customers who use a single proxy. If you have more advanced proxy requirements, refer to Scenario 3.
|
||||
|
||||
If you want to learn more about proxy considerations on Windows, see [Understanding Web Proxy Configuration](https://blogs.msdn.microsoft.com/ieinternals/2013/10/11/understanding-web-proxy-configuration/).
|
||||
|
||||
|
||||
@ -12,6 +12,9 @@ ms.topic: article
|
||||
|
||||
# Use Upgrade Readiness to manage Windows upgrades
|
||||
|
||||
>[!IMPORTANT]
|
||||
>>**The OMS portal has been deprecated, so you need to switch to the [Azure portal](https://portal.azure.com) now.** The two portals offer the same experience, with some key differences. Learn how to use [Windows Analytics in the Azure Portal](../update/windows-analytics-azure-portal.md). Find out more about the [OMS portal moving to Azure](https://docs.microsoft.com/azure/log-analytics/log-analytics-oms-portal-transition), or jump right in and [Get started with Upgrade Readiness](https://docs.microsoft.com/windows/deployment/upgrade/upgrade-readiness-get-started).
|
||||
|
||||
You can use Upgrade Readiness to prioritize and work through application and driver issues, assign and track issue resolution status, and identify computers that are ready to upgrade. Upgrade Readiness enables you to deploy Windows with confidence, knowing that you’ve addressed potential blocking issues.
|
||||
|
||||
- Based on diagnostic data from user computers, Upgrade Readiness identifies application and driver compatibility issues that may block Windows upgrades, allowing you to make data-driven decisions about your organization’s upgrade readiness.
|
||||
|
||||
@ -12,21 +12,24 @@ ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows error reporting
|
||||
# Windows Error Reporting
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
>[!NOTE]
|
||||
>This is a 300 level topic (moderately advanced).<br>
|
||||
>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
|
||||
> This is a 300 level topic (moderately advanced).
|
||||
> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
|
||||
|
||||
|
||||
When Windows Setup fails, the result and extend code are recorded as an informational event in the Application log by Windows Error Reporting as event 1001. The event name is **WinSetupDiag02**. You can use Event Viewer to review this event, or you can use Windows PowerShell.
|
||||
|
||||
To use Windows PowerShell, type the following commands from an elevated Windows PowerShell prompt:
|
||||
|
||||
```
|
||||
>[!IMPORTANT]
|
||||
>}The following source will be available only if you have updated from a previous version of Windows 10 to a new version. If you installed the current version and have not updated, the source named **WinSetupDiag02** will be unavailable.
|
||||
|
||||
```Powershell
|
||||
$events = Get-WinEvent -FilterHashtable @{LogName="Application";ID="1001";Data="WinSetupDiag02"}
|
||||
$event = [xml]$events[0].ToXml()
|
||||
$event.Event.EventData.Data
|
||||
@ -40,19 +43,20 @@ To use Event Viewer:
|
||||
Note: For legacy operating systems, the Event Name was WinSetupDiag01.
|
||||
|
||||
Ten parameters are listed in the event:
|
||||
<br>
|
||||
<table border="0">
|
||||
<tr><td>P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool)</td></tr>
|
||||
<tr><td>P2: Setup Mode (x=default,1=Downlevel,5=Rollback)</td></tr>
|
||||
<tr><td>P3: New OS Architecture (x=default,0=X86,9=AMD64)</td></tr>
|
||||
<tr><td>P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked)</td></tr>
|
||||
<tr><td><b>P5: Result Error Code</b> (Ex: 0xc1900101)</td></tr>
|
||||
<tr><td><b>P6: Extend Error Code</b> (Ex: 0x20017)</td></tr>
|
||||
<tr><td>P7: Source OS build (Ex: 9600)</td></tr>
|
||||
<tr><td>P8: Source OS branch (not typically available)</td></tr>
|
||||
<tr><td>P9: New OS build (Ex: 16299}</td></tr>
|
||||
<tr><td>P10: New OS branch (Ex: rs3_release}</td></tr>
|
||||
</table>
|
||||
|
||||
| Parameters |
|
||||
| ------------- |
|
||||
|P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool) |
|
||||
|P2: Setup Mode (x=default,1=Downlevel,5=Rollback) |
|
||||
|P3: New OS Architecture (x=default,0=X86,9=AMD64) |
|
||||
|P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked) |
|
||||
|**P5: Result Error Code** (Ex: 0xc1900101) |
|
||||
|**P6: Extend Error Code** (Ex: 0x20017) |
|
||||
|P7: Source OS build (Ex: 9600) |
|
||||
|P8: Source OS branch (not typically available) |
|
||||
|P9: New OS build (Ex: 16299} |
|
||||
|P10: New OS branch (Ex: rs3_release} |
|
||||
|
||||
|
||||
The event will also contain links to log files that can be used to perform a detailed diagnosis of the error. An example of this event from a successful upgrade is shown below.
|
||||
|
||||
@ -60,8 +64,8 @@ The event will also contain links to log files that can be used to perform a det
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 FAQ for IT professionals](https://technet.microsoft.com/windows/dn798755.aspx)
|
||||
<br>[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
|
||||
<br>[Windows 10 Specifications](https://www.microsoft.com/en-us/windows/Windows-10-specifications)
|
||||
<br>[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
<br>[Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/kb/947821)
|
||||
[Windows 10 FAQ for IT professionals](https://technet.microsoft.com/windows/dn798755.aspx)
|
||||
[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
|
||||
[Windows 10 Specifications](https://www.microsoft.com/en-us/windows/Windows-10-specifications)
|
||||
[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
[Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/kb/947821)
|
||||
|
||||
@ -28,6 +28,9 @@ Windows Easy Transfer is a software wizard for transferring files and settings
|
||||
|
||||
With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. However, you cannot use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store.
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Easy Transfer [is not available in Windows 10](https://support.microsoft.com/help/4026265/windows-windows-easy-transfer-is-not-available-in-windows-10).
|
||||
|
||||
### Migrate with the User State Migration Tool
|
||||
You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. You can use USMT for both *side-by-side* migrations, where one piece of hardware is being replaced, or *wipe-and-load* (or *refresh*) migrations, when only the operating system is being upgraded.
|
||||
|
||||
|
||||
@ -455,9 +455,9 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
<p>USMT migrates all user accounts on the computer, unless you specifically exclude an account with either the /<strong>ue</strong> or /<strong>uel</strong> options. For this reason, you do not need to specify this option on the command line. However, if you choose to specify the /<strong>all</strong> option, you cannot also use the /<strong>ui</strong>, /<strong>ue</strong> or /<strong>uel</strong> options.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/<strong>ui</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<td align="left"><p>/<strong>ui</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<p>or</p>
|
||||
<p>/<strong>ui</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<p>/<strong>ui</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<td align="left"><p><strong>(User include)</strong></p>
|
||||
<p>Migrates the specified users. By default, all users are included in the migration. Therefore, this option is helpful only when used with the /<strong>ue</strong> or /<strong>uel</strong> options. You can specify multiple /<strong>ui</strong> options, but you cannot use the /<strong>ui</strong> option with the /<strong>all</strong> option. <em>DomainName</em> and <em>UserName</em> can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you will need to surround it with quotation marks.</p>
|
||||
<div class="alert">
|
||||
@ -469,10 +469,10 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
</div>
|
||||
<p>For example:</p>
|
||||
<ul>
|
||||
<li><p>To include only User2 from the Fabrikam domain, type:</p>
|
||||
<p><code>/ue:*\* /ui:fabrikam\user2</code></p></li>
|
||||
<li><p>To migrate all users from the Fabrikam domain, and only the user accounts from other domains that have been active or otherwise modified in the last 30 days, type:</p>
|
||||
<p><code>/uel:30 /ui:fabrikam\*</code></p>
|
||||
<p>To include only User2 from the Fabrikam domain, type:</p>
|
||||
<p><code>/ue:*\* /ui:fabrikam\user2</code></p>
|
||||
<p>To migrate all users from the Fabrikam domain, and only the user accounts from other domains that have been active or otherwise modified in the last 30 days, type:</p>
|
||||
<p><code>/uel:30 /ui:fabrikam\*</code></p>
|
||||
<p>In this example, a user account from the Contoso domain that was last modified 2 months ago will not be migrated.</p></li>
|
||||
</ul>
|
||||
<p>For more examples, see the descriptions of the /<strong>ue</strong> and /<strong>ui</strong> options in this table.</p></td>
|
||||
@ -500,17 +500,17 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
<li><p><strong>/uel:2002/1/15</strong> migrates users who have logged on or been modified January 15, 2002 or afterwards.</p></li>
|
||||
</ul>
|
||||
<p>For example:</p>
|
||||
<p><code>scanstate /i:migapp.xml /i:migdocs.xml \\server\share\migration\mystore /uel:0</code></p></td>
|
||||
<p><code>scanstate /i:migapp.xml /i:migdocs.xml \\server\share\migration\mystore /uel:0</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/<strong>ue</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<td align="left"><p>/<strong>ue</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<p>-or-</p>
|
||||
<p></p>
|
||||
<p>/<strong>ue</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<p>/<strong>ue</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<td align="left"><p><strong>(User exclude)</strong></p>
|
||||
<p>Excludes the specified users from the migration. You can specify multiple /<strong>ue</strong> options. You cannot use this option with the /<strong>all</strong> option. <em><DomainName></em> and <em><UserName></em> can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you need to surround it with quotation marks.</p>
|
||||
<p>For example:</p>
|
||||
<p><code>scanstate /i:migdocs.xml /i:migapp.xml \\server\share\migration\mystore /ue:contoso\user1</code></p></td>
|
||||
<p><code>scanstate /i:migdocs.xml /i:migapp.xml \\server\share\migration\mystore /ue:contoso\user1</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -548,15 +548,15 @@ The following examples apply to both the /**ui** and /**ue** options. You can re
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Exclude all domain users.</p></td>
|
||||
<td align="left"><p><code>/ue:Domain\*</code></p></td>
|
||||
<td align="left"><p><code>/ue:Domain\*</code></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Exclude all local users.</p></td>
|
||||
<td align="left"><p><code>/ue:%computername%\*</code></p></td>
|
||||
<td align="left"><p><code>/ue:%computername%\*</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Exclude users in all domains named User1, User2, and so on.</p></td>
|
||||
<td align="left"><p><code>/ue:*\user*</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\user*</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -586,23 +586,23 @@ The /**uel** option takes precedence over the /**ue** option. If a user has logg
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Include only User2 from the Fabrikam domain and exclude all other users.</p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:fabrikam\user2</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:fabrikam\user2</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Include only the local user named User1 and exclude all other users.</p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:user1</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:user1</code></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Include only the domain users from Contoso, except Contoso\User1.</p></td>
|
||||
<td align="left"><p>This behavior cannot be completed using a single command. Instead, to migrate this set of users, you will need to specify the following:</p>
|
||||
<ul>
|
||||
<li><p>On the <strong>ScanState</strong> command line, type: <code>/ue:*\* /ui:contoso\*</code></p></li>
|
||||
<li><p>On the <strong>ScanState</strong> command line, type: <code>/ue:*\* /ui:contoso\*</code></p></li>
|
||||
<li><p>On the <strong>LoadState</strong> command line, type: <code>/ue:contoso\user1</code></p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Include only local (non-domain) users.</p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:%computername%\*</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:%computername%\*</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -20,6 +20,7 @@ ms.topic: article
|
||||
- Windows 8
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2016
|
||||
|
||||
**Looking for retail activation?**
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
@ -133,11 +133,9 @@ If you have already established a KMS infrastructure in your organization for an
|
||||
1. Download and install the correct update for your current KMS host operating system. Restart the computer as directed.
|
||||
2. Request a new KMS host key from the Volume Licensing Service Center.
|
||||
3. Install the new KMS host key on your KMS host.
|
||||
4. Activate the new KMS host key by running the slmrg.vbs script.
|
||||
4. Activate the new KMS host key by running the slmgr.vbs script.
|
||||
|
||||
For detailed instructions, see [Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows](https://go.microsoft.com/fwlink/p/?LinkId=618265) and [Update that enables Windows 7 and Windows Server 2008 R2 KMS hosts to activate Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=626590).
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -20,6 +20,8 @@ ms.topic: article
|
||||
The Windows Autopilot Enrollment Status page displaying the status of the complete device configuration process. Incorporating feedback from customers, this provides information to the user to show that the device is being set up and can be configured to prevent access to the desktop until the configuration is complete.
|
||||
|
||||
|
||||
|
||||
From Windows 10 version 1803 onwards, you can opt out of the account setup phase. If it is skipped, settings will be applied for users when they access their desktop for the first time.
|
||||
|
||||
## Available settings
|
||||
|
||||
|
||||
@ -29,7 +29,8 @@ To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
|
||||
- **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile.
|
||||
- If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group.
|
||||
- The device must be running Windows 10, version 1809 or later.
|
||||
- The device must be connected to the Internet and have access to an Active Directory domain controller.
|
||||
- The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user).
|
||||
- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements-network.md).
|
||||
- The Intune Connector for Active Directory must be installed.
|
||||
- Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf.
|
||||
- If using Proxy, WPAD Proxy settings option must be enabled and configured.
|
||||
|
||||
@ -19,12 +19,14 @@ ms.topic: article
|
||||
|
||||
**Applies to: Windows 10, version 1709 and above
|
||||
|
||||
The Intune Service Administrator role is required to perform this task. Learn more about how to [Assign Azure Active Directory roles](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
|
||||
|
||||
IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state.
|
||||
|
||||
To enable local Autopilot Reset in Windows 10:
|
||||
|
||||
1. [Enable the policy for the feature](#enable-autopilot-reset)
|
||||
2. [Trigger a reset for each device](#trigger-autopilot-reset)
|
||||
1. [Enable the policy for the feature](#enable-local-windows-autopilot-reset)
|
||||
2. [Trigger a reset for each device](#trigger-local-windows-autopilot-reset)
|
||||
|
||||
## Enable local Windows Autopilot Reset
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ The Windows Autopilot Reset process automatically retains information from the e
|
||||
- Provisioning packages previously applied to the device, as well as a provisioning package present on a USB drive when the reset process is initiated.
|
||||
- Azure Active Directory device membership and MDM enrollment information.
|
||||
|
||||
Windows Autopilot Reset will block the user from accessing the desktop until this information is restored, including re-applying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset will also block until an MDM sync is completed. This requires configuring the device to use the [enrollment status page](enrollment-status.md).
|
||||
Windows Autopilot Reset will block the user from accessing the desktop until this information is restored, including re-applying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset will also block until an MDM sync is completed.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>To reestablish Wi-Fi connectivity after reset, make sure the **Connect automatically** box is checked for the device's wireless network connection.
|
||||
|
||||
Reference in New Issue
Block a user