mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-8094158
This commit is contained in:
LizRoss
commit
2e8b4acb48
@ -1,4 +1,14 @@
|
||||
# [Deploy Windows 10](index.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)
|
||||
### [Use Upgrade Analytics to manage Windows upgrades](use-upgrade-analytics-to-manage-windows-upgrades.md)
|
||||
#### [Prepare your environment](upgrade-analytics-prepare-your-environment.md)
|
||||
#### [Resolve application and driver issues](upgrade-analytics-resolve-issues.md)
|
||||
#### [Deploy Windows](upgrade-analytics-deploy-windows.md)
|
||||
### [Troubleshoot Upgrade Analytics](troubleshoot-upgrade-analytics.md)
|
||||
## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
## [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
### [Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)
|
||||
|
||||
@ -9,9 +9,9 @@ author: MaggiePucciEvans
|
||||
|
||||
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.
|
||||
|
||||
Microsoft developed Upgrade Analytics in response to the 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 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.
|
||||
|
||||
Enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly.
|
||||
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.
|
||||
|
||||
@ -33,5 +33,25 @@ Use Upgrade Analytics to get:
|
||||
|
||||
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 data is collected from user computers, see [Windows 7-8.1 Telemetry Events and Fields Descriptions](http://go.microsoft.com/fwlink/?LinkId=822965).
|
||||
**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](http://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
##**Related topics**
|
||||
|
||||
[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)
|
||||
|
||||
[Use Upgrade Analytics to manage Windows upgrades](use-upgrade-analytics-to-manage-windows-upgrades.md)
|
||||
|
||||
[Troubleshoot Upgrade Analytics](troubleshoot-upgrade-analytics.md)
|
||||
|
||||
|
||||
@ -7,11 +7,13 @@ author: MaggiePucciEvans
|
||||
|
||||
# Troubleshoot Upgrade Analytics
|
||||
|
||||
If you’re having issues seeing data in Upgrade Analytics after running the script, enable verbose mode in the Upgrade Analytics Deployment script to turn on a more comprehensive mode of logging. To enable:
|
||||
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 [Run the Upgrade Analytics deployment script](#_Run_the_Upgrade).
|
||||
2. Edit the script as described in [Run the Upgrade Analytics deployment script](upgrade-analytics-get-started.md#run-the-upgrade-analytics-deployment-script).
|
||||
|
||||
3. Check that isVerboseLogging is set to $true.
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ author: MaggiePucciEvans
|
||||
|
||||
# Upgrade Analytics architecture
|
||||
|
||||
The diagram below illustrates how Upgrade Analytics components work together in a typical installation. After you enable Windows telemetry on user computers and install the Compatibility Update (1), user computers send system, application and driver data to a Microsoft telemetry data repository (2). Once you configure Upgrade Analytics, telemetry data is queried from the repository, analyzed by the Upgrade Analytics Service (3) and pushed into your OMS workspace (4). You can then use the Upgrade Analytics solution (5) to determine your organization’s upgrade readiness.
|
||||
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" />
|
||||
@ -15,3 +15,20 @@ The diagram below illustrates how Upgrade Analytics components work together in
|
||||
|
||||
|
||||
|
||||
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)
|
||||
|
||||
[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](http://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
##**Related topics**
|
||||
|
||||
[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)
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
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 upgrade ready by using Upgrade Analytics.
|
||||
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: MaggiePucciEvans
|
||||
---
|
||||
|
||||
# Upgrade Analytics: Get a list of computers that are upgrade ready
|
||||
# Upgrade Analytics - Get a list of computers that are upgrade ready
|
||||
|
||||
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.
|
||||
|
||||
@ -23,4 +23,4 @@ Computers grouped by deployment decision are listed.
|
||||
|
||||
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: 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.
|
||||
>**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.
|
||||
|
||||
@ -7,11 +7,18 @@ author: MaggiePucciEvans
|
||||
|
||||
# Get started with Upgrade Analytics
|
||||
|
||||
Use Upgrade Analytics to plan and manage your upgrade project end to end. After you’ve established communications between Upgrade Analytics and users’ computers, the solution collects computer, application, and driver data for analysis. We use this data to identify compatibility issues that can block your upgrade, and suggest fixes that are known to Microsoft.
|
||||
Use Upgrade Analytics to plan and manage your upgrade project end to end. After you’ve established communications between user computers and Microsoft, Upgrade Analytics collects computer, application, and driver data for analysis. We use this data to identify compatibility issues that can block your upgrade and suggest fixes that are known to Microsoft.
|
||||
|
||||
For more information about what user computer data Microsoft collects and assesses, see [Windows 7-8.1 Telemetry Events and Fields Descriptions](http://go.microsoft.com/fwlink/?LinkId=822965). For information about how Microsoft uses telemetry data, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
|
||||
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:
|
||||
|
||||
This topic explains how to obtain and set up Upgrade Analytics components. If you haven’t done so already, see [Upgrade Analytics requirements](upgrade-analytics-requirements.md) for information about requirements for using Upgrade Analytics.
|
||||
- [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](http://go.microsoft.com/fwlink/?LinkID=822965)
|
||||
|
||||
|
||||
This topic explains how to obtain and set up Upgrade Analytics components. If you haven’t done so already, see [Upgrade Analytics requirements](https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-requirements) for information about requirements for using Upgrade Analytics.
|
||||
|
||||
To configure Upgrade Analytics, you’ll need to:
|
||||
|
||||
@ -21,15 +28,16 @@ To configure Upgrade Analytics, you’ll need to:
|
||||
|
||||
Each task is explained in detail in the following sections.
|
||||
|
||||
|
||||
## 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-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
||||
Upgrade Analytics is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud based services for managing your on-premise 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 page. Upgrade Analytics is now visible in your workspace.
|
||||
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 \[link to new Upgrade Analytics Web page on Microsoft.com\] and select the **Upgrade Analytics Service** link to kick off the onboarding process.
|
||||
1. Go to the [Upgrade Analytics website](http://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.
|
||||
|
||||
@ -37,11 +45,11 @@ If you are not using OMS:
|
||||
|
||||
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.
|
||||
> 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 Overview portal. Note that you may need to scroll to find Upgrade Analytics.
|
||||
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.
|
||||
2. Click the **Upgrade Analytics** tile to configure the solution. The **Settings Dashboard** opens.
|
||||
|
||||
## Enable data sharing between your organization and Upgrade Analytics
|
||||
|
||||
@ -51,25 +59,19 @@ After you’ve signed in to Operations Management Suite and added the Upgrade An
|
||||
|
||||
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**.
|
||||
1. On the Settings Dashboard, navigate to the **Windows telemetry** panel.
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
|
||||
<img src="media/image2.png" width="245" height="291" />
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
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: 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 users’ computers again.
|
||||
>**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 data 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. 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.
|
||||
|
||||
@ -129,35 +131,31 @@ The Upgrade Analytics deployment script does the following:
|
||||
|
||||
To run the Upgrade Analytics deployment script:
|
||||
|
||||
1. Download and extract UpgradeAnalytics.zip .
|
||||
1. Download the [Upgrade Analytics deployment script](http://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and extract UpgradeAnalytics.zip. The files in the Diagnostics folder are necessary only if you plan to run the script in troubleshooting mode.
|
||||
|
||||
> NOTE: The files in the Diagnostics folder are necessary only if you plan to run the script in troubleshooting mode.
|
||||
|
||||
1. Edit the following parameters in RunConfig.bat:
|
||||
2. Edit the following parameters in RunConfig.bat:
|
||||
|
||||
1. Provide a storage location for log information. Example: %SystemDrive%\\UADiagnostics
|
||||
|
||||
2. 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 it in the drive with the Windows directory.
|
||||
2. 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.
|
||||
|
||||
3. Input your commercial ID key.
|
||||
|
||||
4. 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 = 0 log to console only*
|
||||
>
|
||||
> *logMode = 1 log to file and console*
|
||||
> *logMode = 1 log to file and console*
|
||||
>
|
||||
> *logMode = 2 log to file only*
|
||||
> *logMode = 2 log to file only*
|
||||
|
||||
1. For troubleshooting, set isVerboseLogging to $true to generate log information that can help with diagnosing issues. By default, isVerboseLogging is set to $false. Ensure the Diagnostics folder is installed in the same directory as the script to use this mode.
|
||||
3. For troubleshooting, set isVerboseLogging to $true to generate log information that can help with diagnosing issues. By default, isVerboseLogging is set to $false. Ensure the Diagnostics folder is installed in the same directory as the script to use this mode.
|
||||
|
||||
2. Notify users if they need to restart their computers. By default, this is set to off.
|
||||
4. Notify users if they need to restart their computers. By default, this is set to off.
|
||||
|
||||
<!-- -->
|
||||
|
||||
1. After you finish editing the parameters in RunConfig.bat, run the script as an administrator.
|
||||
5. After you finish editing the parameters in RunConfig.bat, run the script as an administrator.
|
||||
|
||||
## Seeing data from computers in Upgrade Analytics
|
||||
|
||||
After data is sent from computers to Microsoft, it generally takes 48 hours for the data to populate in Upgrade Analytics. The inventory collection KB takes several minutes to run – if the component 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, it’s fair to expect a majority of your computers to be populated in OMS in about 1-2 weeks after deploying the KB and configuration to all of your computers in your enterprise.
|
||||
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.
|
||||
|
||||
|
||||
@ -1,19 +1,19 @@
|
||||
---
|
||||
title: Upgrade Analytics: Prepare your environment (Windows 10)
|
||||
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
|
||||
# Upgrade Analytics - Prepare your environment
|
||||
|
||||
This section of the 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.
|
||||
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 sending data to Upgrade Analytics and the count of computers upgraded. As you successfully upgrade computers, the count of computers upgraded increases.
|
||||
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.
|
||||
|
||||
@ -25,7 +25,7 @@ Check this blade for data refresh status, including the date and time of the mos
|
||||
|
||||
Select **Total computers** for a list of computers and details about them, including:
|
||||
|
||||
- Computer ID or computer name
|
||||
- Computer ID and computer name
|
||||
|
||||
- Computer manufacturer
|
||||
|
||||
@ -47,18 +47,14 @@ Select **Total applications** for a list of applications discovered on user comp
|
||||
|
||||
- Count of computers the application is installed on
|
||||
|
||||
- Count of number of computers that opened the application at least once in the past 30 days
|
||||
- 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
|
||||
|
||||
- Importance level (click **User changes** to change)
|
||||
|
||||
- Upgrade decision (click **User changes** to change)
|
||||
|
||||
|
||||
- Roll up level
|
||||
|
||||
## Run a pilot
|
||||
@ -81,9 +77,9 @@ Before you start your pilot project, be sure to review upgrade assessment and gu
|
||||
|
||||
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.
|
||||
|
||||
NOTE: There is a known issue where the maximum number of exported rows must be less than or equal to 5,000.
|
||||
>**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/en-us/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.
|
||||
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
|
||||
|
||||
|
||||
@ -9,11 +9,11 @@ author: MaggiePucciEvans
|
||||
|
||||
## Supported versions of Windows
|
||||
|
||||
The compatibility update KB that sends data from user computers to Upgrade Analytics works only with Windows 7 SP1 and Windows 8.1. Upgrade Analytics cannot evaluate Windows XP or Windows Vista for upgrade eligibility.
|
||||
The compatibility update KB that sends telemetry data from user computers to Upgrade Analytics works only with Windows 7 SP1 and Windows 8.1. Upgrade Analytics cannot evaluate Windows XP or Windows Vista for upgrade eligibility.
|
||||
|
||||
With Windows 10 edition 1607, the compatibility update KB is installed automatically.
|
||||
<!--With Windows 10, edition 1607, the compatibility update KB is installed automatically.-->
|
||||
|
||||
## Telemetry
|
||||
## User authenticated proxies not supported in this release
|
||||
|
||||
User computers communicate with Upgrade Analytics 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.
|
||||
|
||||
@ -27,7 +27,7 @@ Windows telemetry data from user computers is encrypted, sent to, and processed
|
||||
|
||||
## Known issues
|
||||
|
||||
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.
|
||||
- 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.
|
||||
|
||||
Clicking a column heading a client-side sort. Which means it basically only sorts what’s currently displayed…kind of (it actually does what’s shown + a little more but not the complete query result, not really sure if this is the intended behavior but currently investigating). The bottom line is, if they want sort to work as they expect, they need to write a new query, something like | sort TotalInstalls desc. So I’d recommend removing this line for now.
|
||||
- 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).
|
||||
|
||||
|
||||
@ -7,11 +7,7 @@ author: MaggiePucciEvans
|
||||
|
||||
# Upgrade Analytics requirements
|
||||
|
||||
Prior to installing the Upgrade Analytics solution, review the following requirements and recommendations for using the solution to simplify and accelerate your Windows upgrade.
|
||||
|
||||
This article introduces the 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.
|
||||
|
||||
See *Get started with Upgrade Analytics* for detailed, step-by-step instructions for configuring Upgrade Analytics and getting started on your Windows upgrade project.
|
||||
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
|
||||
|
||||
@ -61,9 +57,11 @@ NOTE: The compatibility update KB runs under the computer’s system account and
|
||||
|
||||
**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.
|
||||
|
||||
**Configure and deploy Upgrade Analytics deployment script.** Configure and deploy the Upgrade Analytics deployment script to user computers to finish setting up.
|
||||
|
||||
**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: The compatibility update and related KBs are frequently updated 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 scans computers only when it is updated and does not scan computers on a schedule, although an option to kick off the scan manually is available.
|
||||
>**Important**<br> The compatibility update and related KBs are frequently updated 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.
|
||||
|
||||
See [Get started with Upgrade Analytics](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-analytics-get-started
|
||||
) for detailed, step-by-step instructions for configuring Upgrade Analytics and getting started on your Windows upgrade project.
|
||||
|
||||
@ -1,17 +1,15 @@
|
||||
---
|
||||
title: Upgrade Analytics: Resolve application and driver issues (Windows 10)
|
||||
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: MaggiePucciEvans
|
||||
---
|
||||
|
||||
# Upgrade Analytics: Resolve application and driver issues
|
||||
# Upgrade Analytics - Resolve application 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. Select **Decide upgrade readiness** at the bottom of each blade to change available values.
|
||||
|
||||
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.
|
||||
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:
|
||||
|
||||
@ -34,7 +32,17 @@ Applications with issues known to Microsoft are listed, grouped by upgrade asses
|
||||
|
||||
|
||||
|
||||
Select **Decide upgrade readiness** to view all applications with issues. In the table view, sort on **UpgradeAssessment** to group applications into **Attention needed** and **Fix available**. Select **User changes** to change the upgrade decision for each application.
|
||||
To change an application's upgrade decision:
|
||||
|
||||
1. Select **Decide upgrade readiness** to view applications with issues.
|
||||
|
||||
2. In the table view, sort on **UpgradeAssessment** to group applications into **Attention needed** and **Fix available**.
|
||||
|
||||
3. Select **User changes** 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.
|
||||
|
||||
@ -48,7 +56,7 @@ For applications assessed as **Attention needed**, review the table below for de
|
||||
| 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 | <br><br>Different versions of the application have different issues <br><br>\[Make a note here about making sure the inventory scanner is up to date\] or a version of the application has more than one issue affecting its upgrade-readiness. | 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.<br><br>Can also be because data hasn’t been refreshed yet and is still showing computers with old KB installed.<br><br>Think about how to or whether to include more details about why there would be “multiple” |
|
||||
| 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.
|
||||
|
||||
@ -71,7 +79,17 @@ Applications with no issues known to Microsoft are listed, grouped by upgrade de
|
||||
|
||||
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. Change the importance level and upgrade decision by selecting **User input**. Select the applications you want to change to a specific importance level and then select the appropriate option from the **Select importance level** list. Select the applications you want to change to a specific upgrade readiness status and then select the appropriate option from the **Select upgrade decision** list.
|
||||
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
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user