mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into DO19H1
This commit is contained in:
jaimeo
@ -4,7 +4,7 @@
|
||||
## [What's new in Windows 10 deployment](deploy-whats-new.md)
|
||||
## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
## [Windows Autopilot](windows-autopilot/windows-autopilot.md)
|
||||
## [Windows 10 Subscription Activation](windows-10-enterprise-subscription-activation.md)
|
||||
## [Windows 10 Subscription Activation](windows-10-subscription-activation.md)
|
||||
### [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md)
|
||||
### [Configure VDA for Subscription Activation](vda-subscription-activation.md)
|
||||
### [Deploy Windows 10 Enterprise licenses](deploy-enterprise-licenses.md)
|
||||
|
||||
@ -7,17 +7,13 @@ ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
ms.date: 05/25/2018
|
||||
author: greg-lindsay
|
||||
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).
|
||||
This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-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.
|
||||
|
||||
@ -25,7 +25,7 @@ This topic provides an overview of new solutions and online content related to d
|
||||
|
||||
## Recent additions to this page
|
||||
|
||||
[SetupDiag](#setupdiag) 1.4 is released.<br>
|
||||
[SetupDiag](#setupdiag) 1.4.1 is released.<br>
|
||||
[MDT](#microsoft-deployment-toolkit-mdt) 8456 is released.<br>
|
||||
New [Windows Autopilot](#windows-autopilot) content is available.<br>
|
||||
The [Microsoft 365](#microsoft-365) section was added.
|
||||
@ -51,7 +51,7 @@ Microsoft is [extending support](https://www.microsoft.com/microsoft-365/blog/20
|
||||
|
||||
## Windows 10 Enterprise upgrade
|
||||
|
||||
Windows 10 version 1703 includes a Windows 10 Enterprise E3 and E5 benefit to Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA). These customers can now subscribe users to Windows 10 Enterprise E3 or E5 and activate their subscriptions on up to five devices. Virtual machines can also be activated. For more information, see [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md).
|
||||
Windows 10 version 1703 includes a Windows 10 Enterprise E3 and E5 benefit to Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA). These customers can now subscribe users to Windows 10 Enterprise E3 or E5 and activate their subscriptions on up to five devices. Virtual machines can also be activated. For more information, see [Windows 10 Enterprise Subscription Activation](windows-10-subscription-activation.md).
|
||||
|
||||
Windows 10 Enterprise E3 launched in the Cloud Solution Provider (CSP) channel on September 1, 2016. Previously, only organizations with a Microsoft Volume Licensing Agreement could deploy Windows 10 Enterprise to their users. With Windows 10 Enterprise E3 in CSP, small and medium-sized organizations can more easily take advantage of Windows 10 Enterprise features.
|
||||
|
||||
@ -72,7 +72,7 @@ Recent Autopilot content includes new instructions for CSPs and OEMs on how to [
|
||||
|
||||
[SetupDiag](upgrade/setupdiag.md) is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
|
||||
|
||||
SetupDiag version 1.4 was released on 12/18/2018.
|
||||
SetupDiag version 1.4.1 was released on 5/17/2019.
|
||||
|
||||
### Upgrade Readiness
|
||||
|
||||
|
||||
BIN
windows/deployment/images/after.png
Normal file
BIN
windows/deployment/images/after.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 58 KiB |
BIN
windows/deployment/images/before.png
Normal file
BIN
windows/deployment/images/before.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
BIN
windows/deployment/images/ent.png
Normal file
BIN
windows/deployment/images/ent.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
@ -5,10 +5,11 @@
|
||||
## [Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
|
||||
## Features removed or planned for replacement
|
||||
### [Windows 10, version 1903](windows-10-1903-removed-features.md)
|
||||
### [Windows 10, version 1809](windows-10-1809-removed-features.md)
|
||||
### [Windows 10, version 1803](windows-10-1803-removed-features.md)
|
||||
### [Windows 10, version 1709](windows-10-fall-creators-deprecation.md)
|
||||
### [Windows 10, version 1703](windows-10-creators-update-deprecation.md)
|
||||
### [Windows 10, version 1709](windows-10-1709-removed-features.md)
|
||||
### [Windows 10, version 1703](windows-10-1703-removed-features.md)
|
||||
|
||||
## [Application Compatibility Toolkit (ACT) Technical Reference](act-technical-reference.md)
|
||||
### [SUA User's Guide](sua-users-guide.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows 10 Creators Update Deprecated Features
|
||||
description: Learn about features that were removed in Windows 10 Creators Update (version 1703)
|
||||
title: Windows 10, version 1703 removed features
|
||||
description: Learn about features that were removed in Windows 10, version 1703
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
@ -9,15 +9,15 @@ author: lizap
|
||||
ms.date: 10/09/2017
|
||||
ms.topic: article
|
||||
---
|
||||
# Features that are removed or deprecated in Windows 10 Creators Update
|
||||
# Features that are removed or deprecated in Windows 10, version 1703
|
||||
|
||||
> Applies to: Windows 10
|
||||
> Applies to: Windows 10, version 1703
|
||||
|
||||
The following features and functionalities in the Windows 10 Creators Update edition (Windows 10, version 1703) have either been removed from the product in the current release (*Removed*) or are not in active development and are planned for potential removal in subsequent releases (*Deprecated*).
|
||||
The following features and functionalities in the Windows 10 Creators Update edition (Windows 10, version 1703) have either been removed from the product in the current release (*Removed*) or are not in active development and are planned for potential removal in subsequent releases.
|
||||
|
||||
This list is intended for IT professionals who are updating operating systems in a commercial environment. The plan and list are subject to change and may not include every deprecated feature or functionality. For more details about a listed feature or functionality and its replacement, see the documentation for that feature.
|
||||
|
||||
| Feature | Removed | Deprecated |
|
||||
| Feature | Removed | Not actively developed |
|
||||
|------------|---------|------------|
|
||||
|Apndatabase.xml is being replaced by the COSA database. Therefore, some constructs will no longer function. This includes Hardware ID, incoming SMS messaging rules in mobile apps, a list of privileged apps in mobile apps, autoconnect order, APN parser, and CDMAProvider ID. | | X |
|
||||
|Apps Corner| | X |
|
||||
@ -1,25 +1,24 @@
|
||||
---
|
||||
title: Windows 10 Fall Creators Update Deprecated Features
|
||||
description: Learn about features that will be removed in Windows 10 Fall Creators Update (version 1709)
|
||||
title: Windows 10, version 1709 removed features
|
||||
description: Learn about features that will be removed in Windows 10, version 1709
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: lizap
|
||||
ms.date: 10/30/2018
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
# Features that are removed or deprecated in Windows 10 Fall Creators Update
|
||||
# Features that are removed or deprecated in Windows 10, version 1709
|
||||
|
||||
> Applies to: Windows 10
|
||||
> Applies to: Windows 10, version 1709
|
||||
|
||||
The following features and functionalities in the Windows 10 Fall Creators Update (Windows 10, version 1709) are either removed from the product in the current release (*Removed*) or are not in active development and might be removed in future releases (*Deprecated*).
|
||||
The following features and functionalities in the Windows 10, version 1709 are either removed from the product in the current release (*Removed*) or are not in active development and might be removed in future releases.
|
||||
|
||||
This list is intended to help customers consider these removals and deprecations for their own planning. The list is subject to change and may not include every deprecated feature or functionality.
|
||||
|
||||
For more information about a listed feature or functionality and its replacement, see the documentation for that feature. You can also follow the provided links in this table to see additional resources.
|
||||
|
||||
| Feature | Removed | Deprecated |
|
||||
| Feature | Removed | Not actively developed |
|
||||
|----------|---------|------------|
|
||||
|**3D Builder app** <br> No longer installed by default. Consider using Print 3D and Paint 3D in its place. However, 3D Builder is still available for download from the Windows Store. | X | |
|
||||
|**Apndatabase.xml** <br> For more information about the replacement database, see the following Hardware Dev Center articles: <br> [MO Process to update COSA](/windows-hardware/drivers/mobilebroadband/planning-your-apn-database-submission) <br> [COSA FAQ](/windows-hardware/drivers/mobilebroadband/cosa---faq) | X | |
|
||||
@ -33,7 +33,7 @@ We've removed the following features and functionalities from the installed prod
|
||||
|Language control in the Control Panel| Use the Settings app to change your language settings.|
|
||||
|HomeGroup|We are removing [HomeGroup](https://support.microsoft.com/help/17145) but not your ability to share printers, files, and folders.<br><br>When you update to Windows 10, version 1803, you won't see HomeGroup in File Explorer, the Control Panel, or Troubleshoot (**Settings > Update & Security > Troubleshoot**). Any printers, files, and folders that you shared using HomeGroup **will continue to be shared**.<br><br>Instead of using HomeGroup, you can now share printers, files and folders by using features that are built into Windows 10: <br>- [Share your network printer](https://www.bing.com/search?q=share+printer+windows+10) <br>- [Share files in File Explorer](https://support.microsoft.com/help/4027674/windows-10-share-files-in-file-explorer) |
|
||||
|**Connect to suggested open hotspots** option in Wi-Fi settings |We previously [disabled the **Connect to suggested open hotspots** option](https://privacy.microsoft.com/windows-10-open-wi-fi-hotspots) and are now removing it from the Wi-Fi settings page. You can manually connect to free wireless hotspots with **Network & Internet** settings, from the taskbar or Control Panel, or by using Wi-Fi Settings (for mobile devices).|
|
||||
|XPS Viewer|We're changing the way you get XPS Viewer. In Windows 10, version 1709 and earlier versions, the app is included in the installation image. <br><br>However, if you install Windows 10, version 1803, you may need to [install XPS Viewer from **Apps and Features** in the Settings app](https://docs.microsoft.com/windows/application-management/add-apps-and-features) or through [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities). If you had XPS Viewer in Windows 10, version 1709, but manually removed it before updating, you'll need to manually reinstall it.|
|
||||
|XPS Viewer|We're changing the way you get XPS Viewer. In Windows 10, version 1709 and earlier versions, the app is included in the installation image. If you have XPS Viewer and you update to Windows 10, version 1803, there's no action required. You'll still have XPS Viewer. <br><br>However, if you install Windows 10, version 1803, on a new device (or as a clean installation), you may need to [install XPS Viewer from **Apps and Features** in the Settings app](https://docs.microsoft.com/windows/application-management/add-apps-and-features) or through [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities). If you had XPS Viewer in Windows 10, version 1709, but manually removed it before updating, you'll need to manually reinstall it.|
|
||||
|
||||
|
||||
## Features we’re no longer developing
|
||||
|
||||
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Windows 10, version 1903 - Features that have been removed
|
||||
description: Learn about features that will be removed or deprecated in Windows 10, version 1903, or a future release
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# Features removed or planned for replacement starting with Windows 10, version 1903
|
||||
|
||||
> Applies to: Windows 10, version 1903
|
||||
|
||||
Each version of Windows 10 adds new features and functionality; occasionally we also remove features and functionality, often because we've added a better option. Below are the details about the features and functionalities that we removed in Windows 10, version 1903. **The list below is subject to change and might not include every affected feature or functionality.**
|
||||
|
||||
**Note**: Join the [Windows Insider program](https://insider.windows.com) to get early access to new Windows 10 builds and test these changes yourself.
|
||||
|
||||
## Features we removed or will remove soon
|
||||
|
||||
The following features and functionalities are removed from the installed product image for Windows 10, version 1903, or are planned for removal in an upcoming release. Applications or code that depend on these features won't function in this release unless you use another method.
|
||||
|
||||
|Feature |Details|
|
||||
|-----------|--------------------|---------
|
||||
|XDDM-based remote display driver|Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For more information on implementing remote indirect display driver ISVs can reach out to [rdsdev@microsoft.com](mailto:rdsdev@microsoft.com).
|
||||
| Desktop messaging app doesn't offer messages sync| The messaging app on Desktop has a sync feature that can be used to sync SMS text messages received from Windows Mobile and keep a copy of them on the Desktop. The sync feature has been removed from all devices. Due to this change, you will only be able to access messages from the device that received the message. |
|
||||
|
||||
## Features we’re no longer developing
|
||||
|
||||
We're no longer actively developing these features and may remove them from a future update. Some features have been replaced with other features or functionality, while others are now available from different sources.
|
||||
|
||||
If you have feedback about the proposed replacement of any of these features, you can use the [Feedback Hub app](https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app).
|
||||
|
||||
|Feature |Details|
|
||||
|-----------|---------------------|
|
||||
| Taskbar settings roaming| Roaming of taskbar settings is no longer being developed and we plan to disable this capability in a future release|
|
||||
|Wi-Fi WEP and TKIP|In this release a warning message will appear when connecting to Wi-Fi networks secured with WEP or TKIP, which are not as secure as those using WPA2 or WPA3. In a future release, any connection to a Wi-Fi network using these old ciphers will be disallowed. Wi-Fi routers should be updated to use AES ciphers, available with WPA2 or WPA3. |
|
||||
|Windows To Go|Windows To Go is no longer being developed. <br><br>The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.|
|
||||
|Print 3D app|Going forward, 3D Builder is the recommended 3D printing app. To 3D print objects on new Windows devices, customers must first install 3D Builder from the Store.|
|
||||
|
||||
@ -32,3 +32,16 @@ Refer to the following list for what each state means:
|
||||
* Devices that have failed the given feature update installation are counted as **Update failed**.
|
||||
* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
|
||||
|
||||
## Compatibility holds
|
||||
|
||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
|
||||
|
||||
To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status).
|
||||
|
||||
### Opting out of compatibility hold
|
||||
|
||||
Microsoft will release a device from a compatibility hold when it has determined it can safely and smoothly install a feature update, but you are ultimately in control of your devices and can opt out if desired. To opt out, set the registry key **HKLM\Software\Microsoft\Windows NT\CurrentVersion\502505fe-762c-4e80-911e-0c3fa4c63fb0** to a name of **DataRequireGatedScanForFeatureUpdates** and a value of **0**.
|
||||
|
||||
|
||||
Setting this registry key to **0** will force the device to opt out from *all* compatibility holds. Any other value, or deleting the key, will resume compatibility protection on the device.
|
||||
|
||||
|
||||
@ -23,6 +23,8 @@ The first blade is the **Build Summary** blade. This blade summarizes the most i
|
||||
|
||||
The second blade is the **Deferral Configurations** blade, breaking down Windows Update for Business deferral settings (if any).
|
||||
|
||||
## Deployment status
|
||||
|
||||
The third blade is the **Deployment Status** blade. This defines how many days it has been since the queried version has been released, and breaks down the various states in the update funnel each device has reported to be in. The possible states are as follows:
|
||||
|
||||
| State | Description |
|
||||
@ -35,6 +37,9 @@ The third blade is the **Deployment Status** blade. This defines how many days i
|
||||
| Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. |
|
||||
| Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. |
|
||||
| Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. |
|
||||
| Failed | A device is unable to install an update. This failure could be linked to a serious error in the update installation process or, in some cases, a [compatibility hold](update-compliance-feature-update-status.md#compatibility-holds). |
|
||||
|
||||
## Detailed deployment status
|
||||
|
||||
The final blade is the **Detailed Deployment Status** blade. This blade breaks down the detailed stage of deployment a device is in, beyond the generalized terms defined in Deployment Status. The following are the possible stages a device can report:
|
||||
|
||||
@ -44,6 +49,7 @@ The final blade is the **Detailed Deployment Status** blade. This blade breaks d
|
||||
| Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. |
|
||||
| Update offered | The device has been offered the update, but has not begun downloading it. |
|
||||
| Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. |
|
||||
| Compatibility hold | The device has been placed under a *compatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared. For more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) |
|
||||
| Download Started | The update has begun downloading on the device. |
|
||||
| Download Succeeded | The update has successfully completed downloading. |
|
||||
| Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. |
|
||||
|
||||
@ -7,7 +7,6 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.date: 12/18/2018
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
@ -25,7 +24,7 @@ ms.topic: article
|
||||
|
||||
## About SetupDiag
|
||||
|
||||
<I>Current version of SetupDiag: 1.4.0.0</I>
|
||||
<I>Current version of SetupDiag: 1.4.1.0</I>
|
||||
|
||||
SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
|
||||
|
||||
@ -64,8 +63,9 @@ The [Release notes](#release-notes) section at the bottom of this topic has info
|
||||
| /Output:\<path to results file\> | <ul><li>This optional parameter enables you to specify the output file for results. This is where you will find what SetupDiag was able to determine. Only text format output is supported. UNC paths will work, provided the context under which SetupDiag runs has access to the UNC path. If the path has a space in it, you must enclose the entire path in double quotes (see the example section below). <li>Default: If not specified, SetupDiag will create the file **SetupDiagResults.log** in the same directory where SetupDiag.exe is run.</ul> |
|
||||
| /LogsPath:\<Path to logs\> | <ul><li>This optional parameter tells SetupDiag.exe where to find the log files for an offline analysis. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories.</ul> |
|
||||
| /ZipLogs:\<True \| False\> | <ul><li>This optional parameter tells SetupDiag.exe to create a zip file containing the results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.<li>Default: If not specified, a value of 'true' is used.</ul> |
|
||||
| /Verbose | <ul><li>This optional parameter will output much more data to a log file. By default, SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce an additional log file with debugging details. These details can be useful when reporting a problem with SetupDiag.</ul> |
|
||||
| /Format:\<xml \| json\> | <ul><li>This optional parameter can be used to output log files in xml or JSON format. If this parameter is not specified, text format is used by default.</ul> |
|
||||
| /Scenario:\[Recovery\] | This optional parameter instructs SetupDiag.exe to look for and process reset and recovery logs and ignore setup/upgrade logs.|
|
||||
| /Verbose | <ul><li>This optional parameter will output much more data to a log file. By default, SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce an additional log file with debugging details. These details can be useful when reporting a problem with SetupDiag.</ul> |
|
||||
| /NoTel | <ul><li>This optional parameter tells SetupDiag.exe not to send diagnostic telemetry to Microsoft.</ul> |
|
||||
|
||||
Note: The **/Mode** parameter is deprecated in version 1.4.0.0 of SetupDiag.
|
||||
@ -97,6 +97,19 @@ The following example specifies that SetupDiag is to run in offline mode, and to
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:D:\Temp\Logs\LogSet1
|
||||
```
|
||||
|
||||
The following example sets recovery scenario in offline mode. In the example, SetupDiag will search for reset/recovery logs in the specified LogsPath location and output the resuts to the directory specified by the /Output parameter.
|
||||
|
||||
```
|
||||
SetupDiag.exe /Output:C:\SetupDiag\RecoveryResults.log /LogsPath:D:\Temp\Cabs\PBR_Log /Scenario:Recovery
|
||||
```
|
||||
|
||||
The following example sets recovery scenario in online mode. In the example, SetupDiag will search for reset/recovery logs on the current system and output results in XML format.
|
||||
|
||||
```
|
||||
SetupDiag.exe /Scenario:Recovery /Format:xml
|
||||
```
|
||||
|
||||
|
||||
## Log files
|
||||
|
||||
[Windows Setup Log Files and Event Logs](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-log-files-and-event-logs) has information about where logs are created during Windows Setup. For offline processing, you should run SetupDiag against the contents of the entire folder. For example, depending on when the upgrade failed, copy one of the following folders to your offline location:
|
||||
@ -141,7 +154,7 @@ The output also provides an error code 0xC1900208 - 0x4000C which corresponds to
|
||||
```
|
||||
C:\SetupDiag>SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:C:\Temp\BobMacNeill
|
||||
|
||||
SetupDiag v1.4.0.0
|
||||
SetupDiag v1.4.1.0
|
||||
Copyright (c) Microsoft Corporation. All rights reserved.
|
||||
|
||||
Searching for setup logs, this can take a minute or more depending on the number and size of the logs...please wait.
|
||||
@ -397,6 +410,9 @@ Each rule name and its associated unique rule identifier are listed with a descr
|
||||
|
||||
## Release notes
|
||||
|
||||
05/17/2019 - SetupDiag v1.4.1.0 is released with 53 rules, as a standalone tool available from the Download Center.
|
||||
- This release dds the ability to find and diagnose reset and recovery failures (Push Button Reset).
|
||||
|
||||
12/18/2018 - SetupDiag v1.4.0.0 is released with 53 rules, as a standalone tool available from the Download Center.
|
||||
- This release includes major improvements in rule processing performance: ~3x faster rule processing performance!
|
||||
- The FindDownlevelFailure rule is up to 10x faster.
|
||||
|
||||
@ -7,7 +7,6 @@ ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
ms.date: 05/17/2018
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.collection: M365-modern-desktop
|
||||
@ -15,7 +14,7 @@ ms.collection: M365-modern-desktop
|
||||
|
||||
# Configure VDA for Windows 10 Subscription Activation
|
||||
|
||||
This document describes how to configure virtual machines (VMs) to enable [Windows 10 Subscription Activation](windows-10-enterprise-subscription-activation.md) in a Windows Virtual Desktop Access (VDA) scenario. Windows VDA is a device or user-based licensing mechanism for managing access to virtual desktops.
|
||||
This document describes how to configure virtual machines (VMs) to enable [Windows 10 Subscription Activation](windows-10-subscription-activation.md) in a Windows Virtual Desktop Access (VDA) scenario. Windows VDA is a device or user-based licensing mechanism for managing access to virtual desktops.
|
||||
|
||||
Deployment instructions are provided for the following scenarios:
|
||||
1. [Active Directory-joined VMs](#active-directory-joined-vms)
|
||||
@ -40,7 +39,7 @@ Deployment instructions are provided for the following scenarios:
|
||||
### Scenario 2
|
||||
- The Hyper-V host and the VM are both running Windows 10, version 1803 or later.
|
||||
|
||||
[Inherited Activation](https://docs.microsoft.com/windows/deployment/windows-10-enterprise-subscription-activation#inherited-activation) is enabled. All VMs created by a user with a Windows 10 E3 or E5 license are automatically activated independent of whether a user signs in iwth a local account or using an Azure Active Directory account.
|
||||
[Inherited Activation](https://docs.microsoft.com/windows/deployment/windows-10-subscription-activation#inherited-activation) is enabled. All VMs created by a user with a Windows 10 E3 or E5 license are automatically activated independent of whether a user signs in iwth a local account or using an Azure Active Directory account.
|
||||
|
||||
### Scenario 3
|
||||
- The VM is running Windows 10, version 1703 or 1709, or the hoster is not an authorized [QMTH](https://www.microsoft.com/en-us/CloudandHosting/licensing_sca.aspx) partner.
|
||||
@ -88,13 +87,13 @@ For examples of activation issues, see [Troubleshoot the user experience](https:
|
||||
## Azure Active Directory-joined VMs
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Azure Active Directory (Azure AD) provisioning packages have a 30 day limit on bulk token usage. You will need to update the provisioning package and re-inject it into the image after 30 days. Existing virtual machines that are Azure AD-joined and deployed will not need to be recreated.
|
||||
>Azure Active Directory (Azure AD) provisioning packages have a 180 day limit on bulk token usage. You will need to update the provisioning package and re-inject it into the image after 180 days. Existing virtual machines that are Azure AD-joined and deployed will not need to be recreated.
|
||||
|
||||
For Azure AD-joined VMs, follow the same instructions (above) as for [Active Directory-joined VMs](#active-directory-joined-vms) with the following exceptions:
|
||||
- In step 9, during setup with Windows Configuration Designer, under **Name**, type a name for the project that indicates it is not for Active Directory joined VMs, such as **Desktop Bulk Enrollment Token Pro GVLK**.
|
||||
- In step 11, during setup with Windows Configuration Designer, on the Account Management page, instead of enrolling in Active Directory, choose **Enroll in Azure AD**, click **Get Bulk Token**, sign in and add the bulk token using your organization's credentials.
|
||||
- In step 15, sub-step 2, when entering the PackagePath, use the project name you entered in step 9 (ex: **Desktop Bulk Enrollment Token Pro GVLK.ppkg**)
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described below in [Create custom RDP settings for Azure](#create-custom-rpd-settings-for-azure).
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described below in [Create custom RDP settings for Azure](#create-custom-rdp-settings-for-azure).
|
||||
|
||||
## Azure Gallery VMs
|
||||
|
||||
@ -120,7 +119,7 @@ For Azure AD-joined VMs, follow the same instructions (above) as for [Active Dir
|
||||
13. On the Finish page, click **Create**.
|
||||
14. Copy the .ppkg file to the remote Virtual machine. Double click to initiate the provisioning package install. This will reboot the system.
|
||||
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described [below](#create-custom-rpd-settings-for-azure).
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described [below](#create-custom-rdp-settings-for-azure).
|
||||
|
||||
## Create custom RDP settings for Azure
|
||||
|
||||
@ -141,7 +140,7 @@ To create custom RDP settings for Azure:
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 Subscription Activation](windows-10-enterprise-subscription-activation.md)
|
||||
[Windows 10 Subscription Activation](windows-10-subscription-activation.md)
|
||||
<BR>[Recommended settings for VDI desktops](https://docs.microsoft.com/windows-server/remote/remote-desktop-services/rds-vdi-recommendations)
|
||||
<BR>[Licensing the Windows Desktop for VDI Environments](https://download.microsoft.com/download/1/1/4/114A45DD-A1F7-4910-81FD-6CAF401077D0/Microsoft%20VDI%20and%20VDA%20FAQ%20v3%200.pdf)
|
||||
|
||||
|
||||
@ -249,7 +249,7 @@ The Managed User Experience feature is a set of Windows 10 Enterprise edition f
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md)
|
||||
[Windows 10 Enterprise Subscription Activation](windows-10-subscription-activation.md)
|
||||
<BR>[Connect domain-joined devices to Azure AD for Windows 10 experiences](https://azure.microsoft.com/documentation/articles/active-directory-azureadjoin-devices-group-policy/)
|
||||
<BR>[Compare Windows 10 editions](https://www.microsoft.com/WindowsForBusiness/Compare)
|
||||
<BR>[Windows for business](https://www.microsoft.com/windowsforbusiness/default.aspx)
|
||||
|
||||
@ -7,7 +7,6 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
keywords: deployment, automate, tools, configure, mdt, sccm
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/16/2017
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
@ -57,7 +56,7 @@ Topics and procedures in this guide are summarized in the following table. An es
|
||||
<tr><td>[Convert PC to VM](#convert-pc-to-vm)<td>Convert a physical computer on your network to a VM hosted in Hyper-V.<td>30 minutes
|
||||
<tr><td>[Resize VHD](#resize-vhd)<td>Increase the storage capacity for one of the Windows Server VMs.<td>5 minutes
|
||||
<tr><td>[Configure Hyper-V](#configure-hyper-v)<td>Create virtual switches, determine available RAM for virtual machines, and add virtual machines.<td>15 minutes
|
||||
<tr><td>[Configure service and user accounts](#configure-service-and-user-accounts)<td>Start virtual machines and configure all services and settings.<td>60 minutes
|
||||
<tr><td>[Configure service and user accounts](#configure-vms)<td>Start virtual machines and configure all services and settings.<td>60 minutes
|
||||
<tr><td>[Configure VMs](#configure-vms)<td>Start virtual machines and configure all services and settings.<td>60 minutes
|
||||
<tr><td>[Appendix A: Verify the configuration](#appendix-a-verify-the-configuration)<td>Verify and troubleshoot network connectivity and services in the PoC environment.<td>30 minutes
|
||||
<tr><td>[Appendix B: Terminology in this guide](#appendix-b-terminology-used-in-this-guide)<td>Terms used in this guide.<td>Informational
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows 10 Subscription Activation
|
||||
description: How to enable Windows 10 Enterprise E3 and E5 subscriptions
|
||||
description: How to dynamically enable Windows 10 Enterprise or Educations subscriptions
|
||||
keywords: upgrade, update, task sequence, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -16,20 +16,33 @@ ms.topic: article
|
||||
|
||||
# Windows 10 Subscription Activation
|
||||
|
||||
With Windows 10 version 1703 (also known as the Creator’s Update), both Windows 10 Enterprise E3 and Windows 10 Enterprise E5 are available as online services via subscription. Deploying [Windows 10 Enterprise](planning/windows-10-enterprise-faq-itpro.md) in your organization can now be accomplished with no keys and no reboots.
|
||||
Starting with Windows 10, version 1703 Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro to **Windows 10 Enterprise** automatically if they are subscribed to Windows 10 Enterprise E3 or E5.
|
||||
|
||||
If you are running Windows 10 version 1703 or later:
|
||||
With Windows 10, version 1903 the Subscription Activation feature also supports the ability to step-up from Windows 10 Pro Education to the Enterprise grade edition for educational institutions – **Windows 10 Education**.
|
||||
|
||||
The Subscription Activation feature eliminates the need to manually deploy Windows 10 Enterprise or Education images on each target device, then later standing up on-prem key management services such as KMS or MAK based activation, entering GVLKs, and subsequently rebooting client devices.
|
||||
|
||||
## Subscription Activation for Windows 10 Enterprise
|
||||
|
||||
With Windows 10, version 1703 both Windows 10 Enterprise E3 and Windows 10 Enterprise E5 are available as online services via subscription. Deploying [Windows 10 Enterprise](planning/windows-10-enterprise-faq-itpro.md) in your organization can now be accomplished with no keys and no reboots.
|
||||
|
||||
If you are running Windows 10, version 1703 or later:
|
||||
|
||||
- Devices with a current Windows 10 Pro license can be seamlessly upgraded to Windows 10 Enterprise.
|
||||
- Product key-based Windows 10 Enterprise software licenses can be transitioned to Windows 10 Enterprise subscriptions.
|
||||
|
||||
Organizations that have an Enterprise agreement can also benefit from the new service, using traditional Active Directory-joined devices. In this scenario, the Active Directory user that signs in on their device must be synchronized with Azure AD using [Azure AD Connect Sync](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-whatis).
|
||||
|
||||
See the following topics in this article:
|
||||
## Subscription Activation for Windows 10 Education
|
||||
|
||||
Subscription Activation for Education works the same as the Enterprise version, but in order to use Subscription Activation for Education, you must have a device running Windows 10 Pro Education, version 1903 or later and an active subscription plan with a Windows 10 Enterprise license. For more information, see the [requirements](#windows-10-education-requirements) section.
|
||||
|
||||
## In this article
|
||||
|
||||
- [Inherited Activation](#inherited-activation): Description of a new feature available in Windows 10, version 1803 and later.
|
||||
- [The evolution of Windows 10 deployment](#the-evolution-of-deployment): A short history of Windows deployment.
|
||||
- [Requirements](#requirements): Prerequisites to use the Windows 10 Enterprise subscription model.
|
||||
- [Benefits](#benefits): Advantages of Windows 10 Enterprise + subscription-based licensing.
|
||||
- [Requirements](#requirements): Prerequisites to use the Windows 10 Subscription Activation model.
|
||||
- [Benefits](#benefits): Advantages of Windows 10 subscription-based licensing.
|
||||
- [How it works](#how-it-works): A summary of the subscription-based licensing option.
|
||||
- [Virtual Desktop Access (VDA)](#virtual-desktop-access-vda): Enable Windows 10 Subscription Activation for VMs in the cloud.
|
||||
|
||||
@ -39,7 +52,7 @@ For information on how to deploy Windows 10 Enterprise licenses, see [Deploy Win
|
||||
|
||||
Inherited Activation is a new feature available in Windows 10, version 1803 that allows Windows 10 virtual machines to inherit activation state from their Windows 10 host.
|
||||
|
||||
When a user with Windows 10 E3 or E5 license assigned creates a new Windows 10 virtual machine (VM) using a Windows 10 local host, the VM inherits the activation state from a host machine independent of whether user signs on with a local account or using an Azure Active Directory (AAD) account on a VM.
|
||||
When a user with Windows 10 E3/E5 or A3/A5 license assigned creates a new Windows 10 virtual machine (VM) using a Windows 10 local host, the VM inherits the activation state from a host machine independent of whether user signs on with a local account or using an Azure Active Directory (AAD) account on a VM.
|
||||
|
||||
To support Inherited Activation, both the host computer and the VM must be running Windows 10, version 1803 or later.
|
||||
|
||||
@ -53,14 +66,17 @@ The following figure illustrates how deploying Windows 10 has evolved with each
|
||||
|
||||
- **Windows 7** required you to redeploy the operating system using a full wipe-and-load process if you wanted to change from Windows 7 Professional to Windows 10 Enterprise.<br>
|
||||
- **Windows 8.1** added support for a Windows 8.1 Pro to Windows 8.1 Enterprise in-place upgrade (considered a “repair upgrade” because the OS version was the same before and after). This was a lot easier than wipe-and-load, but it was still time-consuming.<br>
|
||||
- **Windows 10 1507** added the ability to install a new product key using a provisioning package or using MDM to change the SKU. This required a reboot, which would install the new OS components, and took several minutes to complete. However, it was a lot quicker than in-place upgrade.<br>
|
||||
- **Windows 10 1607** made a big leap forward. Now you can just change the product key and the SKU instantly changes from Windows 10 Pro to Windows 10 Enterprise. In addition to provisioning packages and MDM, you can just inject a key using SLMGR.VBS (which injects the key into WMI), so it became trivial to do this using a command line.<br>
|
||||
- **Windows 10 1703** made this “step-up” from Windows 10 Pro to Windows 10 Enterprise automatic for those that subscribed to Windows 10 Enterprise E3 or E5 via the CSP program.<br>
|
||||
- **Windows 10 1709** adds support for Windows 10 Subscription Activation, very similar to the CSP support but for large enterprises, enabling the use of Azure AD for assigning licenses to users. When those users sign in on an AD or Azure AD-joined machine, it automatically steps up from Windows 10 Pro to Windows 10 Enterprise.
|
||||
- **Windows 10 1803** updates Windows 10 Subscription Activation to enable pulling activation keys directly from firmware for devices that support firmware-embedded keys. It is no longer necessary to run a script to perform the activation step on Windows 10 Pro prior to activating Enterprise. For virtual machines and hosts running Windows 10, version 1803 [Inherited Activation](#inherited-activation) is also enabled.
|
||||
- **Windows 10, version 1507** added the ability to install a new product key using a provisioning package or using MDM to change the SKU. This required a reboot, which would install the new OS components, and took several minutes to complete. However, it was a lot quicker than in-place upgrade.<br>
|
||||
- **Windows 10, version 1607** made a big leap forward. Now you can just change the product key and the SKU instantly changes from Windows 10 Pro to Windows 10 Enterprise. In addition to provisioning packages and MDM, you can just inject a key using SLMGR.VBS (which injects the key into WMI), so it became trivial to do this using a command line.<br>
|
||||
- **Windows 10, version 1703** made this “step-up” from Windows 10 Pro to Windows 10 Enterprise automatic for those that subscribed to Windows 10 Enterprise E3 or E5 via the CSP program.<br>
|
||||
- **Windows 10, version 1709** adds support for Windows 10 Subscription Activation, very similar to the CSP support but for large enterprises, enabling the use of Azure AD for assigning licenses to users. When those users sign in on an AD or Azure AD-joined machine, it automatically steps up from Windows 10 Pro to Windows 10 Enterprise.<br>
|
||||
- **Windows 10, version 1803** updates Windows 10 Subscription Activation to enable pulling activation keys directly from firmware for devices that support firmware-embedded keys. It is no longer necessary to run a script to perform the activation step on Windows 10 Pro prior to activating Enterprise. For virtual machines and hosts running Windows 10, version 1803 [Inherited Activation](#inherited-activation) is also enabled.<br>
|
||||
- **Windows 10, version 1903** updates Windows 10 Subscription Activation to enable step up from Windows 10 Pro Education to Windows 10 Education for those with a qualifying Windows 10 or Microsoft 365 subscription.
|
||||
|
||||
## Requirements
|
||||
|
||||
### Windows 10 Enterprise requirements
|
||||
|
||||
For Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA), you must have the following:
|
||||
|
||||
- Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded.
|
||||
@ -70,33 +86,62 @@ For Microsoft customers with Enterprise Agreements (EA) or Microsoft Products &
|
||||
>[!NOTE]
|
||||
>An issue has been identified with Hybrid Azure AD joined devices that have enabled [multi-factor authentication](https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-getstarted) (MFA). If a user signs into a device using their Active Directory account and MFA is enabled, the device will not successfully upgrade to their Windows Enterprise subscription. To resolve this issue, the user must either sign in with an Azure Active Directory account, or you must disable MFA for this user during the 30-day polling period and renewal.
|
||||
|
||||
For Microsoft customers that do not have EA or MPSA, you can obtain Windows 10 Enterprise E3 or E5 through a cloud solution provider (CSP). Identity management and device requirements are the same when you use CSP to manage licenses, with the exception that Windows 10 Enterprise E3 is also available through CSP to devices running Windows 10, version 1607. For more information about obtaining Windows 10 Enterprise E3 through your CSP, see [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md).
|
||||
For Microsoft customers that do not have EA or MPSA, you can obtain Windows 10 Enterprise E3/E5 or A3/A5 through a cloud solution provider (CSP). Identity management and device requirements are the same when you use CSP to manage licenses, with the exception that Windows 10 Enterprise E3 is also available through CSP to devices running Windows 10, version 1607. For more information about obtaining Windows 10 Enterprise E3 through your CSP, see [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md).
|
||||
|
||||
If devices are running Windows 7 or Windows 8.1, see [New Windows 10 upgrade benefits for Windows Cloud Subscriptions in CSP](https://blogs.windows.com/business/2017/01/19/new-windows-10-upgrade-benefits-windows-cloud-subscriptions-csp/)
|
||||
|
||||
### Windows 10 Education requirements
|
||||
|
||||
1. Windows 10 Pro Education, version 1903 or later installed on the devices to be upgraded.
|
||||
2. A device with a Windows 10 Pro Education digital license. You can confirm this information in Settings > Update & Security> Activation.
|
||||
3. The Education tenant must have an active subscription to Microsoft 365 with a Windows 10 Enterprise license or a Windows 10 Enterprise or Education subscription.
|
||||
4. Devices must be Azure AD-joined or Hybrid Azure AD joined. Workgroup-joined or Azure AD registered devices are not supported.
|
||||
|
||||
>If Windows 10 Pro is converted to Windows 10 Pro Education [using benefits available in Store for Education](https://docs.microsoft.com/education/windows/change-to-pro-education#change-using-microsoft-store-for-education), then the feature will not work. You will need to re-image the device using a Windows 10 Pro Education edition.
|
||||
|
||||
|
||||
## Benefits
|
||||
|
||||
With Windows 10 Enterprise, businesses can benefit from enterprise-level security and control. Previously, only organizations with a Microsoft Volume Licensing Agreement could deploy Windows 10 Enterprise E3 or E5 to their users. Now, with Windows 10 Enterprise E3 and E5 being available as a true online service, it is available in every channel thus allowing all organizations to take advantage of enterprise grade Windows 10 features. To compare Windows 10 editions and review pricing, see the following:
|
||||
With Windows 10 Enterprise or Windows 10 Education, businesses and institutions can benefit from enterprise-level security and control. Previously, only organizations with a Microsoft Volume Licensing Agreement could deploy Windows 10 Education or Windows 10 Enterprise to their users. Now, with Windows 10 Enterprise E3 or A3 and E5 or A5 being available as a true online service, it is available in select channels thus allowing all organizations to take advantage of enterprise-grade Windows 10 features. To compare Windows 10 editions and review pricing, see the following:
|
||||
|
||||
- [Compare Windows 10 editions](https://www.microsoft.com/en-us/windowsforbusiness/compare)
|
||||
- [Enterprise Mobility + Security Pricing Options](https://www.microsoft.com/en-us/cloud-platform/enterprise-mobility-security-pricing)
|
||||
|
||||
You can benefit by moving to Windows as an online service in the following ways:
|
||||
|
||||
1. Licenses for Windows 10 Enterprise are checked based on Azure Active Directory (Azure AD) credentials, so now businesses have a systematic way to assign licenses to end users and groups in their organization.
|
||||
1. Licenses for Windows 10 Enterprise and Education are checked based on Azure Active Directory (Azure AD) credentials, so now businesses have a systematic way to assign licenses to end users and groups in their organization.
|
||||
2. User logon triggers a silent edition upgrade, with no reboot required
|
||||
3. Support for mobile worker/BYOD activation; transition away from on-prem KMS and MAK keys.
|
||||
4. Compliance support via seat assignment.
|
||||
4. Compliance support via seat assignment.
|
||||
5. Licenses can be updated to different users dynamically, enabling you to optimize your licensing investment against changing needs.
|
||||
|
||||
## How it works
|
||||
|
||||
When a licensed user signs in to a device that meets requirements using the Azure AD credentials associated with a Windows 10 Enterprise E3 or E5 license, the operating system turns from Windows 10 Pro to Windows 10 Enterprise and all the appropriate Windows 10 Enterprise features are unlocked. When a user’s subscription expires or is transferred to another user, the Windows 10 Enterprise device reverts seamlessly to Windows 10 Pro edition, after a grace period of up to 90 days.
|
||||
The device is AAD joined from Settings > Accounts > Access work or school.
|
||||
|
||||
Devices currently running Windows 10 Pro, version 1703 or later can get Windows 10 Enterprise Semi-Annual Channel on up to five devices for each user covered by the license. This benefit does not include Long Term Servicing Channel.
|
||||
The IT administrator assigns Windows 10 Enterprise to a user. See the following figure.
|
||||
|
||||
|
||||
|
||||
When a licensed user signs in to a device that meets requirements using their Azure AD credentials, the operating system steps up from Windows 10 Pro to Windows 10 Enterprise (or Windows 10 Pro Education to Windows 10 Education) and all the appropriate Windows 10 Enterprise/Education features are unlocked. When a user’s subscription expires or is transferred to another user, the device reverts seamlessly to Windows 10 Pro / Windows 10 Pro Education edition, once current subscription validity expires.
|
||||
|
||||
Devices running Windows 10 Pro, version 1703 or Windows 10 Pro Education, version 1903 or later can get Windows 10 Enterprise or Education Semi-Annual Channel on up to five devices for each user covered by the license. This benefit does not include Long Term Servicing Channel.
|
||||
|
||||
The following figures summarize how the Subscription Activation model works:
|
||||
|
||||
Before Windows 10, version 1903:<br>
|
||||
|
||||
|
||||
After Windows 10, version 1903:<br>
|
||||
|
||||
|
||||
Note:
|
||||
1. A Windows 10 Pro Education device will only step up to Windows 10 Education edition when “Windows 10 Enterprise” license is assigned from M365 Admin center (as of May 2019).
|
||||
2. A Windows 10 Pro device will only step up to Windows 10 Enterprise edition when “Windows 10 Enterprise” license is assigned from M365 Admin center (as of May 2019).
|
||||
|
||||
### Scenarios
|
||||
|
||||
**Scenario #1**: You are using Windows 10 1803 or above, and just purchased Windows 10 Enterprise E3 or E5 subscriptions (or have had an E3 or E5 subscription for a while but haven’t yet deployed Windows 10 Enterprise).
|
||||
**Scenario #1**: You are using Windows 10, version 1803 or above, and just purchased Windows 10 Enterprise E3 or E5 subscriptions (or have had an E3 or E5 subscription for a while but haven’t yet deployed Windows 10 Enterprise).
|
||||
|
||||
All of your Windows 10 Pro devices will step-up to Windows 10 Enterprise, and devices that are already running Windows 10 Enterprise will migrate from KMS or MAK activated Enterprise edition to Subscription activated Enterprise edition when a Subscription Activation-enabled user signs in to the device.
|
||||
|
||||
@ -118,15 +163,12 @@ If you’re running Windows 7, it can be more work. A wipe-and-load approach w
|
||||
### Licenses
|
||||
|
||||
The following policies apply to acquisition and renewal of licenses on devices:
|
||||
- Devices that have been upgraded will attempt to acquire licenses every 30 days, and must be connected to the Internet to be successful.
|
||||
- Licenses are valid for 90 days. If a device is disconnected from the Internet until its current license expires, the operating system will revert to Windows 10 Pro. As soon as the device is connected to the Internet again, the license will automatically renew assuming the device is still present on list of user devices.
|
||||
- Devices that have been upgraded will attempt to renew licenses about every 30 days, and must be connected to the Internet to successfully acquire or renew a license.
|
||||
- If a device is disconnected from the Internet until its current subscription expires, the operating system will revert to Windows 10 Pro or Windows 10 Pro Education. As soon as the device is connected to the Internet again, the license will automatically renew.
|
||||
- Up to five devices can be upgraded for each user license.
|
||||
- The list of devices is chronological and cannot be manually modified.
|
||||
- If a device meets requirements and a licensed user signs in on that device, it will be upgraded.
|
||||
- If five devices are already on the list and a subscribed user signs in on a sixth device, then this new device is added to the end of the list and the first device is removed.
|
||||
- Devices that are removed from the list will cease trying to acquire a license and revert to Windows 10 Pro when the grace period expires.
|
||||
- If a device the meets requirements and a licensed user signs in on that device, it will be upgraded.
|
||||
|
||||
Licenses can also be reallocated from one user to another user, allowing you to optimize your licensing investment against changing needs.
|
||||
Licenses can be reallocated from one user to another user, allowing you to optimize your licensing investment against changing needs.
|
||||
|
||||
When you have the required Azure AD subscription, group-based licensing is the preferred method to assign Enterprise E3 and E5 licenses to users. For more information, see [Group-based licensing basics in Azure AD](https://docs.microsoft.com/azure/active-directory/active-directory-licensing-whatis-azure-portal).
|
||||
|
||||
@ -154,7 +196,7 @@ changepk.exe /ProductKey %ProductKey%
|
||||
)
|
||||
</pre>
|
||||
|
||||
### Obtaining an Azure AD licence
|
||||
### Obtaining an Azure AD license
|
||||
|
||||
Enterprise Agreement/Software Assurance (EA/SA):
|
||||
- Organizations with a traditional EA must order a $0 SKU, process e-mails sent to the license administrator for the company, and assign licenses using Azure AD (ideally to groups using the new Azure AD Premium feature for group assignment). For more information, see [Enabling Subscription Activation with an existing EA](https://docs.microsoft.com/windows/deployment/deploy-enterprise-licenses#enabling-subscription-activation-with-an-existing-ea).
|
||||
@ -178,6 +220,6 @@ Virtual machines (VMs) must be configured to enable Windows 10 Enterprise subscr
|
||||
|
||||
## Related topics
|
||||
|
||||
[Connect domain-joined devices to Azure AD for Windows 10 experiences](https://azure.microsoft.com/documentation/articles/active-directory-azureadjoin-devices-group-policy/)
|
||||
<BR>[Compare Windows 10 editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare)
|
||||
<BR>[Windows for business](https://www.microsoft.com/en-us/windowsforbusiness/default.aspx)
|
||||
[Connect domain-joined devices to Azure AD for Windows 10 experiences](https://azure.microsoft.com/documentation/articles/active-directory-azureadjoin-devices-group-policy/)<br>
|
||||
[Compare Windows 10 editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare)<br>
|
||||
[Windows for business](https://www.microsoft.com/en-us/windowsforbusiness/default.aspx)<br>
|
||||
@ -6,6 +6,7 @@
|
||||
### [Licensing requirements](windows-autopilot-requirements-licensing.md)
|
||||
## [Scenarios and Capabilities](windows-autopilot-scenarios.md)
|
||||
### [Support for existing devices](existing-devices.md)
|
||||
### [White glove](white-glove.md)
|
||||
### [User-driven mode](user-driven.md)
|
||||
#### [Azure Active Directory joined](user-driven-aad.md)
|
||||
#### [Hybrid Azure Active Directory joined](user-driven-hybrid.md)
|
||||
|
||||
@ -20,17 +20,20 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
## Deploying new devices
|
||||
<img src="./images/image2.png" width="511" height="249" />
|
||||
|
||||
When deploying new devices using Windows Autopilot, a common set of steps are required:
|
||||
## Configuring Autopilot to deploy new devices
|
||||
|
||||
1. [Register devices with the Windows Autopilot deployment service](add-devices.md). Ideally, this step would be performed by the OEM, reseller, or distributor from which the devices were purchased, but this can also be done by the organization by collecting the hardware identity and uploading it manually.
|
||||
|
||||
2. [Assign a profile of settings to each device](profiles.md), specifying how the device should be deployed and what user experience should be presented.
|
||||
When deploying new devices using Windows Autopilot, the following steps are required:
|
||||
|
||||
1. [Register devices](add-devices.md). Ideally, this step would be performed by the OEM, reseller, or distributor from which the devices were purchased, but this can also be done by the organization by collecting the hardware identity and uploading it manually.
|
||||
2. [Configure device profiles](profiles.md), specifying how the device should be deployed and what user experience should be presented.
|
||||
3. Boot the device. When the device is connected to a network with internet access, it will contact the Windows Autopilot deployment service to see if the device is registered, and if it is, it will download profile settings such as the [Enrollment Status page](enrollment-status.md), which are used to customize the end user experience.
|
||||
|
||||
<img src="./images/image2.png" width="511" height="249" />
|
||||
## Other configuration settings
|
||||
|
||||
- [Bitlocker encryption settings](bitlocker.md): You can configure the BitLocker encryption settings to be applied before automatic encryption is started.
|
||||
- [Cortana voiceover and speech recognition](windows-autopilot-scenarios.md): In Windows 10, version 1903 and later Cortana voiceover and speech recognition during OOBE is DISABLED by default for all Windows 10 Pro, Education and Enterprise SKUs.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 242 KiB |
BIN
windows/deployment/windows-autopilot/images/choice.png
Normal file
BIN
windows/deployment/windows-autopilot/images/choice.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
BIN
windows/deployment/windows-autopilot/images/landing.png
Normal file
BIN
windows/deployment/windows-autopilot/images/landing.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
BIN
windows/deployment/windows-autopilot/images/wg01.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg01.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.4 KiB |
BIN
windows/deployment/windows-autopilot/images/wg02.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg02.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.0 KiB |
BIN
windows/deployment/windows-autopilot/images/wg03.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg03.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 86 KiB |
BIN
windows/deployment/windows-autopilot/images/wg04.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg04.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 135 KiB |
BIN
windows/deployment/windows-autopilot/images/wg05.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg05.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
BIN
windows/deployment/windows-autopilot/images/wg06.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg06.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
BIN
windows/deployment/windows-autopilot/images/wg07.png
Normal file
BIN
windows/deployment/windows-autopilot/images/wg07.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 189 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
105
windows/deployment/windows-autopilot/white-glove.md
Normal file
105
windows/deployment/windows-autopilot/white-glove.md
Normal file
@ -0,0 +1,105 @@
|
||||
---
|
||||
title: Windows Autopilot for white glove deployment
|
||||
description: Windows Autopilot for white glove deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune, pre-provisioning
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: low
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows Autopilot for white glove deployment
|
||||
|
||||
**Applies to: Windows 10, version 1903**
|
||||
|
||||
Windows Autopilot enables organizations to easily provision new devices - leveraging the preinstalled OEM image and drivers with a simple process that can be performed by the end user to help get their device business-ready.
|
||||
|
||||
|
||||
|
||||
Windows Autopilot can also provide a <I>white glove</I> service that enables partners or IT staff to pre-provision a Windows 10 PC so that it is fully configured and business-ready. From the end user’s perspective, the Windows Autopilot user-driven experience is unchanged, but getting their device to a fully provisioned state is faster.
|
||||
|
||||
With **Windows Autopilot for white glove deployment**, the provisioning process is split. The time-consuming portions are performed by IT, partners, or OEMs. The end user simply completes a few neceesary settings and polices and then they can begin using their device.
|
||||
|
||||
|
||||
|
||||
Enabled with Microsoft Intune in Windows 10, version 1903 and later, white glove deployment capabilities build on top of existing Windows Autopilot [user-driven scenarios](user-driven.md), supporting both the user-driven [Azure AD join](user-driven-aad.md) and [Hybrid Azure AD](user-driven-hybrid.md) join scenarios.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
In addition to [Windows Autopilot requirements](windows-autopilot-requirements.md), Windows Autopilot for white glove deployment adds the following:
|
||||
|
||||
- Windows 10, version 1903 or later is required.
|
||||
- An Intune subscription with additional flighted features that are not yet available publicly is currently required. Note: This feature will change soon from flighted to preview. Prior to this feature switching to preview status, attempts to perform white glove deployment without t flighted features will fail with an Intune enrollment error.
|
||||
- Physical devices that support TPM 2.0 and device attestation; virtual machines are not supported. The white glove provisioning process leverages Windows Autopilot self-deploying capabilities, hence the TPM 2.0 requirements.
|
||||
- Physical devices with Ethernet connectivity; Wi-fi connectivity is not supported due to the requirement to choose a language, locale, and keyboard to make that Wi-fi connection; doing that in a pre-provisioning process could prevent the user from choosing their own language, locale, and keyboard when they receive the device.
|
||||
|
||||
## Preparation
|
||||
|
||||
To be ready to try out Windows Autopilot for white glove deployment, ensure that you can first successfully use existing Windows Autopilot user-driven scenarios:
|
||||
|
||||
- User-driven Azure AD join. Devices can be deployed using Windows Autopilot and joined to an Azure Active Directory tenant.
|
||||
- User-driven with Hybrid Azure AD join. Devices can be deployed using Windows Autopilot and joined to an on-premises Active Directory domain, then registered with Azure Active Directory to enable the Hybrid Azure AD join features.
|
||||
|
||||
If these scenarios cannot be completed, Windows Autopilot for white glove deployment will also not succeed since it builds on top of these scenarios.
|
||||
|
||||
To enable white glove deployment, an additional Autopilot profile setting must be configured:
|
||||
|
||||
>[!TIP]
|
||||
>To see the white glove deployment Autopilot profile setting, use this URL to access the Intune portal: https://portal.azure.com/?microsoft_intune_enrollment_enableWhiteGlove=true. This is a temporary requirement.
|
||||
|
||||
|
||||
|
||||
The Windows Autopilot for white glove deployment pre-provisioning process will apply all device-targeted policies from Intune. That includes certificates, security templates, settings, apps, and more – anything targeting the device. Additionally, any apps (Win32 or LOB) that are configured to install in the device context and targeted to the user that has been pre-assigned to the Autopilot device will also be installed. **Note**: other user-targeted policies will not apply until the user signs into the device. To verify these behaviors, be sure to create appropriate apps and policies targeted to devices and users.
|
||||
|
||||
## Scenarios
|
||||
|
||||
Windows Autopilot for white glove deployment supports two distinct scenarios:
|
||||
- User-driven deployments with Azure AD Join. The device will be joined to an Azure AD tenant.
|
||||
- User-driven deployments with Hybrid Azure AD Join. The device will be joined to an on-premises Active Directory domain, and separately registered with Azure AD.
|
||||
Each of these scenarios consists of two parts, a technician flow and a user flow. At a high level, these parts are the same for Azure AD Join and Hybrid Azure AD join; differences are primarily seen by the end user in the authentication steps.
|
||||
|
||||
### Technican flow
|
||||
|
||||
The first part of the Windows Autopilot for white glove deployment process is designed to be carried out by a technician; this could be a member of the IT staff, a services partner, or an OEM – each organization can decide who should perform these activities.
|
||||
Regardless of the scenario, the process to be performed by the technician is the same:
|
||||
- Boot the device (running Windows 10 Pro, Enterprise, or Education SKUs, version 1903 or later).
|
||||
- From the first OOBE screen (which could be a language selection or locale selection screen), do not click **Next**. Instead, press the Windows key five times to view an additional options dialog. From that screen, choose the **Windows Autopilot provisioning** option and then click **Continue**.
|
||||
|
||||
|
||||
|
||||
- On the **Windows Autopilot Configuration** screen, information will be displayed about the device:
|
||||
- The Autopilot profile assigned to the device.
|
||||
- The organization name for the device.
|
||||
- The user assigned to the device (if there is one).
|
||||
- A QR code containing a unique identifier for the device, useful to look up the device in Intune to make any configuration changes needed (e.g. assigning a user, adding the device to any additional groups needed for app or policy targeting).
|
||||
- Validate the information displayed. If any changes are needed, make these and then click **Refresh** to re-download the updated Autopilot profile details.
|
||||
|
||||
|
||||
|
||||
- Click **Provision** to begin the provisioning process.
|
||||
If the pre-provisioning process completes successfully:
|
||||
- A green status screen will be displayed with information about the device, including the same details presented previously (e.g. Autopilot profile, organization name, assigned user, QR code), as well as the elapsed time for the pre-provisioning steps.
|
||||
- Click **Reseal** to shut the device down. At that point, the device can be shipped to the end user.
|
||||
|
||||
If the pre-provisioning process fails:
|
||||
- A red status screen will be displayed with information about the device, including the same details presented previously (e.g. Autopilot profile, organization name, assigned user, QR code), as well as the elapsed time for the pre-provisioning steps.
|
||||
- Diagnostic logs can be gathered from the device, and then it can be reset to start the process over again.
|
||||
|
||||
|
||||
|
||||
### User flow
|
||||
|
||||
If the pre-provisioning process completed successfully and the device was resealed, it can be delivered to the end user to complete the normal Windows Autopilot user-driven process. They will perform a standard set of steps:
|
||||
|
||||
- Power on the device.
|
||||
- Select the appropriate language, locale, and keyboard layout.
|
||||
- Connect to a network (if using Wi-Fi). If using Hybrid Azure AD Join, there must be connectivity to a domain controller; if using Azure AD Join, internet connectivity is required.
|
||||
- On the branded sign-on screen, enter the user’s Azure Active Directory credentials.
|
||||
- If using Hybrid Azure AD Join, the device will reboot; after the reboot, enter the user’s Active Directory credentials.
|
||||
- Additional policies and apps will be delivered to the device, as tracked by the Enrollment Status Page (ESP). Once complete, the user will be able to access the desktop.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows Autopilot scenarios
|
||||
title: Windows Autopilot scenarios and capabilities
|
||||
description: Listing of Autopilot scenarios
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
@ -14,10 +14,12 @@ ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot scenarios
|
||||
# Windows Autopilot scenarios and capabilities
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
## Scenarios
|
||||
|
||||
Windows Autopilot includes support for a growing list of scenarios, designed to support common organization needs which can vary based on the type of organization and their progress moving to Windows 10 and [transitioning to modern management](https://docs.microsoft.com/windows/client-management/manage-windows-10-in-your-organization-modern-management).
|
||||
|
||||
For details about these scenarios, see these additional topics:
|
||||
@ -27,6 +29,34 @@ For details about these scenarios, see these additional topics:
|
||||
- [Windows Autopilot self-deploying mode](self-deploying.md), for devices that will be automatically configured for shared use, as a kiosk, or as a digital signage device.
|
||||
- [Windows Autopilot Reset](windows-autopilot-reset.md), to re-deploy a device in a business-ready state.
|
||||
|
||||
## Capabilities
|
||||
|
||||
### Windows Autopilot is self-updating during OOBE:
|
||||
|
||||
Starting with the Windows 10, version 1903, Autopilot functional and critical updates will begin downloading automatically during OOBE after a device gets connected to a network and the [critical driver and Windows zero-day patch (ZDP) updates](https://docs.microsoft.com/windows-hardware/customize/desktop/windows-updates-during-oobe) have completed. The user or IT admin cannot opt-out of these Autopilot updates; they are required for Windows Autopilot deployment to operate properly. Windows will alert the user that the device is checking for, downloading and installing the updates.
|
||||
|
||||
### Cortana voiceover and speech recognition during OOBE
|
||||
|
||||
In Windows 10, version 1903 and later Cortana voiceover and speech recognition during OOBE is DISABLED by default for all Windows 10 Pro, Education and Enterprise SKUs.
|
||||
|
||||
If desired, you can enable Cortana voiceover and speech recognition during OOBE by creating the following registry key. This key does not exist by default.
|
||||
|
||||
HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE\EnableVoiceForAllEditions
|
||||
|
||||
The key value is a DWORD with **0** = disabled and **1** = enabled.
|
||||
|
||||
| Value | Description |
|
||||
| --- | --- |
|
||||
| 0 | Cortana voiceover is disabled |
|
||||
| 1 | Cortana voiceover is enabled |
|
||||
| No value | Device will fall back to default behavior of the edition |
|
||||
|
||||
To change this key value, use WCD tool to create as PPKG as documented [here](https://docs.microsoft.com/windows/configuration/wcd/wcd-oobe#nforce).
|
||||
|
||||
### Bitlocker encryption
|
||||
|
||||
With Windows Autopilot, you can configure the BitLocker encryption settings to be applied before automatic encryption is started. For more information, see [Setting the BitLocker encryption algorithm for Autopilot devices](bitlocker.md)
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows Autopilot Enrollment Status page](enrollment-status.md)
|
||||
|
||||
@ -64,7 +64,7 @@ Windows Autopilot enables you to pre-register devices to your organization so th
|
||||
|
||||
Windows Autopilot enables you to:
|
||||
* Automatically join devices to Azure Active Directory (Azure AD) or Active Directory (via Hybrid Azure AD Join). See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
|
||||
* Auto-enroll devices into MDM services, such as Microsoft Intune ([*Requires an Azure AD Premium subscription*](#prerequisites)).
|
||||
* Auto-enroll devices into MDM services, such as Microsoft Intune ([*Requires an Azure AD Premium subscription*](windows-autopilot-requirements-configuration.md)).
|
||||
* Restrict the Administrator account creation.
|
||||
* Create and auto-assign devices to configuration groups based on a device's profile.
|
||||
* Customize OOBE content specific to the organization.
|
||||
|
||||
Reference in New Issue
Block a user