From b7c8547298ae3cb07adef7a69c9299dd8d562934 Mon Sep 17 00:00:00 2001 From: Nicola Dolci Date: Mon, 25 Jul 2016 20:06:53 -0700 Subject: [PATCH 1/5] Delete localization.config The config now lives in the handback repo at https://github.com/Microsoft/win-cpub-itpro-docs.handback/blob/master/ol-config/Microsoft/win-cpub-itpro-docs/master/.localization-config. This allows support to get to it as needed. This config was incorrect --- .localization-config | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 .localization-config diff --git a/.localization-config b/.localization-config deleted file mode 100644 index 148efa2f39..0000000000 --- a/.localization-config +++ /dev/null @@ -1,21 +0,0 @@ -{ - - "filters": [ - - { - "metadata": { - "localizationpriority": [ "high" ] - } - } -], - - "locales": [ "ja-jp", "de-de", "fr-fr", "zh-cn", "zh-tw", "ko-kr", "es-es", "it-it", "ru-ru", "pt-br" ], - "files": ["!/*.md", "**/**/*.md", "**/*.md"], - "includeDependencies": true, - "autoPush": true, - "xliffVersion": "2.0", - "useJavascriptMarkdownTransformer": true, - "markdownTransformerOptions": { - "lockBackslashEscapeChars": false - } -} From e31305adc0615de2bda8062b4b12a95e34c131d4 Mon Sep 17 00:00:00 2001 From: Maggie Evans Date: Tue, 26 Jul 2016 09:20:38 -0700 Subject: [PATCH 2/5] Redirect Release Notes topic to Requirements topic Moved release notes content to Requirements topic. Added redirect in Release notes topic to Requirements topic. --- .../deploy/upgrade-analytics-release-notes.md | 34 ++----------------- .../deploy/upgrade-analytics-requirements.md | 29 +++++++++++++--- 2 files changed, 28 insertions(+), 35 deletions(-) diff --git a/windows/deploy/upgrade-analytics-release-notes.md b/windows/deploy/upgrade-analytics-release-notes.md index 45ead2b529..dd1959b0e1 100644 --- a/windows/deploy/upgrade-analytics-release-notes.md +++ b/windows/deploy/upgrade-analytics-release-notes.md @@ -1,33 +1,5 @@ --- title: Upgrade Analytics release notes (Windows 10) -description: Provides release notes for Upgrade Analytics. -ms.prod: w10 -author: MaggiePucciEvans ---- - -# Upgrade Analytics release notes - -## Supported versions of Windows - -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. - - - -## 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. - -## Upgrade Analytics does not support on-premise 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-premise. - -## 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’ll be frequently adding support for additional regions and we’ll update this information when new international regions are supported. - -## 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. - -- 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). - +description: Provides tips and limitations about Upgrade Analytics. +redirect_url: https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-requirements +--- \ No newline at end of file diff --git a/windows/deploy/upgrade-analytics-requirements.md b/windows/deploy/upgrade-analytics-requirements.md index 6cb93e90c5..58fb28d579 100644 --- a/windows/deploy/upgrade-analytics-requirements.md +++ b/windows/deploy/upgrade-analytics-requirements.md @@ -13,6 +13,10 @@ This article introduces concepts and steps needed to get up and running with Upg 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. + + + 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. @@ -49,7 +53,7 @@ See \[link to Steve May’s PDF doc when it’s published\] for more information `https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc/extended` -NOTE: The compatibility update KB runs under the computer’s system account and does not support user authentication in this release. +>**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. @@ -59,9 +63,26 @@ NOTE: The compatibility update KB runs under the computer’s system account and **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 collects inventory information from computers only when it is updated. +>**Important**
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. -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. +## 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-premise 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-premise. + +**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. From 8ddce6422067f21f7a05de0bef51fed6f21ad5db Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Tue, 26 Jul 2016 12:40:30 -0700 Subject: [PATCH 3/5] adding section on Upgrade Analytics --- .../configure-windows-telemetry-in-your-organization.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/manage/configure-windows-telemetry-in-your-organization.md b/windows/manage/configure-windows-telemetry-in-your-organization.md index db19b958a4..9bee3c8163 100644 --- a/windows/manage/configure-windows-telemetry-in-your-organization.md +++ b/windows/manage/configure-windows-telemetry-in-your-organization.md @@ -94,10 +94,10 @@ Windows telemetry also helps Microsoft better understand how customers use (or d **These examples show how the use of telemetry data enables Microsoft to build or enhance features which can help organizations increase employee productivity while lowering help desk calls.** - ## How is telemetry data handled by Microsoft? ### Data collection @@ -180,7 +179,8 @@ The levels are cumulative and are illustrated in the following diagram. Also, th The Security level gathers only the telemetry info that is required to keep Windows devices, Windows Server, and guests protected with the latest security updates. This level is only available on Windows Server 2016, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, and Windos IoT Core editions. -> **Note:**  If your organization relies on Windows Update for updates, you shouldn’t use the **Security** level. Because no Windows Update information is gathered at this level, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates. +> ![NOTE] +> If your organization relies on Windows Update for updates, you shouldn’t use the **Security** level. Because no Windows Update information is gathered at this level, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates. Windows Server Update Services (WSUS) and System Center Configuration Manager functionality is not affected at this level, nor is telemetry data about Windows Server features or System Center gathered. From 6dc4e2fa89c73cb468386e44733817a02afbfe57 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Tue, 26 Jul 2016 13:24:28 -0700 Subject: [PATCH 4/5] fixed note style --- .../manage/configure-windows-telemetry-in-your-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/configure-windows-telemetry-in-your-organization.md b/windows/manage/configure-windows-telemetry-in-your-organization.md index 9bee3c8163..f96de676a4 100644 --- a/windows/manage/configure-windows-telemetry-in-your-organization.md +++ b/windows/manage/configure-windows-telemetry-in-your-organization.md @@ -179,7 +179,7 @@ The levels are cumulative and are illustrated in the following diagram. Also, th The Security level gathers only the telemetry info that is required to keep Windows devices, Windows Server, and guests protected with the latest security updates. This level is only available on Windows Server 2016, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, and Windos IoT Core editions. -> ![NOTE] +> [!NOTE] > If your organization relies on Windows Update for updates, you shouldn’t use the **Security** level. Because no Windows Update information is gathered at this level, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates. Windows Server Update Services (WSUS) and System Center Configuration Manager functionality is not affected at this level, nor is telemetry data about Windows Server features or System Center gathered. From c91ad87170e9f276e68f742f862f396f6041b74c Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Tue, 26 Jul 2016 13:34:13 -0700 Subject: [PATCH 5/5] fixing note --- .../manage/configure-windows-telemetry-in-your-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/configure-windows-telemetry-in-your-organization.md b/windows/manage/configure-windows-telemetry-in-your-organization.md index f96de676a4..2e71148479 100644 --- a/windows/manage/configure-windows-telemetry-in-your-organization.md +++ b/windows/manage/configure-windows-telemetry-in-your-organization.md @@ -179,7 +179,7 @@ The levels are cumulative and are illustrated in the following diagram. Also, th The Security level gathers only the telemetry info that is required to keep Windows devices, Windows Server, and guests protected with the latest security updates. This level is only available on Windows Server 2016, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, and Windos IoT Core editions. -> [!NOTE] +> [!NOTE] > If your organization relies on Windows Update for updates, you shouldn’t use the **Security** level. Because no Windows Update information is gathered at this level, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates. Windows Server Update Services (WSUS) and System Center Configuration Manager functionality is not affected at this level, nor is telemetry data about Windows Server features or System Center gathered.