mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-22 18:27:23 +00:00
Merged PR 4993: 12/14 PM Publish
This commit is contained in:
Alma Jenks
commit
ea714478b4
BIN
windows/deployment/images/upgrade-analytics-settings.png
Normal file
BIN
windows/deployment/images/upgrade-analytics-settings.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 469 KiB |
@ -42,13 +42,13 @@ To enable system, application, and driver data to be shared with Microsoft, you
|
||||
Upgrade Readiness is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud based services for managing your on-premises and cloud environments. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/documentation/articles/operations-management-suite-overview/).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Upgrade Readiness is a free solution. When configured correctly, all data associated with the Upgrade Readiness solution are exempt from billing in both OMS and Azure. Upgrade Readiness data **do not** count toward OMS daily upload limits.
|
||||
>Upgrade Readiness is a free solution for Azure subsribers. When configured correctly, all data associated with the Upgrade Readiness solution are exempt from billing in both OMS and Azure. Upgrade Readiness data **do not** count toward OMS daily upload limits.
|
||||
|
||||
If you are already using OMS, you’ll find Upgrade Readiness in the Solutions Gallery. Select the **Upgrade Readiness** tile in the gallery and then click **Add** on the solution's details page. Upgrade Readiness is now visible in your workspace. While you have this dialog open, you should also consider adding the [Device Health](../update/device-health-monitor.md) and [Update Compliance](../update/update-compliance-monitor.md) solutions as well, if you haven't already. To do so, just select the check boxes for those solutions.
|
||||
|
||||
If you are not using OMS:
|
||||
|
||||
1. Go to the [Upgrade Readiness page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and click **New Customers >** to kick off the onboarding process.
|
||||
1. Go to the [Upgrade Readiness page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and select **New Customers >** to start the process.
|
||||
2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
|
||||
3. Create a new OMS workspace. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Select **Create**.
|
||||
4. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator.
|
||||
@ -57,27 +57,24 @@ If you are not using OMS:
|
||||
|
||||
5. To add the Upgrade Readiness solution to your workspace, go to the **Solutions Gallery**. Select the **Upgrade Readiness** tile in the gallery and then select **Add** on the solution’s details page. The solution is now visible on your workspace. Note that you may need to scroll to find Upgrade Readiness.
|
||||
|
||||
6. Click the **Upgrade Readiness** tile to configure the solution. The **Settings Dashboard** opens.
|
||||
|
||||
### Generate your commercial ID key
|
||||
### Copy your commercial ID key
|
||||
|
||||
Microsoft uses a unique commercial ID to map information from user computers to your OMS workspace. Generate your commercial ID key in OMS and then deploy it to user computers.
|
||||
Microsoft uses a unique commercial ID to map information from user computers to your OMS workspace. This should be generated for you automatically. Copy your commercial ID key in OMS and then deploy it to user computers.
|
||||
|
||||
1. On the Settings Dashboard, navigate to the **Windows telemetry** panel.
|
||||
|
||||
|
||||
|
||||
2. On the Windows telemetry panel, copy and save your commercial ID key. You’ll need to insert this key into the Upgrade Readiness deployment script later so it can be deployed to user computers.
|
||||
|
||||
|
||||
1. On the **Settings** dashboard, navigate to the **Windows telemetry** panel.
|
||||
|
||||
|
||||
|
||||
2. On the **Connected Sources** tab, navigate to the Windows telemetry panel.
|
||||
|
||||
>**Important**<br> Regenerate a commercial ID key only if your original ID key can no longer be used. Regenerating a commercial ID key resets the data in your workspace for all solutions that use the ID. Additionally, you’ll need to deploy the new commercial ID key to user computers again.
|
||||
|
||||
### Subscribe to Upgrade Readiness
|
||||
|
||||
For Upgrade Readiness to receive and display upgrade readiness data from Microsoft, subscribe your OMS workspace to Upgrade Readiness.
|
||||
|
||||
1. On the **Windows telemetry** panel, click **Subscribe**. The button changes to **Unsubscribe**. Unsubscribe from the Upgrade Readiness solution if you no longer want to receive upgrade-readiness information from Microsoft. Note that user computer data will continue to be shared with Microsoft for as long as the opt-in keys are set on user computers and the proxy allows the traffic.
|
||||
|
||||
1. Click **Overview** on the Settings Dashboard to return to your OMS workspace portal. The Upgrade Readiness tile now displays summary data. Click the tile to open Upgrade Readiness.
|
||||
|
||||
## Enable data sharing
|
||||
|
||||
@ -107,7 +104,7 @@ The compatibility update KB scans your computers and enables application usage t
|
||||
|
||||
| **Operating System** | **KBs** |
|
||||
|----------------------|-----------------------------------------------------------------------------|
|
||||
| Windows 10 | The latest cumulative updates must be installed on Windows 10 computers to make sure that the required compatibility KBs are installed. You can find the latest cumulative update on the [Microsoft Update Catalog](https://catalog.update.microsoft.com) <P>Note: Windows 10 LTSB is not supported by Upgrade Readiness. See [Upgrade readiness requirements](upgrade-readiness-requirements.md) for more information. |
|
||||
| Windows 10 | The latest cumulative updates must be installed on Windows 10 computers to make sure that the required compatibility updates are installed. You can find the latest cumulative update on the [Microsoft Update Catalog](https://catalog.update.microsoft.com) <P>Note: Windows 10 LTSB is not supported by Upgrade Readiness. See [Upgrade readiness requirements](upgrade-readiness-requirements.md) for more information. |
|
||||
| Windows 8.1 | [KB 2976978](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2976978)<br>Performs diagnostics on the Windows 8.1 systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether compatibility issues may be encountered when the latest Windows operating system is installed. <br>For more information about this KB, see <https://support.microsoft.com/kb/2976978><br><BR>[KB 3150513](https://catalog.update.microsoft.com/v7/site/Search.aspx?q=3150513)<br>Provides updated configuration and definitions for compatibility diagnostics performed on the system.<br>For more information about this KB, see <https://support.microsoft.com/kb/3150513><br>NOTE: KB2976978 must be installed before you can download and install KB3150513. |
|
||||
| Windows 7 SP1 | [KB2952664](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2952664) <br>Performs diagnostics on the Windows 7 SP1 systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether compatibility issues may be encountered when the latest Windows operating system is installed. <br>For more information about this KB, see <https://support.microsoft.com/kb/2952664><br><BR>[KB 3150513](https://catalog.update.microsoft.com/v7/site/Search.aspx?q=3150513)<br>Provides updated configuration and definitions for compatibility diagnostics performed on the system.<br>For more information about this KB, see <https://support.microsoft.com/kb/3150513><br>NOTE: KB2952664 must be installed before you can download and install KB3150513. |
|
||||
|
||||
|
||||
@ -18,6 +18,165 @@ author: greg-lindsay
|
||||
|
||||
To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task.
|
||||
|
||||
The following tables summarize different Windows 10 deployment options and requirements.
|
||||
|
||||
| Scenario | Description | More information |
|
||||
| :---: | :---: | :---: |
|
||||
| [Windows AutoPilot](#windows-autopilot) | Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. |[Overview of Windows AutoPilot](https://docs.microsoft.com/en-us/windows/deployment/windows-10-autopilot) |
|
||||
| [In-place upgrade](#in-place-upgrade) | Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. |[Perform an in-place upgrade to Windows 10 with MDT](https://docs.microsoft.com/windows/deployment/upgrade/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit)<br>[Perform an in-place upgrade to Windows 10 using Configuration Manager](https://docs.microsoft.com/windows/deployment/upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager) |
|
||||
| [Subscription Activation](#windows-10-subscription-activation) | Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. |[Windows 10 Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-enterprise-subscription-activation) |
|
||||
| [AAD / MDM](#dynamic-provisioning) | The device is automatically joined to AAD and configured by MDM. |[Azure Active Directory integration with MDM](https://docs.microsoft.com/windows/client-management/mdm/azure-active-directory-integration-with-mdm) |
|
||||
| [Provisioning packages](#dynamic-provisioning) | Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. |[Configure devices without MDM](https://docs.microsoft.com/windows/configuration/configure-devices-without-mdm) |
|
||||
| [Bare metal](#new-computer) | Deploy a new device, or wipe an existing device and deploy with a fresh image. |[Deploy a Windows 10 image using MDT](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt)<br>[Install a new version of Windows on a new computer with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/install-new-windows-version-new-computer-bare-metal) |
|
||||
| [Refresh](#computer-refresh) | Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. |[Refresh a Windows 7 computer with Windows 10](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10)<br>[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager) |
|
||||
| [Replace](#computer-replace) | Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. |[Replace a Windows 7 computer with a Windows 10 computer](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/replace-a-windows-7-computer-with-a-windows-10-computer)<br>[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/replace-a-windows-7-client-with-windows-10-using-configuration-manager) |
|
||||
|
||||
Secenario details:
|
||||
<br>
|
||||
|
||||
<table border="1" align='left'>
|
||||
<tr style="text-align:center;">
|
||||
<td align="center" style="width:16%; border:1;" bgcolor='#a0e4fa'>
|
||||
<b>Category</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;" bgcolor='#a0e4fa'>
|
||||
<b>Scenario</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;" bgcolor='#a0e4fa'>
|
||||
<b>Windows 10 1703 or later</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;" bgcolor='#a0e4fa'>
|
||||
<b>Windows 7 to Windows 10 1607</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;" bgcolor='#a0e4fa'>
|
||||
<b>Apps & settings migrated</b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="middle" style="width:16%; border:1;" rowspan="2">
|
||||
Modern
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
Windows AutoPilot
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
X
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
X
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
In-place upgrade
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;" rowspan="3">
|
||||
Dynamic
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
Subscription Activation
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
X
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
AAD / MDM
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
Provisioning packages
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;" rowspan="3">
|
||||
Traditional
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
Bare metal
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
X
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
Refresh
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
Replace
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
<td align="center" style="width:16%; border:1;">
|
||||
<b>✓</b>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br>
|
||||
|
||||
## Windows AutoPilot
|
||||
|
||||
Windows AutoPilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows AutoPilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator.
|
||||
@ -90,7 +249,7 @@ The traditional deployment scenario can be divided into different sub-scenarios.
|
||||
|
||||
- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup).
|
||||
|
||||
###New computer
|
||||
### New computer
|
||||
This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD).
|
||||
|
||||
The deployment process for the new machine scenario is as follows:
|
||||
@ -105,7 +264,7 @@ The deployment process for the new machine scenario is as follows:
|
||||
|
||||
After taking these steps, the computer is ready for use.
|
||||
|
||||
###Computer refresh
|
||||
### Computer refresh
|
||||
A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario.
|
||||
|
||||
The deployment process for the wipe-and-load scenario is as follows:
|
||||
@ -124,7 +283,7 @@ The deployment process for the wipe-and-load scenario is as follows:
|
||||
|
||||
After taking these steps, the machine is ready for use.
|
||||
|
||||
###Computer replace
|
||||
### Computer replace
|
||||
A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored.
|
||||
|
||||
The deployment process for the replace scenario is as follows:
|
||||
|
||||
17
windows/deployment/windows-10-deployment-workflow.md
Normal file
17
windows/deployment/windows-10-deployment-workflow.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
title: Windows 10 deployment workflow
|
||||
description: Scenarios, methods, tools, and requirements for deploying Windows 10.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: high
|
||||
ms.pagetype: deploy
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
ms.date: 12/4/2017
|
||||
---
|
||||
|
||||
# Windows 10 deployment workflow
|
||||
|
||||
|
||||
|
||||
Not finding content you need? Windows 10 users, tell us what you want on [Feedback Hub](feedback-hub://?referrer=techDocsUcPage&tabid=2&contextid=897&newFeedback=true&topic=windows-10-deployment-tools.md).
|
||||
@ -38,7 +38,7 @@ The following table show the on which operating systems AppLocker features are s
|
||||
| Windows 10| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL| You can use the [AppLocker CSP](http://msdn.microsoft.com/library/windows/hardware/dn920019.aspx) to configure AppLocker policies on any edition of Windows 10. You can only manage AppLocker with Group Policy on devices running Windows 10 Enterprise, Windows 10 Education, and Windows Server 2016. |
|
||||
| Windows Server 2016<br/>Windows Server 2012 R2<br/>Windows Server 2012| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL| |
|
||||
| Windows 8.1 Pro| Yes| No| N/A||
|
||||
| Windows 8.1 Enterprise| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL| Only the Enterprise edition supports AppLocker|
|
||||
| Windows 8.1 Enterprise| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL| |
|
||||
| Windows RT 8.1| No| No| N/A||
|
||||
| Windows 8 Pro| Yes| No| N/A||
|
||||
| Windows 8 Enterprise| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user