mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-19 00:37:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into live
This commit is contained in:
LizRoss
commit
c1a01c61c5
@ -277,7 +277,7 @@ Changes to volume levels can be sent by a room control system, or other system.
|
||||
<tr class="header">
|
||||
<th align="left">Command</th>
|
||||
<th align="left">State change</th>
|
||||
<th align="left">Response</th>
|
||||
<th align="left">Response</br>(On in [Replacement PC mode](connect-and-display-with-surface-hub.md#replacement-pc-mode))</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
@ -1,18 +1,18 @@
|
||||
# [Deploy Windows 10](index.md)
|
||||
## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
## [Manage Windows upgrades with Upgrade Analytics](manage-windows-upgrades-with-upgrade-analytics.md)
|
||||
### [Upgrade Analytics architecture](upgrade-analytics-architecture.md)
|
||||
### [Upgrade Analytics requirements](upgrade-analytics-requirements.md)
|
||||
### [Upgrade Analytics release notes](upgrade-analytics-release-notes.md)
|
||||
### [Get started with Upgrade Analytics](upgrade-analytics-get-started.md)
|
||||
#### [Upgrade Analytics deployment script](upgrade-analytics-deployment-script.md)
|
||||
### [Use Upgrade Analytics to manage Windows upgrades](use-upgrade-analytics-to-manage-windows-upgrades.md)
|
||||
#### [Upgrade overview](upgrade-analytics-upgrade-overview.md)
|
||||
#### [Step 1: Identify apps](upgrade-analytics-identify-apps.md)
|
||||
#### [Step 2: Resolve issues](upgrade-analytics-resolve-issues.md)
|
||||
#### [Step 3: Deploy Windows](upgrade-analytics-deploy-windows.md)
|
||||
#### [Additional insights](upgrade-analytics-additional-insights.md)
|
||||
### [Troubleshoot Upgrade Analytics](troubleshoot-upgrade-analytics.md)
|
||||
## [Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md)
|
||||
### [Upgrade Readiness architecture](upgrade-readiness-architecture.md)
|
||||
### [Upgrade Readiness requirements](upgrade-readiness-requirements.md)
|
||||
### [Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
|
||||
### [Get started with Upgrade Readiness](upgrade-readiness-get-started.md)
|
||||
#### [Upgrade Readiness deployment script](upgrade-readiness-deployment-script.md)
|
||||
### [Use Upgrade Readiness to manage Windows upgrades](use-upgrade-readiness-to-manage-windows-upgrades.md)
|
||||
#### [Upgrade overview](upgrade-readiness-upgrade-overview.md)
|
||||
#### [Step 1: Identify apps](upgrade-readiness-identify-apps.md)
|
||||
#### [Step 2: Resolve issues](upgrade-readiness-resolve-issues.md)
|
||||
#### [Step 3: Deploy Windows](upgrade-readiness-deploy-windows.md)
|
||||
#### [Additional insights](upgrade-readiness-additional-insights.md)
|
||||
### [Troubleshoot Upgrade Readiness](troubleshoot-upgrade-readiness.md)
|
||||
## [Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md)
|
||||
### [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md)
|
||||
### [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md)
|
||||
|
||||
@ -14,6 +14,7 @@ This topic lists new and updated topics in the [Deploy Windows 10](index.md) doc
|
||||
## February 2017
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
| [Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md) | Multiple topics updated, name changed from Upgrade Analytics to Upgrade Readiness, and other content updates. |
|
||||
| [USMT Requirements](usmt-requirements.md) | Updated: Vista support removed and other minor changes |
|
||||
| [Get started with Upgrade Analytics](upgrade-analytics-get-started.md) | Updated structure and content |
|
||||
| [Upgrade Analytics deployment script](upgrade-analytics-deployment-script.md) | Added as a separate page from get started |
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 10 KiB |
BIN
windows/deploy/images/ua-cg-09-old.png
Normal file
BIN
windows/deploy/images/ua-cg-09-old.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 54 KiB |
BIN
windows/deploy/images/ur-overview.PNG
Normal file
BIN
windows/deploy/images/ur-overview.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
BIN
windows/deploy/images/ur-target-version.png
Normal file
BIN
windows/deploy/images/ur-target-version.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
@ -17,7 +17,7 @@ Learn about deploying Windows 10 for IT professionals.
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md) |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. |
|
||||
|[Manage Windows upgrades with Upgrade Analytics](manage-windows-upgrades-with-upgrade-analytics.md) |With Upgrade Analytics, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With Windows telemetry enabled, Upgrade Analytics collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft. The Upgrade Analytics workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded. |
|
||||
|[Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md) |With Upgrade Readiness, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With Windows telemetry enabled, Upgrade Readiness collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft. The Upgrade Readiness workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded. |
|
||||
|[Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md) |This guide contains instructions to configure a proof of concept (PoC) environment requiring a minimum amount of resources. The guide makes extensive use of Windows PowerShell and Hyper-V. Subsequent companion guides contain steps to deploy Windows 10 using the PoC environment. After completing this guide, see the following Windows 10 PoC deployment guides: [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md), [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md). |
|
||||
|[Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md) |This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 2 specifically. |
|
||||
|[Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md) |If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT) or, more specifically, MDT 2013 Update 2. |
|
||||
|
||||
@ -1,43 +1,4 @@
|
||||
---
|
||||
title: Manage Windows upgrades with Upgrade Analytics (Windows 10)
|
||||
description: Provides an overview of the process of managing Windows upgrades with Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: manage-windows-upgrades-with-upgrade-readiness.md
|
||||
---
|
||||
|
||||
# Manage Windows upgrades with Upgrade Analytics
|
||||
|
||||
Upgrading to new operating systems has traditionally been a challenging, complex, and slow process for many enterprises. Discovering applications and drivers and then testing them for potential compatibility issues have been among the biggest pain points.
|
||||
|
||||
With the release of Upgrade Analytics, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With new Windows versions being released multiple times a year, ensuring application and driver compatibility on an ongoing basis is key to adopting new Windows versions as they are released.
|
||||
|
||||
Microsoft developed Upgrade Analytics in response to demand from enterprise customers looking for additional direction and details about upgrading to Windows 10. Upgrade Analytics was built taking into account multiple channels of customer feedback, testing, and Microsoft’s experience upgrading millions of devices to Windows 10.
|
||||
|
||||
With Windows telemetry enabled, Upgrade Analytics collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft.
|
||||
|
||||
Use Upgrade Analytics to get:
|
||||
|
||||
- A visual workflow that guides you from pilot to production
|
||||
- Detailed computer and application inventory
|
||||
- Powerful computer level search and drill-downs
|
||||
- Guidance and insights into application and driver compatibility issues, with suggested fixes
|
||||
- Data driven application rationalization tools
|
||||
- Application usage information, allowing targeted validation; workflow to track validation progress and decisions
|
||||
- Data export to commonly used software deployment tools, including System Center Configuration Manager
|
||||
|
||||
The Upgrade Analytics workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded.
|
||||
|
||||
**Important** For system, application, and driver data to be shared with Microsoft, you must configure user computers to send data. For information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see:
|
||||
|
||||
- [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)
|
||||
- [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
##**Related topics**
|
||||
|
||||
[Upgrade Analytics architecture](upgrade-analytics-architecture.md)<BR>
|
||||
[Upgrade Analytics requirements](upgrade-analytics-requirements.md)<BR>
|
||||
[Upgrade Analytics release notes](upgrade-analytics-release-notes.md)<BR>
|
||||
[Get started with Upgrade Analytics](upgrade-analytics-get-started.md)<BR>
|
||||
[Use Upgrade Analytics to manage Windows upgrades](use-upgrade-analytics-to-manage-windows-upgrades.md)<BR>
|
||||
[Troubleshoot Upgrade Analytics](troubleshoot-upgrade-analytics.md)<BR>
|
||||
|
||||
@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Manage Windows upgrades with Upgrade Readiness (Windows 10)
|
||||
description: Provides an overview of the process of managing Windows upgrades with Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Manage Windows upgrades with Upgrade Readiness
|
||||
|
||||
Upgrading to new operating systems has traditionally been a challenging, complex, and slow process for many enterprises. Discovering applications and drivers and then testing them for potential compatibility issues have been among the biggest pain points.
|
||||
|
||||
With the release of Upgrade Readiness, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With new Windows versions being released multiple times a year, ensuring application and driver compatibility on an ongoing basis is key to adopting new Windows versions as they are released. Windows Upgrade Readiness not only supports upgrade management from Windows 7, Windows 8.1 to Windows 10, but also Windows 10 upgrades in the [Windows as a service](https://technet.microsoft.com/en-us/itpro/windows/manage/waas-overview) model.
|
||||
|
||||
Microsoft developed Upgrade Readiness in response to demand from enterprise customers looking for additional direction and details about upgrading to Windows 10. Upgrade Readiness was built taking into account multiple channels of customer feedback, testing, and Microsoft’s experience upgrading millions of devices to Windows 10.
|
||||
|
||||
With Windows telemetry enabled, Upgrade Readiness collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft.
|
||||
|
||||
Use Upgrade Readiness to get:
|
||||
|
||||
- A visual workflow that guides you from pilot to production
|
||||
- Detailed computer and application inventory
|
||||
- Powerful computer level search and drill-downs
|
||||
- Guidance and insights into application and driver compatibility issues, with suggested fixes
|
||||
- Data driven application rationalization tools
|
||||
- Application usage information, allowing targeted validation; workflow to track validation progress and decisions
|
||||
- Data export to commonly used software deployment tools, including System Center Configuration Manager
|
||||
|
||||
The Upgrade Readiness workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded.
|
||||
|
||||
**Important** For system, application, and driver data to be shared with Microsoft, you must configure user computers to send data. For information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see:
|
||||
|
||||
- [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)
|
||||
- [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
##**Related topics**
|
||||
|
||||
[Upgrade Readiness architecture](upgrade-readiness-architecture.md)<BR>
|
||||
[Upgrade Readiness requirements](upgrade-readiness-requirements.md)<BR>
|
||||
[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)<BR>
|
||||
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)<BR>
|
||||
[Use Upgrade Readiness to manage Windows upgrades](use-upgrade-readiness-to-manage-windows-upgrades.md)<BR>
|
||||
[Troubleshoot Upgrade Readiness](troubleshoot-upgrade-readiness.md)<BR>
|
||||
@ -1,38 +1,4 @@
|
||||
---
|
||||
title: Troubleshoot Upgrade Analytics (Windows 10)
|
||||
description: Provides troubleshooting information for Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: troubleshoot-upgrade-readiness.md
|
||||
---
|
||||
|
||||
# Troubleshoot Upgrade Analytics
|
||||
|
||||
If you’re having issues seeing data in Upgrade Analytics after running the Upgrade Analytics Deployment script, make sure it completes successfully without any errors. Check the output of the script in the command window and/or log UA_dateTime_machineName.txt to ensure all steps were completed successfully. In addition, we recommend that you wait at least 48 hours before checking OMS for data after the script first completes without reporting any error.
|
||||
|
||||
If you still don’t see data in Upgrade Analytics, follow these steps:
|
||||
|
||||
1. Download and extract UpgradeAnalytics.zip. Ensure the “Diagnostics” folder is included.
|
||||
|
||||
2. Edit the script as described in [Upgrade Analytics deployment script](upgrade-analytics-deployment-script.md).
|
||||
|
||||
3. Check that isVerboseLogging is set to $true.
|
||||
|
||||
4. Run the script again. Log files will be saved to the directory specified in the script.
|
||||
|
||||
5. Open a support case with Microsoft Support through your regular channel and provide this information.
|
||||
|
||||
## Disable Upgrade Analytics
|
||||
|
||||
If you want to stop using Upgrade Analytics and stop sending telemetry data to Microsoft, follow these steps:
|
||||
|
||||
1. Unsubscribe from the Upgrade Analytics solution in the OMS portal. In the OMS portal, go to **Settings** > **Connected Sources** > **Windows Telemetry** and choose the **Unsubscribe** option.
|
||||
|
||||
|
||||
|
||||
2. Disable the Commercial Data Opt-in Key on computers running Windows 7 SP1 or 8.1. On computers running Windows 10, set the telemetry level to **Security**:
|
||||
|
||||
**Windows 7 and Windows 8.1**: Delete CommercialDataOptIn registry property from *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*
|
||||
**Windows 10**: Follow the instructions in the [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#enterprise-management) topic.
|
||||
|
||||
3. If you enabled **Internet Explorer Site Discovery**, you can disable Internet Explorer data collection by setting the *IEDataOptIn* registry key to value "0". The IEDataOptIn key can be found under: *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*.
|
||||
4. You can also remove the “CommercialId” key from: "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection". **This is an optional step**.
|
||||
|
||||
38
windows/deploy/troubleshoot-upgrade-readiness.md
Normal file
38
windows/deploy/troubleshoot-upgrade-readiness.md
Normal file
@ -0,0 +1,38 @@
|
||||
---
|
||||
title: Troubleshoot Upgrade Readiness (Windows 10)
|
||||
description: Provides troubleshooting information for Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Troubleshoot Upgrade Readiness
|
||||
|
||||
If you’re having issues seeing data in Upgrade Readiness after running the Upgrade Readiness Deployment script, make sure it completes successfully without any errors. Check the output of the script in the command window and/or log UA_dateTime_machineName.txt to ensure all steps were completed successfully. In addition, we recommend that you wait at least 48 hours before checking OMS for data after the script first completes without reporting any error.
|
||||
|
||||
If you still don’t see data in Upgrade Readiness, follow these steps:
|
||||
|
||||
1. Download and extract UpgradeAnalytics.zip. Ensure the “Diagnostics” folder is included.
|
||||
|
||||
2. Edit the script as described in [Upgrade Readiness deployment script](upgrade-readiness-deployment-script.md).
|
||||
|
||||
3. Check that isVerboseLogging is set to $true.
|
||||
|
||||
4. Run the script again. Log files will be saved to the directory specified in the script.
|
||||
|
||||
5. Open a support case with Microsoft Support through your regular channel and provide this information.
|
||||
|
||||
## Disable Upgrade Readiness
|
||||
|
||||
If you want to stop using Upgrade Readiness and stop sending telemetry data to Microsoft, follow these steps:
|
||||
|
||||
1. Unsubscribe from the Upgrade Readiness solution in the OMS portal. In the OMS portal, go to **Settings** > **Connected Sources** > **Windows Telemetry** and choose the **Unsubscribe** option.
|
||||
|
||||
|
||||
|
||||
2. Disable the Commercial Data Opt-in Key on computers running Windows 7 SP1 or 8.1. On computers running Windows 10, set the telemetry level to **Security**:
|
||||
|
||||
**Windows 7 and Windows 8.1**: Delete CommercialDataOptIn registry property from *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*
|
||||
**Windows 10**: Follow the instructions in the [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#enterprise-management) topic.
|
||||
|
||||
3. If you enabled **Internet Explorer Site Discovery**, you can disable Internet Explorer data collection by setting the *IEDataOptIn* registry key to value "0". The IEDataOptIn key can be found under: *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*.
|
||||
4. You can also remove the “CommercialId” key from: "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection". **This is an optional step**.
|
||||
@ -1,81 +1,5 @@
|
||||
---
|
||||
title: Upgrade Analytics - Additional insights
|
||||
description: Explains additional features of Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-analytics-additional-insights.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics - Additional insights
|
||||
|
||||
This topic provides information on additional features that are available in Upgrade Analytics to provide insights into your environment. These include:
|
||||
|
||||
- [Site discovery](#site-discovery): An inventory of web sites that are accessed by client computers running Windows 7 or Windows 8.1 using Internet Explorer.
|
||||
- [Office add-ins](#office-add-ins): A list of the Microsoft Office add-ins that are installed on client computers.
|
||||
|
||||
## Site discovery
|
||||
|
||||
The site discovery feature in Upgrade Analytics provides an inventory of web sites that are accessed by client computers using Internet Explorer on Windows 8.1 and Windows 7. Site discovery does not include sites that are accessed using other Web browsers, such as Microsoft Edge. Site inventory information is provided as optional data related to upgrading to Windows 10 and Internet Explorer 11, and is meant to help prioritize compatibility testing for web applications. You can make more informed decisions about testing based on usage data.
|
||||
|
||||
> Note: Site discovery data is disabled by default; you can find documentation on what is collected in the [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965). After you turn on this feature, data is collected on all sites visited by Internet Explorer, except during InPrivate sessions. In addition, the data collection process is silent, without notification to the employee. You are responsible for ensuring that your use of this feature complies with all applicable local laws and regulatory requirements, including any requirements to provide notice to employees.
|
||||
|
||||
### Install prerequisite security update for Internet Explorer
|
||||
|
||||
Ensure the following prerequisites are met before using site discovery:
|
||||
|
||||
1. Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update.
|
||||
2. Install the update for customer experience and diagnostic telemetery ([KB3080149](https://support.microsoft.com/kb/3080149)).
|
||||
3. Enable Internet Explorer data collection, which is disabled by default. The best way to enable it is to modify the [Upgrade Analytics deployment script](upgrade-analytics-deployment-script.md) to allow Internet Explorer data collection before you run it.
|
||||
|
||||
If necessary, you can also enable it by creating the following registry entry.
|
||||
|
||||
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\DataCollection
|
||||
|
||||
Entry name: IEDataOptIn
|
||||
|
||||
Data type: DWORD
|
||||
|
||||
Values:
|
||||
|
||||
> *IEOptInLevel = 0 Internet Explorer data collection is disabled*
|
||||
>
|
||||
> *IEOptInLevel = 1 Data collection is enabled for sites in the Local intranet + Trusted sites + Machine local zones*
|
||||
>
|
||||
> *IEOptInLevel = 2 Data collection is enabled for sites in the Internet + Restricted sites zones*
|
||||
>
|
||||
> *IEOptInLevel = 3 Data collection is enabled for all sites*
|
||||
|
||||
For more information about Internet Explorer Security Zones, see [About URL Security Zones](https://msdn.microsoft.com/library/ms537183.aspx).
|
||||
|
||||
|
||||
|
||||
### Review most active sites
|
||||
|
||||
This blade indicates the most visited sites by computers in your environment. Review this list to determine which web applications and sites are used most frequently. The number of visits is based on the total number of views, and not by the number of unique devices accessing a page.
|
||||
|
||||
For each site, the fully qualified domain name will be listed. You can sort the data by domain name or by URL.
|
||||
|
||||
|
||||
|
||||
Click the name of any site in the list to drill down into more details about the visits, including the time of each visit and the computer name.
|
||||
|
||||
|
||||
|
||||
### Review document modes in use
|
||||
|
||||
This blade provides information about which document modes are used in the sites that are visited in your environment. Document modes are used to provide compatibility with older versions of Internet Explorer. Sites that use older technologies may require additional testing and are less likely to be compatible with Microsoft Edge. Counts are based on total page views and not the number of unique devices. For more information about document modes, see [Deprecated document modes](https://technet.microsoft.com/itpro/internet-explorer/ie11-deploy-guide/deprecated-document-modes).
|
||||
|
||||
|
||||
|
||||
### Run browser-related queries
|
||||
|
||||
You can run predefined queries to capture more info, such as sites that have Enterprise Mode enabled, or the number of unique computers that have visited a site. For example, this query returns the most used ActiveX controls. You can modify and save the predefined queries.
|
||||
|
||||
|
||||
|
||||
## Office add-ins
|
||||
|
||||
Office add-ins provides a list of the Microsoft Office add-ins in your environment, and enumerates the computers that have these add-ins installed. This information should not affect the upgrade decision workflow, but can be helpful to an administrator.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Upgrade Analytics release notes](upgrade-analytics-release-notes.md)
|
||||
|
||||
@ -1,30 +1,4 @@
|
||||
---
|
||||
title: Upgrade Analytics architecture (Windows 10)
|
||||
description: Describes Upgrade Analytics architecture.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-readiness-architecture.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics architecture
|
||||
|
||||
Microsoft analyzes system, application, and driver telemetry data to help you determine when computers are upgrade-ready, allowing you to simplify and accelerate Windows upgrades in your organization. The diagram below illustrates how Upgrade Analytics components work together in a typical installation.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image1.png" width="624" height="401" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
After you enable Windows telemetry on user computers and install the compatibility update KB (1), user computers send computer, application and driver telemetry data to a secure Microsoft data center through the Microsoft Data Management Service (2). After you configure Upgrade Analytics, telemetry data is analyzed by the Upgrade Analytics Service (3) and pushed to your OMS workspace (4). You can then use the Upgrade Analytics solution (5) to plan and manage Windows upgrades.
|
||||
|
||||
For more information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see:
|
||||
|
||||
[Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)<BR>
|
||||
[Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)<BR>
|
||||
[Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)<BR>
|
||||
|
||||
##**Related topics**
|
||||
|
||||
[Upgrade Analytics requirements](upgrade-analytics-requirements.md)<BR>
|
||||
[Upgrade Analytics release notes](upgrade-analytics-release-notes.md)<BR>
|
||||
[Get started with Upgrade Analytics](upgrade-analytics-get-started.md)<BR>
|
||||
|
||||
@ -1,97 +1,4 @@
|
||||
---
|
||||
title: Upgrade Analytics - Get a list of computers that are upgrade-ready (Windows 10)
|
||||
description: Describes how to get a list of computers that are ready to be upgraded in Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-readiness-deploy-windows.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics - Step 3: Deploy Windows
|
||||
|
||||
All of your work up to now involved reviewing and resolving application and driver issues. Along the way, as you’ve resolved issues and decided which applications and drivers are ready to upgrade, you’ve been building a list of computers that are upgrade ready.
|
||||
The blades in the **Deploy** section are:
|
||||
|
||||
- [Deploy eligible computers](#deploy-eligible-computers)
|
||||
- [Deploy computers by group](#computer-groups)
|
||||
|
||||
>Computers that are listed in this step are assigned an **UpgradeDecision** value, and the total count of computers in each upgrade decision category is displayed. Additionally, computers are assigned an **UpgradeAssessment** value. This value is displayed by drilling down into a specific upgrade decision category. For information about upgrade assessment values, see [Upgrade assessment](#upgrade-assessment).
|
||||
|
||||
## Deploy eligible computers
|
||||
|
||||
In this blade, computers grouped by upgrade decision are listed. The upgrade decision on the machines is a calculated value based on the upgrade decision status for the apps and drivers installed on the computer. This value cannot be modified directly. The upgrade decision is calculated in the following ways:
|
||||
- **Review in progress**: At least one app or driver installed on the computer is marked **Review in progress**.
|
||||
- **Ready to upgrade**: All apps and drivers installed on the computer are marked as **Ready to Upgrade**.
|
||||
- **Won’t upgrade**: At least one app or driver installed on the computer is marked as **Won’t upgrade**, or a system requirement is not met.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image9.png" width="195" height="316" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
Select **Export computers** for more details, including computer name, manufacturer and model, and Windows edition currently running on the computer. Sort or further query the data and then select **Export** to generate and save a comma-separated value (csv) list of upgrade-ready computers.
|
||||
|
||||
>**Important**<br> When viewing inventory items in table view, the maximum number of rows that can be viewed and exported is limited to 5,000. If you need to view or export more than 5,000 items, reduce the scope of the query so you can export fewer items at a time.
|
||||
|
||||
## Computer groups
|
||||
|
||||
Computer groups allow you to segment your environment by creating device groups based on OMS log search results, or by importing groups from Active Directory, WSUS or System Center Configuration Manager. Computer groups are an OMS feature. For more information, see [Computer groups in OMS](https://blogs.technet.microsoft.com/msoms/2016/04/04/computer-groups-in-oms/).
|
||||
|
||||
Query based computer groups are recommended in the initial release of this feature. A feature known as **Configuration Manager Upgrade Analytics Connector** is anticipated in a future release that will enable synchronization of **ConfigMgr Collections** with computer groups in OMS.
|
||||
|
||||
### Getting started with Computer Groups
|
||||
|
||||
When you sign in to OMS, you will see a new blade entitled **Computer Groups**. See the following example:
|
||||
|
||||
|
||||
|
||||
To create a computer group, open **Log Search** and create a query based on **Type=UAComputer**, for example:
|
||||
|
||||
```
|
||||
Type=UAComputer Manufacturer=DELL
|
||||
```
|
||||
|
||||
|
||||
|
||||
When you are satisfied that the query is returning the intended results, add the following text to your search:
|
||||
|
||||
```
|
||||
| measure count() by Computer
|
||||
```
|
||||
|
||||
This will ensure every computer only shows up once. Then, save your group by clicking **Save** and **Yes**. See the following example:
|
||||
|
||||
|
||||
|
||||
Your new computer group will now be available in Upgrade Analytics. See the following example:
|
||||
|
||||
|
||||
|
||||
### Using Computer Groups
|
||||
|
||||
When you drill into a computer group, you will see that computers are categorized by **UpgradeDecision**. For computers with the status **Review in progress** or **Won’t upgrade** you can drill down to view issues that cause a computer to be in each category, or you can simply display a list of the computers in the category. For computers that are designated **Ready to upgrade**, you can go directly to the list of computers that are ready.
|
||||
|
||||
|
||||
|
||||
Viewing a list of computers in a certain status is self-explanatory, Let’s look at what happens when you click the details link on **Review in progress**:
|
||||
|
||||
|
||||
|
||||
Next, select if you want to see application issues (**UAApp**) or driver issues (**UADriver**). See the following example of selecting **UAApp**:
|
||||
|
||||
|
||||
|
||||
A list of apps that require review so that Dell Computers are ready for upgrade to Windows 10 is displayed.
|
||||
|
||||
### Upgrade assessment
|
||||
|
||||
Upgrade assessment and guidance details are explained in the following table.
|
||||
|
||||
| Upgrade assessment | Action required before or after upgrade pilot? | Issue | What it means | Guidance |
|
||||
|-----------------------|------------------------------------------------|----------|-----------------|---------------|
|
||||
| No known issues | No | None | Computers will upgrade seamlessly.<br> | OK to use as-is in pilot. |
|
||||
| OK to pilot, fixed during upgrade | No, for awareness only | Application or driver will not migrate to new OS | The currently installed version of an application or driver won’t migrate to the new operating system; however, a compatible version is installed with the new operating system. | OK to use as-is in pilot. |
|
||||
| OK to pilot with new driver from Windows Update | Yes | Driver will not migrate to new OS | The currently installed version of a driver won’t migrate to the new operating system; however, a newer, compatible version is available from Windows Update. | Although a compatible version of the driver is installed during upgrade, a newer version is available from Windows Update. <br><br>If the computer automatically receives updates from Windows Update, no action is required. Otherwise, replace the new in-box driver with the Windows Update version after upgrading. <br> <br> |
|
||||
|
||||
Select **Export computers** to view pilot-ready computers organized by operating system. After you select the computers you want to use in a pilot, click Export to generate and save a comma-separated value (csv) file.
|
||||
|
||||
>**Important**> When viewing inventory items in table view, the maximum number of rows that can be viewed and exported is limited to 5,000. If you need to view or export more than 5,000 items, reduce the scope of the query so you can export fewer items at a time.
|
||||
@ -1,103 +1,4 @@
|
||||
---
|
||||
title: Upgrade Analytics deployment script (Windows 10)
|
||||
description: Deployment script for Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Analytics deployment script
|
||||
|
||||
To automate the steps provided in [Get started with Upgrade Analytics](upgrade-analytics-get-started.md), and to troubleshoot data sharing issues, you can run the [Upgrade Analytics deployment script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409), developed by Microsoft.
|
||||
|
||||
For detailed information about using the upgrade analytics deployment script, also see the [Upgrade Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).
|
||||
|
||||
> The following guidance applies to version 11.11.16 or later of the Upgrade Analytics deployment script. If you are using an older version, please download the latest from [Download Center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409).
|
||||
|
||||
The Upgrade Analytics deployment script does the following:
|
||||
|
||||
1. Sets commercial ID key + CommercialDataOptIn + RequestAllAppraiserVersions keys.
|
||||
2. Verifies that user computers can send data to Microsoft.
|
||||
3. Checks whether the computer has a pending restart.
|
||||
4. Verifies that the latest version of KB package 10.0.x is installed (version 10.0.14348 or later is required, but version 10.0.14913 or later is recommended).
|
||||
5. If enabled, turns on verbose mode for troubleshooting.
|
||||
6. Initiates the collection of the telemetry data that Microsoft needs to assess your organization’s upgrade readiness.
|
||||
7. If enabled, displays the script’s progress in a cmd window, providing you immediate visibility into issues (success or fail for each step) and/or writes to log file.
|
||||
|
||||
To run the Upgrade Analytics deployment script:
|
||||
|
||||
1. Download the [Upgrade Analytics deployment script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and extract UpgradeAnalytics.zip. Inside, there are two folders: Pilot and Deployment. The Pilot folder contains advanced logging that can help troubleshoot issues and is intended to be run from an elevated command prompt. The Deployment folder offers a lightweight script intended for broad deployment through ConfigMgr or other software deployment system. We recommend manually running the Pilot version of the script on 5-10 machines to verify that everything is configured correctly. Once you have confirmed that data is flowing successfully, proceed to run the Deployment version throughout your organization.
|
||||
|
||||
2. Edit the following parameters in RunConfig.bat:
|
||||
|
||||
1. Provide a storage location for log information. You can store log information on a remote file share or a local directory. If the script is blocked from creating the log file for the given path, it creates the log files in the drive with the Windows directory. Example: %SystemDrive%\\UADiagnostics
|
||||
|
||||
2. Input your commercial ID key. This can be found in your OMS workspace under Settings -> Connected Sources -> Windows Telemetry.
|
||||
|
||||
3. By default, the script sends log information to both the console and the log file. To change the default behavior, use one of the following options:
|
||||
|
||||
> *logMode = 0 log to console only*
|
||||
>
|
||||
> *logMode = 1 log to file and console*
|
||||
>
|
||||
> *logMode = 2 log to file only*
|
||||
|
||||
3. To enable Internet Explorer data collection, set AllowIEData to IEDataOptIn. By default, AllowIEData is set to Disable. Then use one of the following options to determine what Internet Explorer data can be collected:
|
||||
|
||||
> *IEOptInLevel = 0 Internet Explorer data collection is disabled*
|
||||
>
|
||||
> *IEOptInLevel = 1 Data collection is enabled for sites in the Local intranet + Trusted sites + Machine local zones*
|
||||
>
|
||||
> *IEOptInLevel = 2 Data collection is enabled for sites in the Internet + Restricted sites zones*
|
||||
>
|
||||
> *IEOptInLevel = 3 Data collection is enabled for all sites*
|
||||
|
||||
4. After you finish editing the parameters in RunConfig.bat, you are ready to run the script. If you are using the Pilot version, run RunConfig.bat from an elevated command prompt. If you are using the Deployment version, use ConfigMgr or other software deployment service to run RunConfig.bat as system.
|
||||
|
||||
<div id="error-codes"></div>
|
||||
|
||||
The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered.
|
||||
|
||||
<div style='font-size:10.0pt'>
|
||||
|
||||
<TABLE border=1 cellspacing=0 cellpadding=0>
|
||||
<TR><TH BGCOLOR="#a0e4fa">Exit code<TH BGCOLOR="#a0e4fa">Meaning<TH BGCOLOR="#a0e4fa">Suggested fix
|
||||
<TR><TD>0<TD>Success<TD>
|
||||
<TR><TD>1<TD>Unexpected error occurred while executing the script<TD> The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again.
|
||||
<TR><TD>2<TD>Error when logging to console. $logMode = 0.<TD> Try changing the $logMode value to **1** and try again.
|
||||
<TR><TD>3<TD>Error when logging to console and file. $logMode = 1.<TD>Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
|
||||
<TR><TD>4<TD>Error when logging to file. $logMode = 2.<TD>Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
|
||||
<TR><TD>5<TD>Error when logging to console and file. $logMode = unknown.<TD>Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
|
||||
<TR><TD>6<TD>The commercialID parameter is set to unknown. Modify the script.<TD>Set the value for CommercialID in runconfig.bat file.
|
||||
<TR><TD>8<TD>Failure to create registry key path: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection. <TD> Verify that the configuration script has access to this location.
|
||||
<TR><TD>9<TD>Error when writing CommercialId to registry.<TD>Verify that the configuration script has access to this location.
|
||||
<TR><TD>10<TD>Error when writing CommercialDataOptIn to registry.<TD>Verify that the configuration script has access to this location.
|
||||
<TR><TD>11<TD>Function -SetupCommercialId: Unexpected failure.<TD>Verify that the configuration script has access to this location.
|
||||
<TR><TD>12<TD>Can’t connect to Microsoft – Vortex. Check your network/proxy settings.<TD>Verify that the required endpoints are whitelisted correctly.
|
||||
<TR><TD>13<TD>Can’t connect to Microsoft – setting. <TD>Verify that the required endpoints are whitelisted correctly.
|
||||
<TR><TD>14<TD>Can’t connect to Microsoft – compatexchange.<TD> Verify that the required endpoints are whitelisted.
|
||||
<TR><TD>15<TD>Error connecting to Microsoft:Unexpected failure.<TD>
|
||||
<TR><TD>16<TD>Machine requires reboot.<TD> The reboot is required to complete the installation of the compatibility update and related KBs. Reboot the machine before running the Upgrade Analytics deployment script.
|
||||
<TR><TD>17<TD>Function -CheckRebootRequired: Unexpected failure.<TD>The reboot is required to complete the installation of the compatibility update and related KBs. Reboot the machine before running the Upgrade Analytics deployment script.
|
||||
<TR><TD>18<TD>Outdated compatibility update KB package. Update via Windows Update/WSUS.<TD>
|
||||
The configuration script detected a version of the Compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Analytics solution. Use the latest version of the Compatibility update for Windows 7 SP1/Windows 8.1.
|
||||
<TR><TD>19<TD>The compatibility update failed with unexpected exception.<TD> The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again.
|
||||
<TR><TD>20<TD>Error writing RequestAllAppraiserVersions registry key.<TD> This registry key is required for data collection to work correctly. Verify that the configuration script has access to this location.
|
||||
<TR><TD>21<TD>Function – SetRequestAllAppraiserVersions: Unexpected failure.<TD>This registry key is required for data collection to work correctly. Verify that the configuration script has access to this location.
|
||||
<TR><TD>22<TD>RunAppraiser failed with unexpected exception.<TD> Check %windir%\System32 directory for a file called CompatTelRunner.exe. If the file does not exist, reinstall the required compatibility updates which include this file, and check your organization group policy to make sure it does not remove this file.
|
||||
<TR><TD>23<TD>Error finding system variable %WINDIR%.<TD> Make sure that this environment variable is available on the machine.
|
||||
<TR><TD>24<TD>SetIEDataOptIn failed when writing IEDataOptIn to registry.<TD> Verify that the deployment script in running in a context that has access to the registry key.
|
||||
<TR><TD>25<TD>SetIEDataOptIn failed with unexpected exception.<TD> The files in the deployment script are likely corrupted. Download the latest script from the [download center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and try again.
|
||||
<TR><TD>26<TD>The operating system is Server or LTSB SKU.<TD> The script does not support Server or LTSB SKUs.
|
||||
<TR><TD>27<TD>The script is not running under System account.<TD>The Upgrade Analytics configuration script must be run as system.
|
||||
<TR><TD>28<TD>Could not create log file at the specified logPath.<TD> Make sure the deployment script has access to the location specified in the logPath parameter.
|
||||
<TR><TD>29<TD> Connectivity check failed for proxy authentication. <TD> Install the cumulative updates on the machine and enable the `DisableEnterpriseAuthProxy` authentication proxy setting. The `DisableEnterpriseAuthProxy` setting is enabled by default for Windows 7. For Windows 8.1 machines, set the `DisableEnterpriseAuthProxy` setting to **0** (not disabled). For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
|
||||
<TR><TD>30<TD>Connectivity check failed. Registry key property `DisableEnterpriseAuthProxy` is not enabled.<TD> The `DisableEnterpriseAuthProxy` setting is enabled by default for Windows 7. For Windows 8.1 machines, set the `DisableEnterpriseAuthProxy` setting to **0** (not disabled). For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
|
||||
<TR><TD>31<TD>There is more than one instance of the Upgrade Analytics data collector running at the same time on this machine. <TD> Use the Windows Task Manager to check if CompatTelRunner.exe is running, and wait until it has completed to rerun the script.
|
||||
**The Upgrade Analytics task is scheduled to run daily at 3 a.m.**
|
||||
</TABLE>
|
||||
|
||||
</div>
|
||||
|
||||
redirect_url: upgrade-readiness-deployment-script.md
|
||||
---
|
||||
@ -1,130 +1,4 @@
|
||||
---
|
||||
title: Get started with Upgrade Analytics (Windows 10)
|
||||
description: Explains how to get started with Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Get started with Upgrade Analytics
|
||||
|
||||
This topic explains how to obtain and configure Upgrade Analytics for your organization.
|
||||
|
||||
You can use Upgrade Analytics to plan and manage your upgrade project end-to-end. Upgrade Analytics works by establishing communications between computers in your organization and Microsoft. Upgrade Analytics collects computer, application, and driver data for analysis. This data is used to identify compatibility issues that can block your upgrade and to suggest fixes that are known to Microsoft.
|
||||
|
||||
Before you begin, consider reviewing the following helpful information:<BR>
|
||||
- [Upgrade Analytics requirements](https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-requirements): Provides detailed requirements to use Upgrade Analytics.<BR>
|
||||
- [Upgrade Analytics blog](https://blogs.technet.microsoft.com/UpgradeAnalytics): Contains announcements of new features and provides helpful tips for using Upgrade Analytics.
|
||||
|
||||
>If you are using System Center Configuration Manager, also check out information about how to integrate Upgrade Analytics with Configuration Manager: [Integrate Upgrade Analytics with System Center Configuration Manager](https://docs.microsoft.com/sccm/core/clients/manage/upgrade/upgrade-analytics).
|
||||
|
||||
When you are ready to begin using Upgrade Analytics, perform the following steps:
|
||||
|
||||
1. Review [data collection and privacy](#data-collection-and-privacy) information.
|
||||
2. [Add Upgrade Analytics to OMS](#add-upgrade-analytics-to-operations-management-suite).
|
||||
3. [Enable data sharing](#enable-data-sharing).
|
||||
4. [Deploy required updates](#deploy-the-compatibility-update-and-related-kbs) to computers, and validate using a pilot deployment.
|
||||
5. [Deploy Upgrade Analytics at scale](#deploy-upgrade-analytics-at-scale).
|
||||
|
||||
## Data collection and privacy
|
||||
|
||||
To enable system, application, and driver data to be shared with Microsoft, you must configure user computers to send data. For information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see the following topics:
|
||||
|
||||
- [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)
|
||||
- [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
## Add Upgrade Analytics to Operations Management Suite
|
||||
|
||||
Upgrade Analytics 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/).
|
||||
|
||||
If you are already using OMS, you’ll find Upgrade Analytics in the Solutions Gallery. Select the **Upgrade Analytics** tile in the gallery and then click **Add** on the solution's details page. Upgrade Analytics is now visible in your workspace.
|
||||
|
||||
If you are not using OMS:
|
||||
|
||||
1. Go to the [Upgrade Analytics page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and click **Sign up** to kick off the onboarding 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.
|
||||
|
||||
> If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. Your workspace opens.
|
||||
|
||||
1. To add the Upgrade Analytics solution to your workspace, go to the **Solutions Gallery**. Select the **Upgrade Analytics** 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 Analytics.
|
||||
|
||||
2. Click the **Upgrade Analytics** tile to configure the solution. The **Settings Dashboard** opens.
|
||||
|
||||
### Generate 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.
|
||||
|
||||
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 Analytics deployment script later so it can be deployed to user computers.
|
||||
|
||||
>**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 Analytics
|
||||
|
||||
For Upgrade Analytics to receive and display upgrade readiness data from Microsoft, subscribe your OMS workspace to Upgrade Analytics.
|
||||
|
||||
1. On the **Windows telemetry** panel, click **Subscribe**. The button changes to **Unsubscribe**. Unsubscribe from the Upgrade Analytics 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 Analytics tile now displays summary data. Click the tile to open Upgrade Analytics.
|
||||
|
||||
## Enable data sharing
|
||||
|
||||
To enable data sharing, whitelist the following endpoints. Note that you may need to get approval from your security group to do this.
|
||||
|
||||
Note: The compatibility update KB runs under the computer’s system account. If you are using user authenticated proxies, read [this blog post](https://go.microsoft.com/fwlink/?linkid=838688) to learn what you need to do to run it under the logged on user account.
|
||||
|
||||
| **Endpoint** | **Function** |
|
||||
|---------------------------------------------------------|-----------|
|
||||
| `https://v10.vortex-win.data.microsoft.com/collect/v1`<br>`https://Vortex-win.data.microsoft.com/health/keepalive` | Connected User Experience and Telemetry component endpoint. User computers send data to Microsoft through this endpoint. |
|
||||
| `https://settings.data.microsoft.com/qos` | Enables the compatibility update KB to send data to Microsoft. |
|
||||
| `https://go.microsoft.com/fwlink/?LinkID=544713`<br>`https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc` | This service provides driver information about whether there will be a driver available post-upgrade for the hardware on the system. |
|
||||
|
||||
|
||||
## Deploy the compatibility update and related KBs
|
||||
|
||||
The compatibility update KB scans your computers and enables application usage tracking. If you don’t already have these KBs installed, you can download the applicable version from the Microsoft Update Catalog or deploy it using Windows Server Update Services (WSUS) or your software distribution solution, such as System Center Configuration Manager.
|
||||
|
||||
| **Operating System** | **KBs** |
|
||||
|----------------------|-----------------------------------------------------------------------------|
|
||||
| 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. |
|
||||
|
||||
IMPORTANT: Restart user computers after you install the compatibility update KBs for the first time.
|
||||
|
||||
If you are planning to enable IE Site Discovery, you will need to install a few additional KBs.
|
||||
|
||||
| **Site discovery** | **KB** |
|
||||
|----------------------|-----------------------------------------------------------------------------|
|
||||
| [Review site discovery](upgrade-analytics-review-site-discovery.md) | [KB3080149](http://www.catalog.update.microsoft.com/Search.aspx?q=3080149)<br>Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices. <br>For more information about this KB, see <https://support.microsoft.com/kb/3150513><br><br>Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update. |
|
||||
|
||||
### Deploy the Upgrade Analytics deployment script
|
||||
|
||||
You can use the Upgrade Analytics deployment script to automate and verify your deployment.
|
||||
|
||||
See [Upgrade Analytics deployment script](upgrade-analytics-deployment-script.md) for information on obtaining and running the script, and for a description of the error codes that can be displayed.
|
||||
|
||||
>After data is sent from computers to Microsoft, it generally takes 48 hours for the data to populate in Upgrade Analytics. The compatibility update KB takes several minutes to run. If the KB does not get a chance to finish running or if the computers are inaccessible (turned off or sleeping for example), data will take longer to populate in Upgrade Analytics. For this reason, you can expect most your computers to be populated in OMS in about 1-2 weeks after deploying the KB and configuration to user computers.
|
||||
|
||||
## Deploy Upgrade Analytics at scale
|
||||
|
||||
When you have completed a pilot deployment, you are ready to automate data collection and distribute the deployment script to the remaining computers in your organization.
|
||||
|
||||
### Automate data collection
|
||||
|
||||
To ensure that user computers are receiving the most up to date data from Microsoft, we recommend that you establish the following data sharing and analysis processes.
|
||||
|
||||
- Enable automatic updates for the compatibility update and related KBs. These KBs are updated frequently to include the latest application and driver issue information as we discover it during testing.
|
||||
- Schedule the Upgrade Analytics deployment script to automatically run so that you don’t have to manually initiate an inventory scan each time the compatibility update KBs are updated. Computers are re-scanned only when the compatibility KBs are updated, so if your inventory changes significantly between KB releases you won’t see the changes in Upgrade Analytics until you run the script again.
|
||||
- Schedule monthly user computer scans to view monthly active computer and usage information.
|
||||
|
||||
### Distribute the deployment script at scale
|
||||
|
||||
Use a software distribution system such as System Center Configuration Manager to distribute the Upgrade Analytics deployment script at scale. For more information, see the [Upgrade Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).
|
||||
redirect_url: upgrade-readiness-get-started.md
|
||||
---
|
||||
@ -1,36 +1,5 @@
|
||||
---
|
||||
title: Upgrade Analytics - Identify important apps (Windows 10)
|
||||
description: Describes how to prepare your environment so that you can use Upgrade Analytics to manage Windows upgrades.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-readiness-identify-apps.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics - Step 1: Identify important apps
|
||||
|
||||
This is the first step of the Upgrade Analytics workflow. In this step, applications are listed and grouped by importance level. Setting the importance level enables you to prioritize applications for upgrade.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image5.png" width="213" height="345" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
Select **Assign importance** to change an application’s importance level. By default, applications are marked **Not reviewed** or **Low install count** until you assign a different importance level to them.
|
||||
|
||||
To change an application’s importance level:
|
||||
|
||||
1. Select **Not reviewed** or **Low install count** on the **Prioritize applications** blade to view the list of applications with that importance level.
|
||||
2. Select the applications you want to change to a specific importance level and then select the appropriate option from the **Select importance level** list.
|
||||
3. Click **Save** when finished.
|
||||
|
||||
Importance levels include:
|
||||
|
||||
| Importance level | When to use it | Recommendation |
|
||||
|--------------------|------------------|------------------|
|
||||
| Low install count | We give you a head start by identifying applications that are installed on 2% or less of your total computer inventory. \[Number of computers application is installed on/total number of computers in your inventory.\]<br><br>Low install count applications are automatically marked as **Ready to upgrade** in the **UpgradeDecision** column unless they have issues that need attention.<br> | Be sure to review low install count applications for any business critical or important applications that are not yet upgrade-ready, despite their low installation rates. For example, payroll apps or tax accounting apps tend to be installed on a relatively small number of machines but are still considered business critical applications.<br><br> |
|
||||
| Not reviewed | Applications that are installed on more than 2% of your total computer inventory are marked not reviewed until you set their importance level.<br><br> | Once you’ve started to investigate an application to determine its importance level and upgrade readiness, change its status to **Review in progress** in both the **Importance** and **UpgradeDecision** columns. |
|
||||
| Business critical | By default, no applications are marked as business critical because only you can make that determination. If you know that an application is critical to your organization’s functioning, mark it **Business critical**. <br><br> | You may also want to change the application’s status to **Review in progress** in the **UpgradeDecision** column to let other team members know that you’re working on getting this business critical application upgrade-ready. Once you’ve fixed any issues and validated that the application will migrate successfully, change the upgrade decision to **Ready to upgrade**. <br> |
|
||||
| Important | By default, no applications are marked as important because only you can make that determination. If the application is important but not critical to your organization’s functioning, mark it **Important**. | You may also want to change the application’s status to **Review in progress** in the **UpgradeDecision** column to let other team members know that you’re working on getting this important application upgrade-ready. Once you’ve fixed any issues and validated that the application will migrate successfully, change the upgrade decision to **Ready to upgrade**. <br> |
|
||||
| Ignore | By default, no applications are marked as ignore because only you can make that determination. If the application is not important to your organization’s functioning, such as user-installed applications and games, you may not want to spend time and money validating that these applications will migrate successfully. Mark these applications **Ignore**. <br> | Set the application’s importance level to **Ignore** to let other team members know that it can be left as-is with no further investigation or testing. If you set the importance level to ignore, and this is an app that you are not planning on testing or validating, consider changing the upgrade decision to **Ready to upgrade**. By marking these apps ready to upgrade, you are indicating that you are comfortable upgrading with the app remaining in its current state.<br><br> |
|
||||
| Review in progress | Once you’ve started to investigate an application to determine its importance level and upgrade readiness, change its status to **Review in progress** in both the **Importance** and **UpgradeDecision** columns.<br> | As you learn more about the application’s importance to your organization’s functioning, change the importance level to **Business critical**, **Important**, or **Ignore**.<br><br>Until you’ve determined that priority applications will migrate successfully, leave the upgrade decision status as **Review in progress**. <br> |
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
title: Upgrade Analytics - Identify important apps (Windows 10)
|
||||
redirect_url: upgrade-analytics-identify-apps
|
||||
redirect_url: upgrade-readiness-identify-apps.md
|
||||
---
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Upgrade Analytics release notes (Windows 10)
|
||||
description: Provides tips and limitations about Upgrade Analytics.
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-requirements#important-information-about-this-release
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-requirements#important-information-about-this-release
|
||||
---
|
||||
@ -1,88 +1,5 @@
|
||||
---
|
||||
title: Upgrade Analytics requirements (Windows 10)
|
||||
description: Provides requirements for Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-readiness-requirements.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics requirements
|
||||
|
||||
This article introduces concepts and steps needed to get up and running with Upgrade Analytics. We recommend that you review this list of requirements before getting started as you may need to collect information, such as account credentials, and get approval from internal IT groups, such as your network security group, before you can start using Upgrade Analytics.
|
||||
|
||||
## Supported upgrade paths
|
||||
|
||||
To perform an in-place upgrade, user computers must be running the latest version of either Windows 7 SP1 or Windows 8.1. After you enable Windows telemetry, Upgrade Analytics performs a full inventory of computers so that you can see which version of Windows is installed on each computer.
|
||||
|
||||
The compatibility update KB that sends telemetry data from user computers to Microsoft data centers works with Windows 7 SP1 and Windows 8.1 only. Upgrade Analytics cannot evaluate Windows XP or Windows Vista for upgrade eligibility.
|
||||
|
||||
<!--With Windows 10, edition 1607, the compatibility update KB is installed automatically.-->
|
||||
|
||||
If you need to update user computers to Windows 7 SP1 or Windows 8.1, use Windows Update or download and deploy the applicable package from the Microsoft Download Center.
|
||||
|
||||
Note: Upgrade Analytics is designed to best support in-place upgrades. In-place upgrades do not support migrations from BIOS to UEFI or from 32-bit to 64-bit architecture. If you need to migrate computers in these scenarios, use the wipe-and-reload method. Upgrade Analytics insights are still valuable in this scenario, however, you can ignore in-place upgrade specific guidance.
|
||||
|
||||
See [Windows 10 Specifications](http://www.microsoft.com/en-US/windows/windows-10-specifications) for additional information about computer system requirements.
|
||||
|
||||
## Operations Management Suite
|
||||
|
||||
Upgrade Analytics is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud based services for managing on premise and cloud computing environments. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
||||
|
||||
If you’re already using OMS, you’ll find Upgrade Analytics in the Solutions Gallery. Click the Upgrade Analytics tile in the gallery and then click Add on the solution’s details page. Upgrade Analytics is now visible in your workspace.
|
||||
|
||||
If you are not using OMS, go to [the Upgrade Analytics page on Microsoft.com](https://www.microsoft.com/en-us/WindowsForBusiness/upgrade-analytics) and select **Sign up** to kick off the OMS onboarding process. During the onboarding process, you’ll create an OMS workspace and add the Upgrade Analytics solution to it.
|
||||
|
||||
Important: 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, 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.
|
||||
|
||||
## System Center Configuration Manager integration
|
||||
|
||||
Upgrade Analytics can be integrated with your installation of Configuration Manager. For more information, see [Integrate Upgrade Analytics with System Center Configuration Manager](https://docs.microsoft.com/sccm/core/clients/manage/upgrade/upgrade-analytics).
|
||||
|
||||
## Telemetry and data sharing
|
||||
|
||||
After you’ve signed in to Operations Management Suite and added the Upgrade Analytics solution to your workspace, you’ll need to complete the following tasks to allow user computer data to be shared with and assessed by Upgrade Analytics.
|
||||
|
||||
See [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) for more information about what user computer data Upgrade Analytics collects and assesses. See [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data.
|
||||
|
||||
**Whitelist telemetry endpoints.** To enable telemetry data to be sent to Microsoft, you’ll need to whitelist the following Microsoft telemetry endpoints on your proxy server or firewall. You may need to get approval from your security group to do this.
|
||||
|
||||
`https://v10.vortex-win.data.microsoft.com/collect/v1`<BR>
|
||||
`https://vortex-win.data.microsoft.com/health/keepalive`<BR>
|
||||
`https://settings-win.data.microsoft.com/settings`<BR>
|
||||
`https://vortex.data.microsoft.com/health/keepalive`<BR>
|
||||
`https://settings.data.microsoft.com/qos`<BR>
|
||||
`https://go.microsoft.com/fwlink/?LinkID=544713`<BR>
|
||||
`https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc/extended`<BR>
|
||||
|
||||
>**Note** The compatibility update KB runs under the computer’s system account and does not support user authentication in this release.
|
||||
|
||||
**Generate your commercial ID key.** Microsoft uses a unique commercial ID GUID to map data from your computers to your OMS workspace. You’ll need to generate your commercial ID key in OMS. We recommend that you save your commercial ID key as you’ll need it later.
|
||||
|
||||
**Subscribe your OMS workspace to Upgrade Analytics.** For Upgrade Analytics to receive and display upgrade readiness data from Microsoft, you’ll need to subscribe your OMS workspace to Upgrade Analytics.
|
||||
|
||||
**Enable telemetry and connect data sources.** To allow Upgrade Analytics to collect system, application, and driver data and assess your organization’s upgrade readiness, communication must be established between Upgrade Analytics and user computers. You’ll need to connect Upgrade Analytics to your data sources and enable telemetry to establish communication.
|
||||
|
||||
**Deploy compatibility update and related KBs.** The compatibility update KB scans your systems and enables application usage tracking. If you don’t already have this KB installed, you can download the applicable version from the Microsoft Update Catalog or deploy it using Windows Server Update Services (WSUS) or your software distribution solution, such as System Center Configuration Manager.
|
||||
|
||||
>**Important**<br> The compatibility update and related KBs are updated frequently to include new compatibility issues as they become known to Microsoft. We recommend that you use a deployment system that allows for automatic updates of these KBs. The compatibility update KB collects inventory information from computers only when it is updated.
|
||||
|
||||
**Configure and deploy Upgrade Analytics deployment script.** Configure and deploy the Upgrade Analytics deployment script to user computers to finish setting up.
|
||||
|
||||
## Important information about this release
|
||||
|
||||
Before you get started configuring Upgrade Anatlyics, review the following tips and limitations about this release.
|
||||
|
||||
**User authenticated proxies are not supported in this release.** User computers communicate with Microsoft through Windows telemetry. The Windows telemetry client runs in System context and requires a connection to various Microsoft telemetry endpoints. User authenticated proxies are not supported at this time. Work with your Network Administrator to ensure that user computers can communicate with telemetry endpoints.
|
||||
|
||||
**Upgrade Analytics does not support on-premises Windows deployments.** Upgrade Analytics is built as a cloud service, which allows Upgrade Analytics to provide you with insights based on the data from user computers and other Microsoft compatibility services. Cloud services are easy to get up and running and are cost-effective because there is no requirement to physically implement and maintain services on-premises.
|
||||
|
||||
**In-region data storage requirements.** Windows telemetry data from user computers is encrypted, sent to, and processed at Microsoft-managed secure data centers located in the US. Our analysis of the upgrade readiness-related data is then provided to you through the Upgrade Analytics solution in the Microsoft Operations Management Suite (OMS) portal. At the time this topic is being published, only OMS workspaces created in the East US and West Europe are supported. We’re adding support for additional regions and we’ll update this information when new international regions are supported.
|
||||
|
||||
### Tips
|
||||
|
||||
- When viewing inventory items in table view, the maximum number of rows that can be viewed and exported is limited to 5,000. If you need to view or export more than 5,000 items, reduce the scope of the query so you can export a list with fewer items.
|
||||
|
||||
- Sorting data by clicking a column heading may not sort your complete list of items. For information about how to sort data in OMS, see [Sorting DocumentDB data using Order By](https://azure.microsoft.com/documentation/articles/documentdb-orderby).
|
||||
|
||||
## Get started
|
||||
|
||||
See [Get started with Upgrade Analytics](upgrade-analytics-get-started.md) for detailed, step-by-step instructions for configuring Upgrade Analytics and getting started on your Windows upgrade project.
|
||||
|
||||
@ -1,145 +1,5 @@
|
||||
---
|
||||
title: Upgrade Analytics - Resolve application and driver issues (Windows 10)
|
||||
description: Describes how to resolve application and driver issues that can occur during an upgrade with Upgrade Analytics.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-readiness-resolve-issues.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics - Step 2: Resolve app and driver issues
|
||||
|
||||
This section of the Upgrade Analytics workflow reports application and driver inventory and shows you which applications have known issues, which applications have no known issues, and which drivers have issues. We identify applications and drivers that need attention and suggest fixes when we know about them.
|
||||
|
||||
You can change an application’s upgrade decision and a driver’s upgrade decision from the blades in this section. To change an application’s or a driver’s importance level, select **User changes**. Select the item you want to change and then select the appropriate option from the **Select upgrade decision** list.
|
||||
|
||||
Upgrade decisions include:
|
||||
|
||||
| Upgrade decision | When to use it | Guidance |
|
||||
|--------------------|-------------------|-------------|
|
||||
| Not reviewed | All drivers are marked as Not reviewed by default.<br><br>Any app that has not been marked **Low install count** will also have an upgrade decision of **Not reviewed** by default. <br> | Apps you have not yet reviewed or are waiting to review later should be marked as **Not reviewed**. When you start to investigate an application or a driver to determine upgrade readiness, change their upgrade decision to **Review in progress**.<br><br> |
|
||||
| Review in progress | When you start to investigate an application or a driver to determine upgrade readiness, change its upgrade decision to **Review in progress**.<br><br>Until you’ve determined that applications and drivers will migrate successfully or you’ve resolved blocking issues, leave the upgrade decision status as **Review in progress**. <br><br> | Once you’ve fixed any issues and validated that the application or driver will migrate successfully, change the upgrade decision to **Ready to upgrade**. <br> |
|
||||
| Ready to upgrade | Mark applications and drivers **Ready to upgrade** once you’ve resolved all blocking issues and you’re confident that they will upgrade successfully, or if you’ve decided to upgrade them as-is. | Applications with no known issues and with low installation rates are marked **Ready to upgrade** by default.<br><br>In Step 1, you might have marked some of your apps as **Ignore**. These should be marked as **Ready to upgrade**. Apps with low installation rates are marked as **Ready to upgrade** by default. Be sure to review any low install count applications for any business critical or important applications that are not yet upgrade-ready, despite their low installation rates. <br> |
|
||||
| Won’t upgrade | By default, no applications or drivers are marked **Won’t upgrade** because only you can make that determination. <br><br>Use **Won’t upgrade** for applications and drivers that you do not work on your target operating system, or that you are unable to upgrade.<br> | If, during your investigation into an application or driver, you determine that they should not or cannot be upgraded, mark them **Won’t upgrade**. <br><br> |
|
||||
|
||||
The blades in the **Resolve issues** section are:
|
||||
|
||||
- Review applications with known issues
|
||||
- Review applications with no known issues
|
||||
- Review drivers with known issues
|
||||
|
||||
As you review applications with known issues, you can also see ISV support statements or applications using [Ready for Windows](https://www.readyforwindows.com/).
|
||||
|
||||
## Review applications with known issues
|
||||
|
||||
Applications with issues known to Microsoft are listed, grouped by upgrade assessment into **Attention needed** or **Fix available**.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image6.png" width="192" height="321" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
To change an application's upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** to view applications with issues.
|
||||
2. In the table view, select an **UpgradeDecision** value.
|
||||
3. Select **Decide upgrade readiness** to change the upgrade decision for each application.
|
||||
4. Select the applications you want to change to a specific upgrade decision and then then select the appropriate option from the **Select upgrade decision** list.
|
||||
5. Click **Save** when finished.
|
||||
|
||||
IMORTANT: Ensure that you have the most recent versions of the compatibility update and related KBs installed to get the most up-to-date compatibility information.
|
||||
|
||||
For applications assessed as **Attention needed**, review the table below for details about known issues and for guidance about how to resolve them, when possible.
|
||||
|
||||
| Upgrade Assessment | Action required prior to upgrade? | Issue | What it means | Guidance |
|
||||
|--------------------|-----------------------------------|-----------|-----------------|------------|
|
||||
| Attention needed | No | Application is removed during upgrade | Compatibility issues were detected and the application will not migrate to the new operating system. <br> | No action is required for the upgrade to proceed. |
|
||||
| Attention needed | Yes | Blocking upgrade | Blocking issues were detected and Upgrade Analytics is not able to remove the application during upgrade. <br><br>The application may work on the new operating system.<br> | Remove the application before upgrading, and reinstall and test on new operating system. |
|
||||
| Attention needed | No | Evaluate application on new OS | The application will migrate, but issues were detected that may impact its performance on the new operating system. | No action is required for the upgrade to proceed, but be sure to test the application on the new operating system.<br> |
|
||||
| Attention needed | No | Does not work with new OS, but won’t block upgrade | The application is not compatible with the new operating system, but won’t block the upgrade. | No action is required for the upgrade to proceed, however, you’ll have to install a compatible version of the application on the new operating system.<br> |
|
||||
| Attention needed | Yes | Does not work with new OS, and will block upgrade | The application is not compatible with the new operating system and will block the upgrade. | Remove the application before upgrading. <br><br>A compatible version of the application may be available.<br> |
|
||||
| Attention needed | Yes | May block upgrade, test application | Issues were detected that may interfere with the upgrade, but need to be investigated further.<br> | Test the application’s behavior during upgrade. If it blocks the upgrade, remove it before upgrading and reinstall and test it on the new operating system.<br> |
|
||||
| Attention needed | Maybe | Multiple | Multiple issues are affecting the application. See detailed view for more information.| When you see Multiple in the query detailed view, click **Query** to see details about what issues were detected with the different versions of the application. |
|
||||
|
||||
For applications assessed as **Fix available**, review the table below for details about known issues and ways to fix them that are known to Microsoft.
|
||||
|
||||
| Upgrade Assessment | Action required prior to upgrade? | Issue | What it means | Guidance |
|
||||
|--------------------|-----------------------------------|----------|-----------------|-------------|
|
||||
| Fix available | Yes | Blocking upgrade, update application to newest version | The existing version of the application is not compatible with the new operating system and won’t migrate. A compatible version of the application is available. | Update the application before upgrading. |
|
||||
| Fix available | No | Reinstall application after upgrading | The application is compatible with the new operating system, but must be reinstalled after upgrading. The application is removed during the upgrade process.<br> | No action is required for the upgrade to proceed. Reinstall application on the new operating system. |
|
||||
| Fix available | Yes | Blocking upgrade, but can be reinstalled after upgrading | The application is compatible with the new operating system, but won’t migrate. | Remove the application before upgrading and reinstall on the new operating system.<br> |
|
||||
| Fix available | Yes | Disk encryption blocking upgrade | The application’s encryption features are blocking the upgrade. | Disable the encryption feature before upgrading and enable it again after upgrading.<br> |
|
||||
|
||||
### ISV support for applications with Ready for Windows
|
||||
|
||||
[Ready for Windows](https://www.readyforwindows.com/) lists software solutions that are supported and in use for Windows 10. This site leverages data about application adoption from commercial Windows 10 installations and helps IT managers upgrade to Windows 10 with confidence. For more information, see [Ready for Windows Frequently Asked Questions](https://developer.microsoft.com/windows/ready-for-windows/#/faq/).
|
||||
|
||||
Click **Review Applications With Known Issues** to see the status of applications for Ready for Windows and corresponding guidance. For example:
|
||||
|
||||
|
||||
|
||||
If there are known issues with an application, the specific guidance for that known issue takes precedence over the Ready for Windows guidance.
|
||||
|
||||
|
||||
|
||||
If you query with RollupLevel="NamePublisher", each version of the application can have a different status for Ready for Windows. In this case, different values appear for Ready for Windows.
|
||||
|
||||
|
||||
|
||||
The following table lists possible values for **ReadyForWindows** and what they mean. For more information, see [What does the Adoption Status mean?](https://developer.microsoft.com/en-us/windows/ready-for-windows#/faq/?scrollTo=faqStatuses)
|
||||
|
||||
| Ready for Windows Status | Query rollup level | What this means | Guidance |
|
||||
|-------------------|--------------------------|-----------------|----------|
|
||||
|Supported version available | Granular | The software provider has declared support for one or more versions of this application on Windows 10. | The ISV has declared support for a version of this application on Windows 10. |
|
||||
| Highly adopted | Granular | This version of this application has been highly adopted within the Windows 10 Enterprise ecosystem. | This application has been installed on at least 100,000 commercial Windows 10 devices. |
|
||||
| Adopted | Granular | This version of this application has been adopted within the Windows 10 Enterprise ecosystem. | This application has been installed on at least 10,000 commercial Windows 10 devices. |
|
||||
| Insufficient Data | Granular | Too few commercial Windows 10 devices are sharing information about this version of this application for Microsoft to categorize its adoption. | N/A |
|
||||
| Contact developer | Granular | There may be compatibility issues with this version of the application, so Microsoft recommends contacting the software provider to learn more. | Check [Ready for Windows](https://www.readyforwindows.com/) for additional information.|
|
||||
|Supported version available | NamePublisher | The software provider has declared support for this application on Windows 10. | The ISV has declared support for a version of this application on Windows 10.|
|
||||
|Adoption status available | NamePublisher | A Ready for Windows adoption status is available for one or more versions of this application. Please check Ready for Windows to learn more. |Check [Ready for Windows](https://www.readyforwindows.com/) for adoption information for this application.|
|
||||
| Unknown | Any | There is no Ready for Windows information available for this version of this application. Information may be available for other versions of the application at [Ready for Windows](https://www.readyforwindows.com/). | N/A |
|
||||
|
||||
## Review applications with no known issues
|
||||
|
||||
Applications with no issues known to Microsoft are listed, grouped by upgrade decision.
|
||||
|
||||
|
||||
|
||||
Applications with no known issues that are installed on 2% or less of your total computer inventory \[number of computers application is installed on/total number of computers in your inventory\] are automatically marked **Ready to upgrade** and included in the applications reviewed count. Applications with no known issues that are installed on more than 2% of your total computer inventory are automatically marked **Not reviewed**.
|
||||
|
||||
Be sure to review low install count applications for any business critical or important applications that may not yet be upgrade-ready, despite their low installation rates.
|
||||
|
||||
To change an application's upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** to view applications with issues. Select **Table** to view the list in a table.
|
||||
|
||||
2. Select **User changes** to change the upgrade decision for each application.
|
||||
|
||||
3. Select the applications you want to change to a specific upgrade decision and then then select the appropriate option from the **Select upgrade decision** list.
|
||||
|
||||
4. Click **Save** when finished.
|
||||
|
||||
## Review drivers with known issues
|
||||
|
||||
Drivers that won’t migrate to the new operating system are listed, grouped by availability.
|
||||
|
||||
|
||||
|
||||
Availability categories are explained in the table below.
|
||||
|
||||
| Driver availability | Action required before or after upgrade? | What it means | Guidance |
|
||||
|-----------------------|------------------------------------------|----------------|--------------|
|
||||
| Available in-box | No, for awareness only | The currently installed version of an application or driver won’t migrate to the new operating system; however, a compatible version is installed with the new operating system.<br> | No action is required for the upgrade to proceed. |
|
||||
| Import from Windows Update | Yes | The currently installed version of a driver won’t migrate to the new operating system; however, a compatible version is available from Windows Update.<br> | If the computer automatically receives updates from Windows Update, no action is required. Otherwise, import a new driver from Windows Update after upgrading. <br> |
|
||||
| Available in-box and from Windows Update | Yes | The currently installed version of a driver won’t migrate to the new operating system. <br><br>Although a new driver is installed during upgrade, a newer version is available from Windows Update. <br> | If the computer automatically receives updates from Windows Update, no action is required. Otherwise, import a new driver from Windows Update after upgrading. <br> |
|
||||
| Check with vendor | Yes | The driver won’t migrate to the new operating system and we are unable to locate a compatible version. <br> | Check with the independent hardware vendor (IHV) who manufactures the driver for a solution. |
|
||||
|
||||
To change a driver’s upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** and then select the group of drivers you want to review. Select **Table** to view the list in a table.
|
||||
|
||||
2. Select **User changes** to enable user input.
|
||||
|
||||
3. Select the drivers you want to change to a specific upgrade decision and then select the appropriate option from the **Select upgrade decision** list.
|
||||
|
||||
4. Click **Save** when finished.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Review site discovery
|
||||
redirect_url: upgrade-analytics-additional-insights
|
||||
redirect_url: upgrade-readiness-additional-insights.md
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -1,51 +1,4 @@
|
||||
---
|
||||
title: Upgrade Analytics - Upgrade Overview (Windows 10)
|
||||
description: Displays the total count of computers sharing data and upgraded.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: upgrade-readiness-upgrade-overview.md
|
||||
---
|
||||
|
||||
# Upgrade Analytics - Upgrade overview
|
||||
|
||||
The first blade in the Upgrade Analytics solution is the upgrade overview blade. This blade displays the total count of computers sharing data with Microsoft, and the count of computers upgraded. As you successfully upgrade computers, the count of computers upgraded increases.
|
||||
|
||||
The upgrade overivew blade displays data refresh status, including the date and time of the most recent data update and whether user changes are reflected. The following status changes are reflected on the upgrade overview blade:
|
||||
|
||||
- Computers with incomplete data:
|
||||
- Less than 4% = count is displayed in green.
|
||||
- 4% - 10% = Count is displayed in amber.
|
||||
- Greater than 10% = Count is displayed in red.
|
||||
- Delay processing device inventory data = The "Last updated" banner is displayed in amber.
|
||||
- Pending user changes = User changes count displays "Data refresh pending" in amber.
|
||||
- No pending user changes = User changes count displays "Up to date" in green.
|
||||
|
||||
In the following example, less than 4% of (3k\355k) computers have incomplete data, and there are no pending user changes:
|
||||
|
||||
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image3.png" width="214" height="345" />
|
||||
-->
|
||||
|
||||
If data processing is delayed, you can continue using your workspace as normal. However, any changes or additional information that is added might not be displayed. Data is typically refreshed and the display will return to normal again within 24 hours.
|
||||
|
||||
Select **Total computers** for a list of computers and details about them, including:
|
||||
|
||||
- Computer ID and computer name
|
||||
- Computer manufacturer
|
||||
- Computer model
|
||||
- Operating system version and build
|
||||
- Count of system requirement, application, and driver issues per computer
|
||||
- Upgrade assessment based on analysis of computer telemetry data
|
||||
- Upgrade decision status
|
||||
|
||||
Select **Total applications** for a list of applications discovered on user computers and details about them, including:
|
||||
|
||||
- Application vendor
|
||||
- Application version
|
||||
- Count of computers the application is installed on
|
||||
- Count of computers that opened the application at least once in the past 30 days
|
||||
- Percentage of computers in your total computer inventory that opened the application in the past 30 days
|
||||
- Issues detected, if any
|
||||
- Upgrade assessment based on analysis of application data
|
||||
- Rollup level
|
||||
81
windows/deploy/upgrade-readiness-additional-insights.md
Normal file
81
windows/deploy/upgrade-readiness-additional-insights.md
Normal file
@ -0,0 +1,81 @@
|
||||
---
|
||||
title: Upgrade Readiness - Additional insights
|
||||
description: Explains additional features of Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness - Additional insights
|
||||
|
||||
This topic provides information on additional features that are available in Upgrade Readiness to provide insights into your environment. These include:
|
||||
|
||||
- [Site discovery](#site-discovery): An inventory of web sites that are accessed by client computers running Windows 7 or Windows 8.1 using Internet Explorer.
|
||||
- [Office add-ins](#office-add-ins): A list of the Microsoft Office add-ins that are installed on client computers.
|
||||
|
||||
## Site discovery
|
||||
|
||||
The site discovery feature in Upgrade Readiness provides an inventory of web sites that are accessed by client computers using Internet Explorer on Windows 8.1 and Windows 7. Site discovery does not include sites that are accessed using other Web browsers, such as Microsoft Edge. Site inventory information is provided as optional data related to upgrading to Windows 10 and Internet Explorer 11, and is meant to help prioritize compatibility testing for web applications. You can make more informed decisions about testing based on usage data.
|
||||
|
||||
> Note: Site discovery data is disabled by default; you can find documentation on what is collected in the [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965). After you turn on this feature, data is collected on all sites visited by Internet Explorer, except during InPrivate sessions. In addition, the data collection process is silent, without notification to the employee. You are responsible for ensuring that your use of this feature complies with all applicable local laws and regulatory requirements, including any requirements to provide notice to employees.
|
||||
|
||||
### Install prerequisite security update for Internet Explorer
|
||||
|
||||
Ensure the following prerequisites are met before using site discovery:
|
||||
|
||||
1. Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update.
|
||||
2. Install the update for customer experience and diagnostic telemetery ([KB3080149](https://support.microsoft.com/kb/3080149)).
|
||||
3. Enable Internet Explorer data collection, which is disabled by default. The best way to enable it is to modify the [Upgrade Readiness deployment script](upgrade-readiness-deployment-script.md) to allow Internet Explorer data collection before you run it.
|
||||
|
||||
If necessary, you can also enable it by creating the following registry entry.
|
||||
|
||||
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\DataCollection
|
||||
|
||||
Entry name: IEDataOptIn
|
||||
|
||||
Data type: DWORD
|
||||
|
||||
Values:
|
||||
|
||||
> *IEOptInLevel = 0 Internet Explorer data collection is disabled*
|
||||
>
|
||||
> *IEOptInLevel = 1 Data collection is enabled for sites in the Local intranet + Trusted sites + Machine local zones*
|
||||
>
|
||||
> *IEOptInLevel = 2 Data collection is enabled for sites in the Internet + Restricted sites zones*
|
||||
>
|
||||
> *IEOptInLevel = 3 Data collection is enabled for all sites*
|
||||
|
||||
For more information about Internet Explorer Security Zones, see [About URL Security Zones](https://msdn.microsoft.com/library/ms537183.aspx).
|
||||
|
||||
|
||||
|
||||
### Review most active sites
|
||||
|
||||
This blade indicates the most visited sites by computers in your environment. Review this list to determine which web applications and sites are used most frequently. The number of visits is based on the total number of views, and not by the number of unique devices accessing a page.
|
||||
|
||||
For each site, the fully qualified domain name will be listed. You can sort the data by domain name or by URL.
|
||||
|
||||
|
||||
|
||||
Click the name of any site in the list to drill down into more details about the visits, including the time of each visit and the computer name.
|
||||
|
||||
|
||||
|
||||
### Review document modes in use
|
||||
|
||||
This blade provides information about which document modes are used in the sites that are visited in your environment. Document modes are used to provide compatibility with older versions of Internet Explorer. Sites that use older technologies may require additional testing and are less likely to be compatible with Microsoft Edge. Counts are based on total page views and not the number of unique devices. For more information about document modes, see [Deprecated document modes](https://technet.microsoft.com/itpro/internet-explorer/ie11-deploy-guide/deprecated-document-modes).
|
||||
|
||||
|
||||
|
||||
### Run browser-related queries
|
||||
|
||||
You can run predefined queries to capture more info, such as sites that have Enterprise Mode enabled, or the number of unique computers that have visited a site. For example, this query returns the most used ActiveX controls. You can modify and save the predefined queries.
|
||||
|
||||
|
||||
|
||||
## Office add-ins
|
||||
|
||||
Office add-ins provides a list of the Microsoft Office add-ins in your environment, and enumerates the computers that have these add-ins installed. This information should not affect the upgrade decision workflow, but can be helpful to an administrator.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
|
||||
30
windows/deploy/upgrade-readiness-architecture.md
Normal file
30
windows/deploy/upgrade-readiness-architecture.md
Normal file
@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Upgrade Readiness architecture (Windows 10)
|
||||
description: Describes Upgrade Readiness architecture.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness architecture
|
||||
|
||||
Microsoft analyzes system, application, and driver telemetry data to help you determine when computers are upgrade-ready, allowing you to simplify and accelerate Windows upgrades in your organization. The diagram below illustrates how Upgrade Readiness components work together in a typical installation.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image1.png" width="624" height="401" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
After you enable Windows telemetry on user computers and install the compatibility update KB (1), user computers send computer, application and driver telemetry data to a secure Microsoft data center through the Microsoft Data Management Service (2). After you configure Upgrade Readiness, telemetry data is analyzed by the Upgrade Readiness Service (3) and pushed to your OMS workspace (4). You can then use the Upgrade Readiness solution (5) to plan and manage Windows upgrades.
|
||||
|
||||
For more information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see:
|
||||
|
||||
[Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)<BR>
|
||||
[Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)<BR>
|
||||
[Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)<BR>
|
||||
|
||||
##**Related topics**
|
||||
|
||||
[Upgrade Readiness requirements](upgrade-readiness-requirements.md)<BR>
|
||||
[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)<BR>
|
||||
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)<BR>
|
||||
97
windows/deploy/upgrade-readiness-deploy-windows.md
Normal file
97
windows/deploy/upgrade-readiness-deploy-windows.md
Normal file
@ -0,0 +1,97 @@
|
||||
---
|
||||
title: Upgrade Readiness - Get a list of computers that are upgrade-ready (Windows 10)
|
||||
description: Describes how to get a list of computers that are ready to be upgraded in Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness - Step 3: Deploy Windows
|
||||
|
||||
All of your work up to now involved reviewing and resolving application and driver issues. Along the way, as you’ve resolved issues and decided which applications and drivers are ready to upgrade, you’ve been building a list of computers that are upgrade ready.
|
||||
The blades in the **Deploy** section are:
|
||||
|
||||
- [Deploy eligible computers](#deploy-eligible-computers)
|
||||
- [Deploy computers by group](#computer-groups)
|
||||
|
||||
>Computers that are listed in this step are assigned an **UpgradeDecision** value, and the total count of computers in each upgrade decision category is displayed. Additionally, computers are assigned an **UpgradeAssessment** value. This value is displayed by drilling down into a specific upgrade decision category. For information about upgrade assessment values, see [Upgrade assessment](#upgrade-assessment).
|
||||
|
||||
## Deploy eligible computers
|
||||
|
||||
In this blade, computers grouped by upgrade decision are listed. The upgrade decision on the machines is a calculated value based on the upgrade decision status for the apps and drivers installed on the computer. This value cannot be modified directly. The upgrade decision is calculated in the following ways:
|
||||
- **Review in progress**: At least one app or driver installed on the computer is marked **Review in progress**.
|
||||
- **Ready to upgrade**: All apps and drivers installed on the computer are marked as **Ready to Upgrade**.
|
||||
- **Won’t upgrade**: At least one app or driver installed on the computer is marked as **Won’t upgrade**, or a system requirement is not met.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image9.png" width="195" height="316" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
Select **Export computers** for more details, including computer name, manufacturer and model, and Windows edition currently running on the computer. Sort or further query the data and then select **Export** to generate and save a comma-separated value (csv) list of upgrade-ready computers.
|
||||
|
||||
>**Important**<br> When viewing inventory items in table view, the maximum number of rows that can be viewed and exported is limited to 5,000. If you need to view or export more than 5,000 items, reduce the scope of the query so you can export fewer items at a time.
|
||||
|
||||
## Computer groups
|
||||
|
||||
Computer groups allow you to segment your environment by creating device groups based on OMS log search results, or by importing groups from Active Directory, WSUS or System Center Configuration Manager. Computer groups are an OMS feature. For more information, see [Computer groups in OMS](https://blogs.technet.microsoft.com/msoms/2016/04/04/computer-groups-in-oms/).
|
||||
|
||||
Query based computer groups are recommended in the initial release of this feature. A feature known as **Configuration Manager Upgrade Readiness Connector** is anticipated in a future release that will enable synchronization of **ConfigMgr Collections** with computer groups in OMS.
|
||||
|
||||
### Getting started with Computer Groups
|
||||
|
||||
When you sign in to OMS, you will see a new blade entitled **Computer Groups**. See the following example:
|
||||
|
||||
|
||||
|
||||
To create a computer group, open **Log Search** and create a query based on **Type=UAComputer**, for example:
|
||||
|
||||
```
|
||||
Type=UAComputer Manufacturer=DELL
|
||||
```
|
||||
|
||||
|
||||
|
||||
When you are satisfied that the query is returning the intended results, add the following text to your search:
|
||||
|
||||
```
|
||||
| measure count() by Computer
|
||||
```
|
||||
|
||||
This will ensure every computer only shows up once. Then, save your group by clicking **Save** and **Yes**. See the following example:
|
||||
|
||||
|
||||
|
||||
Your new computer group will now be available in Upgrade Readiness. See the following example:
|
||||
|
||||
|
||||
|
||||
### Using Computer Groups
|
||||
|
||||
When you drill into a computer group, you will see that computers are categorized by **UpgradeDecision**. For computers with the status **Review in progress** or **Won’t upgrade** you can drill down to view issues that cause a computer to be in each category, or you can simply display a list of the computers in the category. For computers that are designated **Ready to upgrade**, you can go directly to the list of computers that are ready.
|
||||
|
||||
|
||||
|
||||
Viewing a list of computers in a certain status is self-explanatory, Let’s look at what happens when you click the details link on **Review in progress**:
|
||||
|
||||
|
||||
|
||||
Next, select if you want to see application issues (**UAApp**) or driver issues (**UADriver**). See the following example of selecting **UAApp**:
|
||||
|
||||
|
||||
|
||||
A list of apps that require review so that Dell Computers are ready for upgrade to Windows 10 is displayed.
|
||||
|
||||
### Upgrade assessment
|
||||
|
||||
Upgrade assessment and guidance details are explained in the following table.
|
||||
|
||||
| Upgrade assessment | Action required before or after upgrade pilot? | Issue | What it means | Guidance |
|
||||
|-----------------------|------------------------------------------------|----------|-----------------|---------------|
|
||||
| No known issues | No | None | Computers will upgrade seamlessly.<br> | OK to use as-is in pilot. |
|
||||
| OK to pilot, fixed during upgrade | No, for awareness only | Application or driver will not migrate to new OS | The currently installed version of an application or driver won’t migrate to the new operating system; however, a compatible version is installed with the new operating system. | OK to use as-is in pilot. |
|
||||
| OK to pilot with new driver from Windows Update | Yes | Driver will not migrate to new OS | The currently installed version of a driver won’t migrate to the new operating system; however, a newer, compatible version is available from Windows Update. | Although a compatible version of the driver is installed during upgrade, a newer version is available from Windows Update. <br><br>If the computer automatically receives updates from Windows Update, no action is required. Otherwise, replace the new in-box driver with the Windows Update version after upgrading. <br> <br> |
|
||||
|
||||
Select **Export computers** to view pilot-ready computers organized by operating system. After you select the computers you want to use in a pilot, click Export to generate and save a comma-separated value (csv) file.
|
||||
|
||||
>**Important**> When viewing inventory items in table view, the maximum number of rows that can be viewed and exported is limited to 5,000. If you need to view or export more than 5,000 items, reduce the scope of the query so you can export fewer items at a time.
|
||||
265
windows/deploy/upgrade-readiness-deployment-script.md
Normal file
265
windows/deploy/upgrade-readiness-deployment-script.md
Normal file
@ -0,0 +1,265 @@
|
||||
---
|
||||
title: Upgrade Readiness deployment script (Windows 10)
|
||||
description: Deployment script for Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness deployment script
|
||||
|
||||
To automate the steps provided in [Get started with Upgrade Readiness](upgrade-readiness-get-started.md), and to troubleshoot data sharing issues, you can run the [Upgrade Readiness deployment script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409), developed by Microsoft.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Upgrade Readiness was previously called Upgrade Analytics. References to Upgrade Analytics in any scripts or online content pertain to the Upgrade Readiness solution.
|
||||
|
||||
For detailed information about using the Upgrade Readiness (also known as upgrade analytics) deployment script, see the [Upgrade Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).
|
||||
|
||||
> The following guidance applies to version 11.11.16 or later of the Upgrade Readiness deployment script. If you are using an older version, please download the latest from the [Download Center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409).
|
||||
|
||||
The Upgrade Readiness deployment script does the following:
|
||||
|
||||
1. Sets commercial ID key + CommercialDataOptIn + RequestAllAppraiserVersions keys.
|
||||
2. Verifies that user computers can send data to Microsoft.
|
||||
3. Checks whether the computer has a pending restart.
|
||||
4. Verifies that the latest version of KB package 10.0.x is installed (version 10.0.14348 or later is required, but version 10.0.14913 or later is recommended).
|
||||
5. If enabled, turns on verbose mode for troubleshooting.
|
||||
6. Initiates the collection of the telemetry data that Microsoft needs to assess your organization’s upgrade readiness.
|
||||
7. If enabled, displays the script’s progress in a cmd window, providing you immediate visibility into issues (success or fail for each step) and/or writes to log file.
|
||||
|
||||
To run the Upgrade Readiness deployment script:
|
||||
|
||||
1. Download the [Upgrade Readiness deployment script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and extract UpgradeAnalytics.zip. Inside, there are two folders: Pilot and Deployment. The Pilot folder contains advanced logging that can help troubleshoot issues and is intended to be run from an elevated command prompt. The Deployment folder offers a lightweight script intended for broad deployment through ConfigMgr or other software deployment system. We recommend manually running the Pilot version of the script on 5-10 machines to verify that everything is configured correctly. Once you have confirmed that data is flowing successfully, proceed to run the Deployment version throughout your organization.
|
||||
|
||||
2. Edit the following parameters in RunConfig.bat:
|
||||
|
||||
1. Provide a storage location for log information. You can store log information on a remote file share or a local directory. If the script is blocked from creating the log file for the given path, it creates the log files in the drive with the Windows directory. Example: %SystemDrive%\\UADiagnostics
|
||||
|
||||
2. Input your commercial ID key. This can be found in your OMS workspace under Settings -> Connected Sources -> Windows Telemetry.
|
||||
|
||||
3. By default, the script sends log information to both the console and the log file. To change the default behavior, use one of the following options:
|
||||
|
||||
> *logMode = 0 log to console only*
|
||||
>
|
||||
> *logMode = 1 log to file and console*
|
||||
>
|
||||
> *logMode = 2 log to file only*
|
||||
|
||||
3. To enable Internet Explorer data collection, set AllowIEData to IEDataOptIn. By default, AllowIEData is set to Disable. Then use one of the following options to determine what Internet Explorer data can be collected:
|
||||
|
||||
> *IEOptInLevel = 0 Internet Explorer data collection is disabled*
|
||||
>
|
||||
> *IEOptInLevel = 1 Data collection is enabled for sites in the Local intranet + Trusted sites + Machine local zones*
|
||||
>
|
||||
> *IEOptInLevel = 2 Data collection is enabled for sites in the Internet + Restricted sites zones*
|
||||
>
|
||||
> *IEOptInLevel = 3 Data collection is enabled for all sites*
|
||||
|
||||
4. After you finish editing the parameters in RunConfig.bat, you are ready to run the script. If you are using the Pilot version, run RunConfig.bat from an elevated command prompt. If you are using the Deployment version, use ConfigMgr or other software deployment service to run RunConfig.bat as system.
|
||||
|
||||
The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered.
|
||||
|
||||
<div style='font-size:8.0pt'>
|
||||
|
||||
<TABLE border=1 cellspacing=0 cellpadding=0>
|
||||
|
||||
<TR><TD BGCOLOR="#a0e4fa" width=5>Exit code</TD>
|
||||
<TD BGCOLOR="#a0e4fa">Meaning
|
||||
<TD BGCOLOR="#a0e4fa">Suggested fix
|
||||
|
||||
<TR><TD>0</TD>
|
||||
<TD>Success
|
||||
<TD>N/A
|
||||
|
||||
<TR><TD>1</TD>
|
||||
<TD>Unexpected error occurred while executing the script.
|
||||
<TD> The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again.
|
||||
|
||||
<TR><TD>2</TD>
|
||||
<TD>Error when logging to console. $logMode = 0.<BR>(console only)
|
||||
<TD>Try changing the $logMode value to **1** and try again.<BR>$logMode value 1 logs to both console and file.
|
||||
|
||||
<TR><TD>3</TD>
|
||||
<TD>Error when logging to console and file. $logMode = 1.
|
||||
<TD>Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
|
||||
|
||||
<TR><TD>4</TD>
|
||||
<TD>Error when logging to file. $logMode = 2.
|
||||
<TD>Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
|
||||
|
||||
<TR><TD>5</TD>
|
||||
<TD>Error when logging to console and file. $logMode = unknown.
|
||||
<TD>Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
|
||||
|
||||
<TR><TD>6</TD>
|
||||
<TD>The commercialID parameter is set to unknown. <BR>Modify the runConfig.bat file to set the CommercialID value.
|
||||
<TD>The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace.
|
||||
<BR>See [Generate your Commercial ID key](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace.
|
||||
|
||||
<TR><TD>8</TD>
|
||||
<TD>Failure to create registry key path: <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div>
|
||||
<TD>The Commercial Id property is set at the following registry key path: <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div>
|
||||
<BR>Verify that the context under which the script in running has access to the registry key.
|
||||
|
||||
<TR><TD>9</TD>
|
||||
<TD>The script failed to write Commercial Id to registry.
|
||||
<BR>Error creating or updating registry key: **CommercialId** at <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div>
|
||||
<TD>Verify that the context under which the script in running has access to the registry key.
|
||||
|
||||
<TR><TD>10</TD>
|
||||
<TD>Error when writing **CommercialDataOptIn** to the registry at <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div>
|
||||
<TD>Verify that the deployment script is running in a context that has access to the registry key.
|
||||
|
||||
<TR><TD>11</TD>
|
||||
<TD>Function **SetupCommercialId** failed with an unexpected exception.
|
||||
<TD>The **SetupCommercialId** function updates the Commercial Id at the registry key path: <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div> <BR>Verify that the configuration script has access to this location.
|
||||
|
||||
<TR><TD>12</TD>
|
||||
<TD>Can’t connect to Microsoft - Vortex. Check your network/proxy settings.
|
||||
<TD>**Http Get** on the end points did not return a success exit code.<BR>
|
||||
For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.<BR>
|
||||
For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive.
|
||||
<BR>If there is an error verifying connectivity, this will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
|
||||
|
||||
|
||||
<TR><TD>13</TD>
|
||||
<TD>Can’t connect to Microsoft - setting.
|
||||
<TD>An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
|
||||
|
||||
|
||||
<TR><TD>14</TD>
|
||||
<TD>Can’t connect to Microsoft - compatexchange.
|
||||
<TD>An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
|
||||
|
||||
<TR><TD>15</TD>
|
||||
<TD>Function CheckVortexConnectivity failed with an unexpected exception.
|
||||
<TD>This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). Check the logs for the exception message and the HResult.
|
||||
|
||||
<TR><TD>16</TD>
|
||||
<TD>The computer requires a reboot before running the script.
|
||||
<TD>A reboot is required to complete the installation of the compatibility update and related KBs. Reboot the computer before running the Upgrade Readiness deployment script.
|
||||
|
||||
<TR><TD>17</TD>
|
||||
<TD>Function **CheckRebootRequired** failed with an unexpected exception.
|
||||
<TD>A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult.
|
||||
|
||||
<TR><TD>18</TD>
|
||||
<TD>Appraiser KBs not installed or **appraiser.dll** not found.
|
||||
<TD>Either the Appraiser KBs are not installed, or the **appraiser.dll** file was not found. For more information, see appraiser telemetry events and fields information in the [Data collection](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#data-collection-and-privacy) and privacy topic.
|
||||
|
||||
<TR><TD>19</TD>
|
||||
<TD>Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception.
|
||||
<TD>Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
|
||||
|
||||
<TR><TD>20</TD>
|
||||
<TD>An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**</div>
|
||||
<TD>The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
|
||||
|
||||
<TR><TD>21</TD>
|
||||
<TD>Function **SetRequestAllAppraiserVersions** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>22</TD>
|
||||
<TD>**RunAppraiser** failed with unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult. Check the **%windir%\System32*8 directory for the file **CompatTelRunner.exe**. If the file does not exist, reinstall the required compatibility updates which include this file, and check your organization's Group Policy to verify it does not remove this file.
|
||||
|
||||
<TR><TD>23</TD>
|
||||
<TD>Error finding system variable **%WINDIR%**.
|
||||
<TD>Verify that this environment variable is configured on the computer.
|
||||
|
||||
<TR><TD>24</TD>
|
||||
<TD>The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div>
|
||||
<TD>This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>25</TD>
|
||||
<TD>The function **SetIEDataOptIn** failed with unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>26</TD>
|
||||
<TD>The operating system is Server or LTSB SKU.
|
||||
<TD> The script does not support Server or LTSB SKUs.
|
||||
|
||||
<TR><TD>27</TD>
|
||||
<TD>The script is not running under **System** account.
|
||||
<TD>The Upgrade Readiness configuration script must be run as **System**.
|
||||
|
||||
<TR><TD>28</TD>
|
||||
<TD>Could not create log file at the specified **logPath**.
|
||||
<TD> Make sure the deployment script has access to the location specified in the **logPath** parameter.
|
||||
|
||||
<TR><TD>29</TD>
|
||||
<TD>Connectivity check failed for proxy authentication.
|
||||
<TD>Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting.
|
||||
<BR>The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
|
||||
<BR>For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled).
|
||||
<BR>For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
|
||||
|
||||
<TR><TD>30</TD>
|
||||
<TD>Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled.
|
||||
<TD>The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
|
||||
<BR>For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled).
|
||||
<BR>For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
|
||||
|
||||
<TR><TD>31</TD>
|
||||
<TD>There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer.
|
||||
<TD>Use the Windows Task Manager to check if **CompatTelRunner.exe** is running, and wait until it has completed to rerun the script. The Upgrade Readiness task is scheduled to run daily at 3 a.m.
|
||||
|
||||
<TR><TD>32</TD>
|
||||
<TD>Appraiser version on the machine is outdated.
|
||||
<TD>The configuration script detected a version of the compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Readiness solution. Use the latest version of the [compatibility update](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1.
|
||||
|
||||
<TR><TD>33</TD>
|
||||
<TD>**CompatTelRunner.exe** exited with an exit code
|
||||
<TD>**CompatTelRunner.exe** runs the appraise task on the machine. If it fails, it will provide a specific exit code. The script will return exit code 33 when **CompatTelRunner.exe** itself exits with an exit code. Please check the logs for more details.
|
||||
|
||||
<TR><TD>34</TD>
|
||||
<TD>Function **CheckProxySettings** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>35</TD>
|
||||
<TD>Function **CheckAuthProxy** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>36</TD>
|
||||
<TD>Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>37</TD>
|
||||
<TD>**Diagnose_internal.cmd** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>38</TD>
|
||||
<TD>Function **Get-SqmID** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>39</TD>
|
||||
<TD>For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**</div>
|
||||
or <div style='font-size:7.0pt'>**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**</div>
|
||||
<TD>For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
|
||||
|
||||
<TR><TD>40</TD>
|
||||
<TD>Function **CheckTelemetryOptIn** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>41</TD>
|
||||
<TD>The script failed to impersonate the currently logged on user.
|
||||
<TD>The script mimics the UTC client to collect upgrade readiness data. When auth proxy is set, the UTC client impersonates the logged on user. The script also tries to mimic this, but the process failed.
|
||||
|
||||
<TR><TD>42</TD>
|
||||
<TD>Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
<TR><TD>43</TD>
|
||||
<TD>Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception.
|
||||
<TD>Check the logs for the exception message and HResult.
|
||||
|
||||
</TABLE>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
133
windows/deploy/upgrade-readiness-get-started.md
Normal file
133
windows/deploy/upgrade-readiness-get-started.md
Normal file
@ -0,0 +1,133 @@
|
||||
---
|
||||
title: Get started with Upgrade Readiness (Windows 10)
|
||||
description: Explains how to get started with Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Get started with Upgrade Readiness
|
||||
|
||||
This topic explains how to obtain and configure Upgrade Readiness for your organization.
|
||||
|
||||
You can use Upgrade Readiness to plan and manage your upgrade project end-to-end. Upgrade Readiness works by establishing communications between computers in your organization and Microsoft. Upgrade Readiness collects computer, application, and driver data for analysis. This data is used to identify compatibility issues that can block your upgrade and to suggest fixes that are known to Microsoft.
|
||||
|
||||
Before you begin, consider reviewing the following helpful information:<BR>
|
||||
- [Upgrade Readiness requirements](upgrade-readiness-requirements.md): Provides detailed requirements to use Upgrade Readiness.<BR>
|
||||
- [Upgrade Readiness blog](https://blogs.technet.microsoft.com/UpgradeAnalytics): Contains announcements of new features and provides helpful tips for using Upgrade Readiness.
|
||||
|
||||
>If you are using System Center Configuration Manager, also check out information about how to integrate Upgrade Readiness with Configuration Manager: [Integrate Upgrade Readiness with System Center Configuration Manager](https://docs.microsoft.com/sccm/core/clients/manage/upgrade/upgrade-analytics).
|
||||
|
||||
When you are ready to begin using Upgrade Readiness, perform the following steps:
|
||||
|
||||
1. Review [data collection and privacy](#data-collection-and-privacy) information.
|
||||
2. [Add Upgrade Readiness to OMS](#add-upgrade-readiness-to-operations-management-suite).
|
||||
3. [Enable data sharing](#enable-data-sharing).
|
||||
4. [Deploy required updates](#deploy-the-compatibility-update-and-related-kbs) to computers, and validate using a pilot deployment.
|
||||
5. [Deploy Upgrade Readiness at scale](#deploy-upgrade-readiness-at-scale).
|
||||
|
||||
## Data collection and privacy
|
||||
|
||||
To enable system, application, and driver data to be shared with Microsoft, you must configure user computers to send data. For information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see the following topics:
|
||||
|
||||
- [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)
|
||||
- [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
## Add Upgrade Readiness to Operations Management Suite
|
||||
|
||||
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/).
|
||||
|
||||
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.
|
||||
|
||||
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 **Sign up** to kick off the onboarding 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.
|
||||
|
||||
> If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. Your workspace opens.
|
||||
|
||||
1. 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.
|
||||
|
||||
2. Click the **Upgrade Readiness** tile to configure the solution. The **Settings Dashboard** opens.
|
||||
|
||||
### Generate 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.
|
||||
|
||||
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.
|
||||
|
||||
>**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
|
||||
|
||||
To enable data sharing, whitelist the following endpoints. Note that you may need to get approval from your security group to do this.
|
||||
|
||||
Note: The compatibility update KB runs under the computer’s system account. If you are using user authenticated proxies, read [this blog post](https://go.microsoft.com/fwlink/?linkid=838688) to learn what you need to do to run it under the logged on user account.
|
||||
|
||||
| **Endpoint** | **Function** |
|
||||
|---------------------------------------------------------|-----------|
|
||||
| `https://v10.vortex-win.data.microsoft.com/collect/v1`<br>`https://Vortex-win.data.microsoft.com/health/keepalive` | Connected User Experience and Telemetry component endpoint. User computers send data to Microsoft through this endpoint. |
|
||||
| `https://settings.data.microsoft.com/qos` | Enables the compatibility update KB to send data to Microsoft. |
|
||||
| `https://go.microsoft.com/fwlink/?LinkID=544713`<br>`https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc` | This service provides driver information about whether there will be a driver available post-upgrade for the hardware on the system. |
|
||||
|
||||
|
||||
## Deploy the compatibility update and related KBs
|
||||
|
||||
The compatibility update KB scans your computers and enables application usage tracking. If you don’t already have these KBs installed, you can download the applicable version from the Microsoft Update Catalog or deploy it using Windows Server Update Services (WSUS) or your software distribution solution, such as System Center Configuration Manager.
|
||||
|
||||
| **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 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. |
|
||||
|
||||
IMPORTANT: Restart user computers after you install the compatibility update KBs for the first time.
|
||||
|
||||
If you are planning to enable IE Site Discovery, you will need to install a few additional KBs.
|
||||
|
||||
| **Site discovery** | **KB** |
|
||||
|----------------------|-----------------------------------------------------------------------------|
|
||||
| [Review site discovery](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-additional-insights#site-discovery) | [KB3080149](http://www.catalog.update.microsoft.com/Search.aspx?q=3080149)<br>Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices. <br>For more information about this KB, see <https://support.microsoft.com/kb/3150513><br><br>Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update. |
|
||||
|
||||
### Deploy the Upgrade Readiness deployment script
|
||||
|
||||
You can use the Upgrade Readiness deployment script to automate and verify your deployment.
|
||||
|
||||
See [Upgrade Readiness deployment script](upgrade-readiness-deployment-script.md) for information on obtaining and running the script, and for a description of the error codes that can be displayed.
|
||||
|
||||
>After data is sent from computers to Microsoft, it generally takes 48 hours for the data to populate in Upgrade Readiness. The compatibility update KB takes several minutes to run. If the KB does not get a chance to finish running or if the computers are inaccessible (turned off or sleeping for example), data will take longer to populate in Upgrade Readiness. For this reason, you can expect most your computers to be populated in OMS in about 1-2 weeks after deploying the KB and configuration to user computers.
|
||||
|
||||
## Deploy Upgrade Readiness at scale
|
||||
|
||||
When you have completed a pilot deployment, you are ready to automate data collection and distribute the deployment script to the remaining computers in your organization.
|
||||
|
||||
### Automate data collection
|
||||
|
||||
To ensure that user computers are receiving the most up to date data from Microsoft, we recommend that you establish the following data sharing and analysis processes.
|
||||
|
||||
- Enable automatic updates for the compatibility update and related KBs. These KBs are updated frequently to include the latest application and driver issue information as we discover it during testing.
|
||||
- Schedule the Upgrade Readiness deployment script to automatically run so that you don’t have to manually initiate an inventory scan each time the compatibility update KBs are updated.
|
||||
- Schedule monthly user computer scans to view monthly active computer and usage information.
|
||||
|
||||
>When you run the deployment script, it initiates a full scan. The daily scheduled task to capture the deltas are created when the update package is installed. A full scan averages to about 2 MB, but the delta scans are very small. For Windows 10 devices, its already part of the OS. This is the **Windows Compat Appraiser** task. Deltas are invoked via the nightly scheduled task. It attempts to run around 3AM, but if system is off at that time, the task will run when the system is turned on.
|
||||
|
||||
### Distribute the deployment script at scale
|
||||
|
||||
Use a software distribution system such as System Center Configuration Manager to distribute the Upgrade Readiness deployment script at scale. For more information, see the [Upgrade Readiness blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).
|
||||
36
windows/deploy/upgrade-readiness-identify-apps.md
Normal file
36
windows/deploy/upgrade-readiness-identify-apps.md
Normal file
@ -0,0 +1,36 @@
|
||||
---
|
||||
title: Upgrade Readiness - Identify important apps (Windows 10)
|
||||
description: Describes how to prepare your environment so that you can use Upgrade Readiness to manage Windows upgrades.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness - Step 1: Identify important apps
|
||||
|
||||
This is the first step of the Upgrade Readiness workflow. In this step, applications are listed and grouped by importance level. Setting the importance level enables you to prioritize applications for upgrade.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image5.png" width="213" height="345" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
Select **Assign importance** to change an application’s importance level. By default, applications are marked **Not reviewed** or **Low install count** until you assign a different importance level to them.
|
||||
|
||||
To change an application’s importance level:
|
||||
|
||||
1. Select **Not reviewed** or **Low install count** on the **Prioritize applications** blade to view the list of applications with that importance level.
|
||||
2. Select the applications you want to change to a specific importance level and then select the appropriate option from the **Select importance level** list.
|
||||
3. Click **Save** when finished.
|
||||
|
||||
Importance levels include:
|
||||
|
||||
| Importance level | When to use it | Recommendation |
|
||||
|--------------------|------------------|------------------|
|
||||
| Low install count | We give you a head start by identifying applications that are installed on 2% or less of your total computer inventory. \[Number of computers application is installed on/total number of computers in your inventory.\]<br><br>Low install count applications are automatically marked as **Ready to upgrade** in the **UpgradeDecision** column unless they have issues that need attention.<br> | Be sure to review low install count applications for any business critical or important applications that are not yet upgrade-ready, despite their low installation rates. For example, payroll apps or tax accounting apps tend to be installed on a relatively small number of machines but are still considered business critical applications.<br><br> |
|
||||
| Not reviewed | Applications that are installed on more than 2% of your total computer inventory are marked not reviewed until you set their importance level.<br><br> | Once you’ve started to investigate an application to determine its importance level and upgrade readiness, change its status to **Review in progress** in both the **Importance** and **UpgradeDecision** columns. |
|
||||
| Business critical | By default, no applications are marked as business critical because only you can make that determination. If you know that an application is critical to your organization’s functioning, mark it **Business critical**. <br><br> | You may also want to change the application’s status to **Review in progress** in the **UpgradeDecision** column to let other team members know that you’re working on getting this business critical application upgrade-ready. Once you’ve fixed any issues and validated that the application will migrate successfully, change the upgrade decision to **Ready to upgrade**. <br> |
|
||||
| Important | By default, no applications are marked as important because only you can make that determination. If the application is important but not critical to your organization’s functioning, mark it **Important**. | You may also want to change the application’s status to **Review in progress** in the **UpgradeDecision** column to let other team members know that you’re working on getting this important application upgrade-ready. Once you’ve fixed any issues and validated that the application will migrate successfully, change the upgrade decision to **Ready to upgrade**. <br> |
|
||||
| Ignore | By default, no applications are marked as ignore because only you can make that determination. If the application is not important to your organization’s functioning, such as user-installed applications and games, you may not want to spend time and money validating that these applications will migrate successfully. Mark these applications **Ignore**. <br> | Set the application’s importance level to **Ignore** to let other team members know that it can be left as-is with no further investigation or testing. If you set the importance level to ignore, and this is an app that you are not planning on testing or validating, consider changing the upgrade decision to **Ready to upgrade**. By marking these apps ready to upgrade, you are indicating that you are comfortable upgrading with the app remaining in its current state.<br><br> |
|
||||
| Review in progress | Once you’ve started to investigate an application to determine its importance level and upgrade readiness, change its status to **Review in progress** in both the **Importance** and **UpgradeDecision** columns.<br> | As you learn more about the application’s importance to your organization’s functioning, change the importance level to **Business critical**, **Important**, or **Ignore**.<br><br>Until you’ve determined that priority applications will migrate successfully, leave the upgrade decision status as **Review in progress**. <br> |
|
||||
|
||||
5
windows/deploy/upgrade-readiness-release-notes.md
Normal file
5
windows/deploy/upgrade-readiness-release-notes.md
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
title: Upgrade Readiness release notes (Windows 10)
|
||||
description: Provides tips and limitations about Upgrade Readiness.
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-requirements#important-information-about-this-release
|
||||
---
|
||||
95
windows/deploy/upgrade-readiness-requirements.md
Normal file
95
windows/deploy/upgrade-readiness-requirements.md
Normal file
@ -0,0 +1,95 @@
|
||||
---
|
||||
title: Upgrade Readiness requirements (Windows 10)
|
||||
description: Provides requirements for Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness requirements
|
||||
|
||||
This article introduces concepts and steps needed to get up and running with Upgrade Readiness. We recommend that you review this list of requirements before getting started as you may need to collect information, such as account credentials, and get approval from internal IT groups, such as your network security group, before you can start using Upgrade Readiness.
|
||||
|
||||
## Supported upgrade paths
|
||||
|
||||
### Windows 7 and Windows 8.1
|
||||
|
||||
To perform an in-place upgrade, user computers must be running the latest version of either Windows 7 SP1 or Windows 8.1. After you enable Windows telemetry, Upgrade Readiness performs a full inventory of computers so that you can see which version of Windows is installed on each computer.
|
||||
|
||||
The compatibility update KB that sends telemetry data from user computers to Microsoft data centers works with Windows 7 SP1 and Windows 8.1 only. Upgrade Readiness cannot evaluate Windows XP or Windows Vista for upgrade eligibility.
|
||||
|
||||
<!--With Windows 10, edition 1607, the compatibility update KB is installed automatically.-->
|
||||
|
||||
If you need to update user computers to Windows 7 SP1 or Windows 8.1, use Windows Update or download and deploy the applicable package from the Microsoft Download Center.
|
||||
|
||||
Note: Upgrade Readiness is designed to best support in-place upgrades. In-place upgrades do not support migrations from BIOS to UEFI or from 32-bit to 64-bit architecture. If you need to migrate computers in these scenarios, use the wipe-and-reload method. Upgrade Readiness insights are still valuable in this scenario, however, you can ignore in-place upgrade specific guidance.
|
||||
|
||||
See [Windows 10 Specifications](http://www.microsoft.com/en-US/windows/windows-10-specifications) for additional information about computer system requirements.
|
||||
|
||||
### Windows 10
|
||||
|
||||
Keeping Windows 10 up to date involves deploying a feature update, and Upgrade Readiness tools help you prepare and plan for these Windows updates.
|
||||
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).
|
||||
|
||||
Windows 10 LTSB is not supported by Upgrade Readiness. The LTSB (long term servicing branch) of Windows 10 is not intended for general deployment, and does not receive feature updates, therefore it is not compatible with Upgrade Readiness. See [Windows as a service overview](https://technet.microsoft.com/en-us/itpro/windows/manage/waas-overview#long-term-servicing-branch) to understand more about LTSB.
|
||||
|
||||
## Operations Management Suite
|
||||
|
||||
Upgrade Readiness is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud based services for managing on premise and cloud computing environments. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
||||
|
||||
If you’re already using OMS, you’ll find Upgrade Readiness in the Solutions Gallery. Click 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.
|
||||
|
||||
If you are not using OMS, go to the [Upgrade Readiness page](https://www.microsoft.com/en-us/WindowsForBusiness/upgrade-analytics) on Microsoft.com and select **Sign up** to kick off the OMS onboarding process. During the onboarding process, you’ll create an OMS workspace and add the Upgrade Readiness solution to it.
|
||||
|
||||
Important: 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, 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. You also need an Azure subscription to link to your OMS workspace. The account you used to create the workspace must have administrator permissions on the Azure subscription in order to link the workspace to the Azure account. Once the link has been established, you can revoke the administrator permissions.
|
||||
|
||||
## System Center Configuration Manager integration
|
||||
|
||||
Upgrade Readiness can be integrated with your installation of Configuration Manager. For more information, see [Integrate Upgrade Readiness with System Center Configuration Manager](https://docs.microsoft.com/sccm/core/clients/manage/upgrade/upgrade-analytics).
|
||||
|
||||
## Telemetry and data sharing
|
||||
|
||||
After you’ve signed in to Operations Management Suite and added the Upgrade Readiness solution to your workspace, you’ll need to complete the following tasks to allow user computer data to be shared with and assessed by Upgrade Readiness.
|
||||
|
||||
See [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) for more information about what user computer data Upgrade Readiness collects and assesses. See [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data.
|
||||
|
||||
**Whitelist telemetry endpoints.** To enable telemetry data to be sent to Microsoft, you’ll need to whitelist the following Microsoft telemetry endpoints on your proxy server or firewall. You may need to get approval from your security group to do this.
|
||||
|
||||
`https://v10.vortex-win.data.microsoft.com/collect/v1`<BR>
|
||||
`https://vortex-win.data.microsoft.com/health/keepalive`<BR>
|
||||
`https://settings.data.microsoft.com/qos`<BR>
|
||||
`https://go.microsoft.com/fwlink/?LinkID=544713`<BR>
|
||||
`https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc`<BR>
|
||||
|
||||
>**Note** The compatibility update KB runs under the computer’s system account and does not support user authentication in this release.
|
||||
|
||||
**Generate your commercial ID key.** Microsoft uses a unique commercial ID GUID to map data from your computers to your OMS workspace. You’ll need to generate your commercial ID key in OMS. We recommend that you save your commercial ID key as you’ll need it later.
|
||||
|
||||
**Subscribe your OMS workspace to Upgrade Readiness.** For Upgrade Readiness to receive and display upgrade readiness data from Microsoft, you’ll need to subscribe your OMS workspace to Upgrade Readiness.
|
||||
|
||||
**Enable telemetry and connect data sources.** To allow Upgrade Readiness to collect system, application, and driver data and assess your organization’s upgrade readiness, communication must be established between Upgrade Readiness and user computers. You’ll need to connect Upgrade Readiness to your data sources and enable telemetry to establish communication.
|
||||
|
||||
**Deploy compatibility update and related KBs.** The compatibility update KB scans your systems and enables application usage tracking. If you don’t already have this KB installed, you can download the applicable version from the Microsoft Update Catalog or deploy it using Windows Server Update Services (WSUS) or your software distribution solution, such as System Center Configuration Manager.
|
||||
|
||||
>**Important**<br> The compatibility update and related KBs are updated frequently to include new compatibility issues as they become known to Microsoft. We recommend that you use a deployment system that allows for automatic updates of these KBs. The compatibility update KB collects inventory information from computers only when it is updated.
|
||||
|
||||
**Configure and deploy Upgrade Readiness deployment script.** Configure and deploy the Upgrade Readiness deployment script to user computers to finish setting up.
|
||||
|
||||
## Important information about this release
|
||||
|
||||
Before you get started configuring Upgrade Anatlyics, review the following tips and limitations about this release.
|
||||
|
||||
**User authenticated proxies are not supported in this release.** User computers communicate with Microsoft through Windows telemetry. The Windows telemetry client runs in System context and requires a connection to various Microsoft telemetry endpoints. User authenticated proxies are not supported at this time. Work with your Network Administrator to ensure that user computers can communicate with telemetry endpoints.
|
||||
|
||||
**Upgrade Readiness does not support on-premises Windows deployments.** Upgrade Readiness is built as a cloud service, which allows Upgrade Readiness to provide you with insights based on the data from user computers and other Microsoft compatibility services. Cloud services are easy to get up and running and are cost-effective because there is no requirement to physically implement and maintain services on-premises.
|
||||
|
||||
**In-region data storage requirements.** Windows telemetry data from user computers is encrypted, sent to, and processed at Microsoft-managed secure data centers located in the US. Our analysis of the upgrade readiness-related data is then provided to you through the Upgrade Readiness solution in the Microsoft Operations Management Suite (OMS) portal. At the time this topic is being published, only OMS workspaces created in the East US and West Europe are supported. We’re adding support for additional regions and we’ll update this information when new international regions are supported.
|
||||
|
||||
### Tips
|
||||
|
||||
- When viewing inventory items in table view, the maximum number of rows that can be viewed and exported is limited to 5,000. If you need to view or export more than 5,000 items, reduce the scope of the query so you can export a list with fewer items.
|
||||
|
||||
- Sorting data by clicking a column heading may not sort your complete list of items. For information about how to sort data in OMS, see [Sorting DocumentDB data using Order By](https://azure.microsoft.com/documentation/articles/documentdb-orderby).
|
||||
|
||||
## Get started
|
||||
|
||||
See [Get started with Upgrade Readiness](upgrade-readiness-get-started.md) for detailed, step-by-step instructions for configuring Upgrade Readiness and getting started on your Windows upgrade project.
|
||||
152
windows/deploy/upgrade-readiness-resolve-issues.md
Normal file
152
windows/deploy/upgrade-readiness-resolve-issues.md
Normal file
@ -0,0 +1,152 @@
|
||||
---
|
||||
title: Upgrade Readiness - Resolve application and driver issues (Windows 10)
|
||||
description: Describes how to resolve application and driver issues that can occur during an upgrade with Upgrade Readiness.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness - Step 2: Resolve app and driver issues
|
||||
|
||||
This section of the Upgrade Readiness workflow reports application and driver inventory and shows you which applications have known issues, which applications have no known issues, and which drivers have issues. We identify applications and drivers that need attention and suggest fixes when we know about them.
|
||||
|
||||
You can change an application’s upgrade decision and a driver’s upgrade decision from the blades in this section. To change an application’s or a driver’s importance level, select **User changes**. Select the item you want to change and then select the appropriate option from the **Select upgrade decision** list.
|
||||
|
||||
Upgrade decisions include:
|
||||
|
||||
| Upgrade decision | When to use it | Guidance |
|
||||
|--------------------|-------------------|-------------|
|
||||
| Not reviewed | All drivers are marked as Not reviewed by default.<br><br>Any app that has not been marked **Low install count** will also have an upgrade decision of **Not reviewed** by default. <br> | Apps you have not yet reviewed or are waiting to review later should be marked as **Not reviewed**. When you start to investigate an application or a driver to determine upgrade readiness, change their upgrade decision to **Review in progress**.<br><br> |
|
||||
| Review in progress | When you start to investigate an application or a driver to determine upgrade readiness, change its upgrade decision to **Review in progress**.<br><br>Until you’ve determined that applications and drivers will migrate successfully or you’ve resolved blocking issues, leave the upgrade decision status as **Review in progress**. <br><br> | Once you’ve fixed any issues and validated that the application or driver will migrate successfully, change the upgrade decision to **Ready to upgrade**. <br> |
|
||||
| Ready to upgrade | Mark applications and drivers **Ready to upgrade** once you’ve resolved all blocking issues and you’re confident that they will upgrade successfully, or if you’ve decided to upgrade them as-is. | Applications with no known issues and with low installation rates are marked **Ready to upgrade** by default.<br><br>In Step 1, you might have marked some of your apps as **Ignore**. These should be marked as **Ready to upgrade**. Apps with low installation rates are marked as **Ready to upgrade** by default. Be sure to review any low install count applications for any business critical or important applications that are not yet upgrade-ready, despite their low installation rates. <br> |
|
||||
| Won’t upgrade | By default, no applications or drivers are marked **Won’t upgrade** because only you can make that determination. <br><br>Use **Won’t upgrade** for applications and drivers that you do not work on your target operating system, or that you are unable to upgrade.<br> | If, during your investigation into an application or driver, you determine that they should not or cannot be upgraded, mark them **Won’t upgrade**. <br><br> |
|
||||
|
||||
The blades in the **Resolve issues** section are:
|
||||
|
||||
- Review applications with known issues
|
||||
- Review applications with no known issues
|
||||
- Review drivers with known issues
|
||||
|
||||
As you review applications with known issues, you can also see ISV support statements or applications using [Ready for Windows](https://www.readyforwindows.com/).
|
||||
|
||||
## Review applications with known issues
|
||||
|
||||
Applications with issues known to Microsoft are listed, grouped by upgrade assessment into **Attention needed** or **Fix available**.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image6.png" width="192" height="321" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
To change an application's upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** to view applications with issues.
|
||||
2. In the table view, select an **UpgradeDecision** value.
|
||||
3. Select **Decide upgrade readiness** to change the upgrade decision for each application.
|
||||
4. Select the applications you want to change to a specific upgrade decision and then then select the appropriate option from the **Select upgrade decision** list.
|
||||
5. Click **Save** when finished.
|
||||
|
||||
IMORTANT: Ensure that you have the most recent versions of the compatibility update and related KBs installed to get the most up-to-date compatibility information.
|
||||
|
||||
For applications assessed as **Attention needed**, review the table below for details about known issues and for guidance about how to resolve them, when possible.
|
||||
|
||||
| Upgrade Assessment | Action required prior to upgrade? | Issue | What it means | Guidance |
|
||||
|--------------------|-----------------------------------|-----------|-----------------|------------|
|
||||
| Attention needed | No | Application is removed during upgrade | Compatibility issues were detected and the application will not migrate to the new operating system. <br> | No action is required for the upgrade to proceed. |
|
||||
| Attention needed | Yes | Blocking upgrade | Blocking issues were detected and Upgrade Analytics is not able to remove the application during upgrade. <br><br>The application may work on the new operating system.<br> | Remove the application before upgrading, and reinstall and test on new operating system. |
|
||||
| Attention needed | No | Evaluate application on new OS | The application will migrate, but issues were detected that may impact its performance on the new operating system. | No action is required for the upgrade to proceed, but be sure to test the application on the new operating system.<br> |
|
||||
| Attention needed | No | Does not work with new OS, but won’t block upgrade | The application is not compatible with the new operating system, but won’t block the upgrade. | No action is required for the upgrade to proceed, however, you’ll have to install a compatible version of the application on the new operating system.<br> |
|
||||
| Attention needed | Yes | Does not work with new OS, and will block upgrade | The application is not compatible with the new operating system and will block the upgrade. | Remove the application before upgrading. <br><br>A compatible version of the application may be available.<br> |
|
||||
| Attention needed | Yes | May block upgrade, test application | Issues were detected that may interfere with the upgrade, but need to be investigated further.<br> | Test the application’s behavior during upgrade. If it blocks the upgrade, remove it before upgrading and reinstall and test it on the new operating system.<br> |
|
||||
| Attention needed | Maybe | Multiple | Multiple issues are affecting the application. See detailed view for more information.| When you see Multiple in the query detailed view, click **Query** to see details about what issues were detected with the different versions of the application. |
|
||||
|
||||
For applications assessed as **Fix available**, review the table below for details about known issues and ways to fix them that are known to Microsoft.
|
||||
|
||||
| Upgrade Assessment | Action required prior to upgrade? | Issue | What it means | Guidance |
|
||||
|--------------------|-----------------------------------|----------|-----------------|-------------|
|
||||
| Fix available | Yes | Blocking upgrade, update application to newest version | The existing version of the application is not compatible with the new operating system and won’t migrate. A compatible version of the application is available. | Update the application before upgrading. |
|
||||
| Fix available | No | Reinstall application after upgrading | The application is compatible with the new operating system, but must be reinstalled after upgrading. The application is removed during the upgrade process.<br> | No action is required for the upgrade to proceed. Reinstall application on the new operating system. |
|
||||
| Fix available | Yes | Blocking upgrade, but can be reinstalled after upgrading | The application is compatible with the new operating system, but won’t migrate. | Remove the application before upgrading and reinstall on the new operating system.<br> |
|
||||
| Fix available | Yes | Disk encryption blocking upgrade | The application’s encryption features are blocking the upgrade. | Disable the encryption feature before upgrading and enable it again after upgrading.<br> |
|
||||
|
||||
### ISV support for applications with Ready for Windows
|
||||
|
||||
[Ready for Windows](https://www.readyforwindows.com/) lists software solutions that are supported and in use for Windows 10. This site leverages data about application adoption from commercial Windows 10 installations and helps IT managers upgrade to Windows 10 with confidence. For more information, see [Ready for Windows Frequently Asked Questions](https://developer.microsoft.com/windows/ready-for-windows/#/faq/).
|
||||
|
||||
Click **Review Applications With Known Issues** to see the status of applications for Ready for Windows and corresponding guidance. For example:
|
||||
|
||||
|
||||
|
||||
If there are known issues with an application, the specific guidance for that known issue takes precedence over the Ready for Windows guidance.
|
||||
|
||||
|
||||
|
||||
If you query with RollupLevel="NamePublisher", each version of the application can have a different status for Ready for Windows. In this case, different values appear for Ready for Windows.
|
||||
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>Within the Upgrade Readiness data model, an object of Type **UAApp** refers to a particular application installed on a specific computer.
|
||||
|
||||
>To support dynamic aggregation and summation of data the Upgrade Readiness solution "rolls up" (aggregates) data in preprocessing. Rolling up to the **Granular** level enables display of the **App** level. In Upgrade Readiness terminology, an **App** is a unique combination of: app name, app vendor, app version, and app language. Thus, at the Granular level, you can see attributes such as **total install count**, which is the number of machines with a specific **App** installed.
|
||||
|
||||
>Upgrade Readiness also has a roll up level of **NamePublisher**, This level enables you to ignore different app versions within your organization for a particular app. In other words, **NamePublisher** displays statistics about a given app, aggregated across all versions.
|
||||
|
||||
The following table lists possible values for **ReadyForWindows** and what they mean. For more information, see [What does the Adoption Status mean?](https://developer.microsoft.com/en-us/windows/ready-for-windows#/faq/?scrollTo=faqStatuses)
|
||||
|
||||
| Ready for Windows Status | Query rollup level | What this means | Guidance |
|
||||
|-------------------|--------------------------|-----------------|----------|
|
||||
|Supported version available | Granular | The software provider has declared support for one or more versions of this application on Windows 10. | The ISV has declared support for a version of this application on Windows 10. |
|
||||
| Highly adopted | Granular | This version of this application has been highly adopted within the Windows 10 Enterprise ecosystem. | This application has been installed on at least 100,000 commercial Windows 10 devices. |
|
||||
| Adopted | Granular | This version of this application has been adopted within the Windows 10 Enterprise ecosystem. | This application has been installed on at least 10,000 commercial Windows 10 devices. |
|
||||
| Insufficient Data | Granular | Too few commercial Windows 10 devices are sharing information about this version of this application for Microsoft to categorize its adoption. | N/A |
|
||||
| Contact developer | Granular | There may be compatibility issues with this version of the application, so Microsoft recommends contacting the software provider to learn more. | Check [Ready for Windows](https://www.readyforwindows.com/) for additional information.|
|
||||
|Supported version available | NamePublisher | The software provider has declared support for this application on Windows 10. | The ISV has declared support for a version of this application on Windows 10.|
|
||||
|Adoption status available | NamePublisher | A Ready for Windows adoption status is available for one or more versions of this application. Please check Ready for Windows to learn more. |Check [Ready for Windows](https://www.readyforwindows.com/) for adoption information for this application.|
|
||||
| Unknown | Any | There is no Ready for Windows information available for this version of this application. Information may be available for other versions of the application at [Ready for Windows](https://www.readyforwindows.com/). | N/A |
|
||||
|
||||
## Review applications with no known issues
|
||||
|
||||
Applications with no issues known to Microsoft are listed, grouped by upgrade decision.
|
||||
|
||||
|
||||
|
||||
Applications with no known issues that are installed on 2% or less of your total computer inventory \[number of computers application is installed on/total number of computers in your inventory\] are automatically marked **Ready to upgrade** and included in the applications reviewed count. Applications with no known issues that are installed on more than 2% of your total computer inventory are automatically marked **Not reviewed**.
|
||||
|
||||
Be sure to review low install count applications for any business critical or important applications that may not yet be upgrade-ready, despite their low installation rates.
|
||||
|
||||
To change an application's upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** to view applications with issues. Select **Table** to view the list in a table.
|
||||
|
||||
2. Select **User changes** to change the upgrade decision for each application.
|
||||
|
||||
3. Select the applications you want to change to a specific upgrade decision and then then select the appropriate option from the **Select upgrade decision** list.
|
||||
|
||||
4. Click **Save** when finished.
|
||||
|
||||
## Review drivers with known issues
|
||||
|
||||
Drivers that won’t migrate to the new operating system are listed, grouped by availability.
|
||||
|
||||
|
||||
|
||||
Availability categories are explained in the table below.
|
||||
|
||||
| Driver availability | Action required before or after upgrade? | What it means | Guidance |
|
||||
|-----------------------|------------------------------------------|----------------|--------------|
|
||||
| Available in-box | No, for awareness only | The currently installed version of an application or driver won’t migrate to the new operating system; however, a compatible version is installed with the new operating system.<br> | No action is required for the upgrade to proceed. |
|
||||
| Import from Windows Update | Yes | The currently installed version of a driver won’t migrate to the new operating system; however, a compatible version is available from Windows Update.<br> | If the computer automatically receives updates from Windows Update, no action is required. Otherwise, import a new driver from Windows Update after upgrading. <br> |
|
||||
| Available in-box and from Windows Update | Yes | The currently installed version of a driver won’t migrate to the new operating system. <br><br>Although a new driver is installed during upgrade, a newer version is available from Windows Update. <br> | If the computer automatically receives updates from Windows Update, no action is required. Otherwise, import a new driver from Windows Update after upgrading. <br> |
|
||||
| Check with vendor | Yes | The driver won’t migrate to the new operating system and we are unable to locate a compatible version. <br> | Check with the independent hardware vendor (IHV) who manufactures the driver for a solution. |
|
||||
|
||||
To change a driver’s upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** and then select the group of drivers you want to review. Select **Table** to view the list in a table.
|
||||
|
||||
2. Select **User changes** to enable user input.
|
||||
|
||||
3. Select the drivers you want to change to a specific upgrade decision and then select the appropriate option from the **Select upgrade decision** list.
|
||||
|
||||
4. Click **Save** when finished.
|
||||
|
||||
62
windows/deploy/upgrade-readiness-upgrade-overview.md
Normal file
62
windows/deploy/upgrade-readiness-upgrade-overview.md
Normal file
@ -0,0 +1,62 @@
|
||||
---
|
||||
title: Upgrade Readiness - Upgrade Overview (Windows 10)
|
||||
description: Displays the total count of computers sharing data and upgraded.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Upgrade Readiness - Upgrade overview
|
||||
|
||||
The first blade in the Upgrade Readiness solution is the upgrade overview blade. This blade displays the total count of computers sharing data with Microsoft, and the count of computers upgraded. As you successfully upgrade computers, the count of computers upgraded increases.
|
||||
|
||||
The upgrade overivew blade displays data refresh status, including the date and time of the most recent data update and whether user changes are reflected. The upgrade overview blade also displays the current target OS version. For more information about the target OS version, see [target version](use-upgrade-readiness-to-manage-windows-upgrades.md).
|
||||
|
||||
The following color-coded status changes are reflected on the upgrade overview blade:
|
||||
|
||||
- The "Last updated" banner:
|
||||
- No delay in processing device inventory data = "Last updated" banner is displayed in green.
|
||||
- Delay processing device inventory data = "Last updated" banner is displayed in amber.
|
||||
- Computers with incomplete data:
|
||||
- Less than 4% = Count is displayed in black.
|
||||
- 4% - 10% = Count is displayed in amber.
|
||||
- Greater than 10% = Count is displayed in red.
|
||||
- User changes:
|
||||
- Pending user changes = User changes count displays "Data refresh pending" in amber.
|
||||
- No pending user changes = User changes count displays "Up to date" in green.
|
||||
- Target version:
|
||||
- If the current value matches the recommended value, the version is displayed in green.
|
||||
- If the current value is an older OS version than the recommended value, but not deprecated, the version is displayed in amber.
|
||||
- If the current value is a deprecated OS version, the version is displayed in red.
|
||||
|
||||
In the following example, there is no delay in data processing, less than 4% of computers (6k\294k) have incomplete data, there are no pending user changes, and the currently selected target OS version is the same as the recommended version:
|
||||
|
||||
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image3.png" width="214" height="345" />
|
||||
-->
|
||||
|
||||
If data processing is delayed, you can continue using your workspace as normal. However, any changes or additional information that is added might not be displayed. Data is typically refreshed and the display will return to normal again within 24 hours.
|
||||
|
||||
If there are computers with incomplete data, verify that you have installed the latest compatibilty update and run the most recent [Update Readiness deployment script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the Microsoft download center.
|
||||
|
||||
Select **Total computers** for a list of computers and details about them, including:
|
||||
|
||||
- Computer ID and computer name
|
||||
- Computer manufacturer
|
||||
- Computer model
|
||||
- Operating system version and build
|
||||
- Count of system requirement, application, and driver issues per computer
|
||||
- Upgrade assessment based on analysis of computer telemetry data
|
||||
- Upgrade decision status
|
||||
|
||||
Select **Total applications** for a list of applications discovered on user computers and details about them, including:
|
||||
|
||||
- Application vendor
|
||||
- Application version
|
||||
- Count of computers the application is installed on
|
||||
- Count of computers that opened the application at least once in the past 30 days
|
||||
- Percentage of computers in your total computer inventory that opened the application in the past 30 days
|
||||
- Issues detected, if any
|
||||
- Upgrade assessment based on analysis of application data
|
||||
- Rollup level
|
||||
@ -1,52 +1,4 @@
|
||||
---
|
||||
title: Use Upgrade Analytics to manage Windows upgrades (Windows 10)
|
||||
description: Describes how to use Upgrade Analytics to manage Windows upgrades.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
redirect_url: use-upgrade-readiness-to-manage-windows-upgrades.md
|
||||
---
|
||||
|
||||
# Use Upgrade Analytics to manage Windows upgrades
|
||||
|
||||
You can use Upgrade Analytics to prioritize and work through application and driver issues, assign and track issue resolution status, and identify computers that are ready to upgrade. Upgrade Analytics enables you to deploy Windows with confidence, knowing that you’ve addressed potential blocking issues.
|
||||
|
||||
- Based on telemetry data from user computers, Upgrade Analytics identifies application and driver compatibility issues that may block Windows upgrades, allowing you to make data-driven decisions about your organization’s upgrade readiness.
|
||||
- Information is refreshed daily so you can monitor upgrade progress. Any changes your team makes, such as assigning application importance and marking applications as ready to upgrade, are reflected 24 hours after you make them.
|
||||
|
||||
When you are ready to begin the upgrade process, a workflow is provided to guide you through critical high-level tasks.
|
||||
|
||||
<A HREF="images/ua-cg-15.png"></A>
|
||||
|
||||
Each step in the workflow is enumerated using blue tiles. Helpful data is provided on white tiles to help you get started, to monitor your progress, and to complete each step.
|
||||
|
||||
>**Important**: You can use the [Target OS](#target-os) setting to evaluate computers that are runnign a specified version of Windows before starting the Upgrade Analytics workflow. By default, the Target OS is configured to the released version of Windows 10 for the Current Branch for Business (CBB).
|
||||
|
||||
The following information and workflow is provided:
|
||||
|
||||
- [Upgrade overview](upgrade-analytics-upgrade-overview.md): Review compatibility and usage information about computers, applications, and drivers.
|
||||
- [Step 1: Identify important apps](upgrade-analytics-identify-apps.md): Assign importance levels to prioritize your applications.
|
||||
- [Step 2: Resolve issues](upgrade-analytics-resolve-issues.md): Identify and resolve problems with applications.
|
||||
- [Step 3: Deploy](upgrade-analytics-deploy-windows.md): Start the upgrade process.
|
||||
|
||||
Also see the following topic for information about additional items that can be affected by the upgrade process:
|
||||
|
||||
- [Additional insights](upgrade-analytics-additional-insights.md): Find out which MS Office add-ins are installed, and review web site activity.
|
||||
|
||||
## Target OS
|
||||
|
||||
The target OS setting is used to evaluate the number of computers that are already running the default version of Windows 10, or a later version.
|
||||
|
||||
As mentioned previously, the default target OS in Upgrade Analytics is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target OS setting is used to evaluate the number of computers that are already running this version of Windows, or a later version.
|
||||
|
||||
The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target OS. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Analytics is based on the target OS version.
|
||||
|
||||
You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, and Windows version 1610.
|
||||
|
||||
To change the target OS setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Analytics solution:
|
||||
|
||||
|
||||
|
||||
>You must be signed in to Upgrade Analytics as an administrator to view settings.
|
||||
|
||||
On the **Upgrade Analytics Settings** page, choose one of the options in the drop down box and click **Save**. The changes in the target OS setting are reflected in evaluations when a new snapshot is uploaded to your workspace.
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
---
|
||||
title: Use Upgrade Readiness to manage Windows upgrades (Windows 10)
|
||||
description: Describes how to use Upgrade Readiness to manage Windows upgrades.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Use Upgrade Readiness to manage Windows upgrades
|
||||
|
||||
You can use Upgrade Readiness to prioritize and work through application and driver issues, assign and track issue resolution status, and identify computers that are ready to upgrade. Upgrade Readiness enables you to deploy Windows with confidence, knowing that you’ve addressed potential blocking issues.
|
||||
|
||||
- Based on telemetry data from user computers, Upgrade Readiness identifies application and driver compatibility issues that may block Windows upgrades, allowing you to make data-driven decisions about your organization’s upgrade readiness.
|
||||
- Information is refreshed daily so you can monitor upgrade progress. Any changes your team makes, such as assigning application importance and marking applications as ready to upgrade, are reflected 24 hours after you make them.
|
||||
|
||||
When you are ready to begin the upgrade process, a workflow is provided to guide you through critical high-level tasks.
|
||||
|
||||
<A HREF="images/ua-cg-15.png"></A>
|
||||
|
||||
Each step in the workflow is enumerated using blue tiles. Helpful data is provided on white tiles to help you get started, to monitor your progress, and to complete each step.
|
||||
|
||||
>**Important**: You can use the [Target version](#target-version) setting to evaluate computers that are runnign a specified version of Windows before starting the Upgrade Readiness workflow. By default, the Target version is configured to the released version of Windows 10 for the Current Branch for Business (CBB).
|
||||
|
||||
The following information and workflow is provided:
|
||||
|
||||
- [Upgrade overview](upgrade-readiness-upgrade-overview.md): Review compatibility and usage information about computers, applications, and drivers.
|
||||
- [Step 1: Identify important apps](upgrade-readiness-identify-apps.md): Assign importance levels to prioritize your applications.
|
||||
- [Step 2: Resolve issues](upgrade-readiness-resolve-issues.md): Identify and resolve problems with applications.
|
||||
- [Step 3: Deploy](upgrade-readiness-deploy-windows.md): Start the upgrade process.
|
||||
|
||||
Also see the following topic for information about additional items that can be affected by the upgrade process:
|
||||
|
||||
- [Additional insights](upgrade-readiness-additional-insights.md): Find out which MS Office add-ins are installed, and review web site activity.
|
||||
|
||||
## Target version
|
||||
|
||||
The target version setting is used to evaluate the number of computers that are already running the default version of Windows 10, or a later version. The target version of Windows 10 is displayed on the upgrade overview tile. See the following example:
|
||||
|
||||
|
||||
|
||||
As mentioned previously, the default target version in Upgrade Readiness is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version.
|
||||
|
||||
The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target version. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Readiness is based on the target operating system version.
|
||||
|
||||
You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, and Windows version 1610.
|
||||
|
||||
To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution:
|
||||
|
||||
|
||||
|
||||
>You must be signed in to Upgrade Readiness as an administrator to view settings.
|
||||
|
||||
On the **Upgrade Readiness Settings** page, choose one of the options in the drop down box and click **Save**. The changes in the target version setting are reflected in evaluations when a new snapshot is uploaded to your workspace.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user