mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
draft
This commit is contained in:
Greg Lindsay
40
windows/deploy/upgrade-analytics-identify-apps.md
Normal file
40
windows/deploy/upgrade-analytics-identify-apps.md
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
# 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. Select **Table** to view the list in a table.
|
||||
|
||||
2. Select **User changes** to enable user input.
|
||||
|
||||
3. Select the applications you want to change to a specific importance level and then select the appropriate option from the **Select importance level** list.
|
||||
|
||||
4. 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,116 +1,4 @@
|
||||
---
|
||||
title: Upgrade Analytics - Prepare your environment (Windows 10)
|
||||
description: Describes how to prepare your environment so that you can use Upgrade Analytics to manage Windows upgrades.
|
||||
ms.prod: w10
|
||||
author: MaggiePucciEvans
|
||||
---
|
||||
|
||||
# Upgrade Analytics - Prepare your environment
|
||||
|
||||
This section of the Upgrade Analytics workflow reports your computer and application inventory and lists computers that you can use in a pilot with no known issues or with fixable driver issues. Additionally, you can determine the priority level of applications to indicate which applications the team should focus on to get them upgrade ready.
|
||||
|
||||
The blades in the **Prepare your environment** section are:
|
||||
|
||||
## Upgrade overview
|
||||
|
||||
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.
|
||||
|
||||
Check this blade for data refresh status, including the date and time of the most recent data update and whether user changes are reflected. If a user change is pending when changing the upgrade assessment or importance level of an application or driver, **Data refresh pending** is displayed in orange. User changes are processed once every 24 hours and read **Up to date** in green when there are no pending changes.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image3.png" width="214" height="345" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
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
|
||||
|
||||
- Roll up level
|
||||
|
||||
## Run a pilot
|
||||
|
||||
Computers with no known issues and computers with fixable driver issues are listed, grouped by upgrade assessment. We recommend that you use these computers to test the impact of upgrading.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image4.png" width="203" height="326" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
Before you start your pilot project, be sure to review upgrade assessment and guidance details, explained in more detail in the table below.
|
||||
|
||||
| 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.
|
||||
|
||||
See [Plan for Windows 10 deployment](http://technet.microsoft.com/itpro/windows/plan/index) for more information about ways to deploy Windows in your organization. Read about [how Microsoft IT deployed Windows as an in-place upgrade](https://www.microsoft.com/itshowcase/Article/Content/668/Deploying-Windows-10-at-Microsoft-as-an-inplace-upgrade) for best practices using the in-place upgrade method.
|
||||
|
||||
## Prioritize applications
|
||||
|
||||
Applications are listed, grouped by importance level. Prioritizing your applications allows you to identify the ones that you will focus on preparing 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. Select **Table** to view the list in a table.
|
||||
|
||||
2. Select **User changes** to enable user input.
|
||||
|
||||
3. Select the applications you want to change to a specific importance level and then select the appropriate option from the **Select importance level** list.
|
||||
|
||||
4. 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. <br><br> |
|
||||
| Not reviewed | Applications that are installed on more than 2% of your total computer inventory are marked not reviewed until you change the importance level.<br><br>These applications are also marked as **Not reviewed** in the **UpgradeDecision** column. <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.<br><br>You may also want to change the application’s status to **Not reviewed** or **Ready to upgrade** in the **UpgradeDecision** column. <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> |
|
||||
|
||||
title: Upgrade Analytics - Identify important apps (Windows 10)
|
||||
redirect_url: upgrade-analytics-identify-apps
|
||||
---
|
||||
52
windows/deploy/upgrade-analytics-upgrade-overview.md
Normal file
52
windows/deploy/upgrade-analytics-upgrade-overview.md
Normal file
@ -0,0 +1,52 @@
|
||||
---
|
||||
title: Upgrade Analytics - Upgrade Overview (Windows 10)
|
||||
description: Displays the total count of computers sharing data and upgraded.
|
||||
ms.prod: w10
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# 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.
|
||||
|
||||
Check this blade for data refresh status, including the date and time of the most recent data update and whether user changes are reflected. If a user change is pending when changing the upgrade assessment or importance level of an application or driver, **Data refresh pending** is displayed in orange. User changes are processed once every 24 hours and read **Up to date** in green when there are no pending changes.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image3.png" width="214" height="345" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
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
|
||||
|
||||
- Roll up level
|
||||
@ -15,14 +15,15 @@ You and your IT team can use the Upgrade Analytics workflow to prioritize and wo
|
||||
|
||||
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.
|
||||
|
||||
The Upgrade Analytics workflow gives you compatibility and usage information about computers, applications, and drivers and walks you through these high-level tasks. Each task is described in more detail in the topics that follow.
|
||||
The Upgrade Analytics solution provides compatibility and usage information about computers, applications, and drivers. A workflow is also provided to walk you through the high-level tasks required during the upgrade process. See the following topics for more information:
|
||||
|
||||
1. [Preparing your environment](upgrade-analytics-prepare-your-environment.md)
|
||||
- [Upgrade overview](upgrade-analytics-upgrade-overview.md)
|
||||
|
||||
2. [Resolving application and driver issues](upgrade-analytics-resolve-issues.md)
|
||||
- Upgrade Analytics workflow:
|
||||
- [Step 1: Identify important apps](upgrade-analytics-identify-apps.md)
|
||||
- [Step 2: Resolve issues](upgrade-analytics-resolve-issues.md)
|
||||
- [Step 3: Deploy](upgrade-analytics-deploy-windows.md)
|
||||
|
||||
3. [Identifying computers that are upgrade ready](upgrade-analytics-deploy-windows.md)
|
||||
|
||||
4. [Additional insights](upgrade-analytics-additional-insights.md)
|
||||
- [Additional insights](upgrade-analytics-additional-insights.md)
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user