From e0264bde6ef88635d9c32a40850b6d2f9b3a2cf6 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 12:59:00 -0700 Subject: [PATCH 01/22] fixing link issues, reformatting table --- windows/deployment/TOC.md | 1 - ...windows-upgrades-with-upgrade-readiness.md | 6 ++-- .../upgrade/upgrade-readiness-architecture.md | 6 ++-- .../upgrade-readiness-deployment-script.md | 29 +++++++------------ .../upgrade/upgrade-readiness-get-started.md | 6 ++-- .../upgrade/upgrade-readiness-requirements.md | 4 +-- 6 files changed, 22 insertions(+), 30 deletions(-) diff --git a/windows/deployment/TOC.md b/windows/deployment/TOC.md index 33c1697c0f..73fce9589a 100644 --- a/windows/deployment/TOC.md +++ b/windows/deployment/TOC.md @@ -46,7 +46,6 @@ ### [Manage Windows upgrades with Upgrade Readiness](upgrade/manage-windows-upgrades-with-upgrade-readiness.md) #### [Upgrade Readiness architecture](upgrade/upgrade-readiness-architecture.md) #### [Upgrade Readiness requirements](upgrade/upgrade-readiness-requirements.md) -#### [Upgrade Readiness release notes](upgrade/upgrade-readiness-release-notes.md) #### [Get started with Upgrade Readiness](upgrade/upgrade-readiness-get-started.md) ##### [Upgrade Readiness deployment script](upgrade/upgrade-readiness-deployment-script.md) #### [Use Upgrade Readiness to manage Windows upgrades](upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) diff --git a/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md b/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md index de269889bf..c2744bd544 100644 --- a/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md +++ b/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md @@ -29,15 +29,15 @@ The Upgrade Readiness workflow steps you through the discovery and rationalizati **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) +- [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization) +- [Manage connections from Windows operating system components to Microsoft services](/windows/configuration/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)
[Upgrade Readiness requirements](upgrade-readiness-requirements.md)
-[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
+[Upgrade Readiness release notes](upgrade-readiness-requirements.md#important-information-about-this-release)
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)
[Use Upgrade Readiness to manage Windows upgrades](use-upgrade-readiness-to-manage-windows-upgrades.md)
[Troubleshoot Upgrade Readiness](troubleshoot-upgrade-readiness.md)
diff --git a/windows/deployment/upgrade/upgrade-readiness-architecture.md b/windows/deployment/upgrade/upgrade-readiness-architecture.md index 6bc7492d37..ae5949405f 100644 --- a/windows/deployment/upgrade/upgrade-readiness-architecture.md +++ b/windows/deployment/upgrade/upgrade-readiness-architecture.md @@ -19,12 +19,12 @@ After you enable Windows telemetry on user computers and install the compatibili 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)
+[Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization)
+[Manage connections from Windows operating system components to Microsoft services](/windows/configuration/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 requirements](upgrade-readiness-requirements.md)
-[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
+[Upgrade Readiness release notes](upgrade-readiness-requirements.md#important-information-about-this-release)
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)
diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 43870037ce..b3dcdf790a 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,11 +70,11 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. -
+ - +
Exit code
Exit code Meaning Suggested fix @@ -105,7 +105,7 @@ The deployment script displays the following exit codes to let you know if it wa
6 The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value. 		The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace. -
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. +
See [Generate your Commercial ID key](upgrade-readiness-get-started.md#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace.
8 Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
@@ -130,21 +130,21 @@ The deployment script displays the following exit codes to let you know if it wa 		**Http Get** on the end points did not return a success exit code.
For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive. -
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). +
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](upgrade-readiness-get-started.md#enable-data-sharing).
13 Can’t connect to Microsoft - setting. -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). +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](upgrade-readiness-get-started.md#enable-data-sharing).
14 Can’t connect to Microsoft - compatexchange. -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). +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](upgrade-readiness-get-started.md#enable-data-sharing).
15 Function CheckVortexConnectivity failed with an unexpected exception. -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. +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](upgrade-readiness-get-started.md#enable-data-sharing). Check the logs for the exception message and the HResult.
16 The computer requires a reboot before running the script. @@ -156,7 +156,7 @@ For previous operating systems, connectivity is verified by connecting to https:
18 Appraiser KBs not installed or **appraiser.dll** not found. -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. +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](upgrade-readiness-get-started.md#data-collection-and-privacy) and privacy topic.
19 Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception. @@ -217,7 +217,7 @@ For previous operating systems, connectivity is verified by connecting to https:
32 Appraiser version on the machine is outdated. -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. +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](upgrade-readiness-get-started.md#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1.
33 **CompatTelRunner.exe** exited with an exit code @@ -246,7 +246,7 @@ For previous operating systems, connectivity is verified by connecting to https:
39 For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
-		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). +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](/windows/configuration/configure-windows-telemetry-in-your-organization).
40 Function **CheckTelemetryOptIn** failed with an unexpected exception. @@ -284,11 +284,4 @@ or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersio
The **CommercialID** referenced in RunConfig.bat must be a GUID. The **CommercialID** that is entered in RunConfig.bat must be a GUID. Copy the commercial ID from your workspace. To find the commercialID on the OMS portal, view Upgrade Readiness > Settings. You will find the commercial ID on the settings page. -
- -
- - - - - + \ No newline at end of file diff --git a/windows/deployment/upgrade/upgrade-readiness-get-started.md b/windows/deployment/upgrade/upgrade-readiness-get-started.md index 102fb76463..bb6ce8f949 100644 --- a/windows/deployment/upgrade/upgrade-readiness-get-started.md +++ b/windows/deployment/upgrade/upgrade-readiness-get-started.md @@ -32,8 +32,8 @@ When you are ready to begin using Upgrade Readiness, perform the following steps 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) +- [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization) +- [Manage connections from Windows operating system components to Microsoft services](/windows/configuration/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 @@ -113,7 +113,7 @@ If you are planning to enable IE Site Discovery, you will need to install a few | **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)
Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices.
For more information about this KB, see

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. | +| [Review site discovery](upgrade-readiness-additional-insights.md#site-discovery) | [KB3080149](http://www.catalog.update.microsoft.com/Search.aspx?q=3080149)
Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices.
For more information about this KB, see

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 diff --git a/windows/deployment/upgrade/upgrade-readiness-requirements.md b/windows/deployment/upgrade/upgrade-readiness-requirements.md index 5593a4eb72..5643e2df81 100644 --- a/windows/deployment/upgrade/upgrade-readiness-requirements.md +++ b/windows/deployment/upgrade/upgrade-readiness-requirements.md @@ -30,7 +30,7 @@ See [Windows 10 Specifications](http://www.microsoft.com/en-US/windows/windows-1 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. +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](../update/waas-overview.md#long-term-servicing-branch) to understand more about LTSB. ## Operations Management Suite @@ -50,7 +50,7 @@ Upgrade Readiness can be integrated with your installation of Configuration Mana 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. +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](windows/configuration/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. From 8418877c9bca12240b51161885bbeb198c966fff Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:10:17 -0700 Subject: [PATCH 02/22] fixing table width --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- windows/deployment/upgrade/upgrade-readiness-requirements.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index b3dcdf790a..e44324588d 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
- - + - + - + @@ -180,7 +180,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +200,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -305,15 +305,3 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code Meaning diff --git a/windows/deployment/upgrade/upgrade-readiness-requirements.md b/windows/deployment/upgrade/upgrade-readiness-requirements.md index 5643e2df81..eb98ebd2cf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-requirements.md +++ b/windows/deployment/upgrade/upgrade-readiness-requirements.md @@ -50,7 +50,7 @@ Upgrade Readiness can be integrated with your installation of Configuration Mana 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](windows/configuration/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data. +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](/windows/configuration/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. From 775f74f6a25be6263068e8542f6756e7061fa831 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:21:44 -0700 Subject: [PATCH 03/22] table formatting --- .../upgrade/upgrade-readiness-deployment-script.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index e44324588d..cb0b03011c 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -74,9 +74,9 @@ The deployment script displays the following exit codes to let you know if it wa - - + + - + @@ -304,4 +304,16 @@ The deployment script displays the following exit codes to let you know if it wa
Exit codeMeaning -Suggested fix +
Exit codeMeaningSuggested fix
0 Success From 75fb00db33f91a16b706897542c703abd956094a Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:32:03 -0700 Subject: [PATCH 04/22] table formatting --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index cb0b03011c..896111f8b3 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
From fa2475afcd4d0565a5281b3ef8b33bd4721d5e21 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:40:16 -0700 Subject: [PATCH 05/22] table formatting --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 896111f8b3..1c10d4acaf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -76,7 +76,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
Exit code Meaning
Exit code MeaningSuggested fix
Suggested fix
0 Success From 42386a5239595660346cd48dadac9eb2526fbd43 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:55:32 -0700 Subject: [PATCH 06/22] table formatting --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 1c10d4acaf..f643327a10 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
From b013e7cf58ffa4c26979bc8b5e24cde0e9fcbe2d Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 14:08:35 -0700 Subject: [PATCH 07/22] removed divs from tables --- .../upgrade-readiness-deployment-script.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index f643327a10..58802e85bf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -108,22 +108,22 @@ The deployment script displays the following exit codes to let you know if it wa
See [Generate your Commercial ID key](upgrade-readiness-get-started.md#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. - - - @@ -179,7 +179,7 @@ For previous operating systems, connectivity is verified by connecting to https: - @@ -244,8 +244,8 @@ For previous operating systems, connectivity is verified by connecting to https: - From 7a6c57fb9d110fde1fd02445af2c05466202c0c6 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 14:20:15 -0700 Subject: [PATCH 08/22] still playing with table size --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 58802e85bf..9256cab8df 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa -
Exit code Meaning
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
-		The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** +The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception. -The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location. +		The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12 Can’t connect to Microsoft - Vortex. Check your network/proxy settings. @@ -163,7 +163,7 @@ For previous operating systems, connectivity is verified by connecting to https: Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
+		An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** 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.
21Verify that this environment variable is configured on the computer.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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.
25Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
-or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** +or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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](/windows/configuration/configure-windows-telemetry-in-your-organization).
40
+
From 9a6eff268802287045db524a7a514c5775feff2f Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 14:32:55 -0700 Subject: [PATCH 09/22] still playing with table size --- .../upgrade/upgrade-readiness-deployment-script.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 9256cab8df..62768524f5 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -74,9 +74,9 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code Meaning
- - - + + + - - + - + - + @@ -180,7 +180,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +200,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - - or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ + or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** From ec3ad288ef4b8cc38fc6c0d38e3d514f4387acf8 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:15:13 -0700 Subject: [PATCH 12/22] trying smaller font for the whole table --- .../upgrade/upgrade-readiness-deployment-script.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index e5ee92c1bf..6174cfc954 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. - +
Exit codeMeaningSuggested fix
Exit codeMeaningSuggested fix
0 Success From 2939c6a5002395e3ff9ae19f29af16d84cc31971 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 10:32:27 -0700 Subject: [PATCH 10/22] fixing table --- .../upgrade-readiness-deployment-script.md | 447 +++++++++--------- 1 file changed, 233 insertions(+), 214 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 62768524f5..22ab8bc418 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -71,217 +71,236 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Exit codeMeaningSuggested fix
0Success -N/A - -
1Unexpected error occurred while executing the script. - 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. - -
2Error when logging to console. $logMode = 0.
(console only) -		Try changing the $logMode value to **1** and try again.
$logMode value 1 logs to both console and file. - -
3Error when logging to console and file. $logMode = 1. -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. - -
4Error when logging to file. $logMode = 2. -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. - -
5Error when logging to console and file. $logMode = unknown. -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. - -
6The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value. -		The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace. -
See [Generate your Commercial ID key](upgrade-readiness-get-started.md#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. - -
8Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -
Verify that the context under which the script in running has access to the registry key. - -
9The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -		Verify that the context under which the script in running has access to the registry key. - -
10Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -Verify that the deployment script is running in a context that has access to the registry key. - -
11Function **SetupCommercialId** failed with an unexpected exception. -The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location. - -
12Can’t connect to Microsoft - Vortex. Check your network/proxy settings. -**Http Get** on the end points did not return a success exit code.
-For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
-For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive. -
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](upgrade-readiness-get-started.md#enable-data-sharing). - - -
13Can’t connect to Microsoft - setting. -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](upgrade-readiness-get-started.md#enable-data-sharing). - - -
14Can’t connect to Microsoft - compatexchange. -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](upgrade-readiness-get-started.md#enable-data-sharing). - -
15Function CheckVortexConnectivity failed with an unexpected exception. -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](upgrade-readiness-get-started.md#enable-data-sharing). Check the logs for the exception message and the HResult. - -
16The computer requires a reboot before running the script. -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. - -
17Function **CheckRebootRequired** failed with an unexpected exception. -A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult. - -
18Appraiser KBs not installed or **appraiser.dll** not found. -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](upgrade-readiness-get-started.md#data-collection-and-privacy) and privacy topic. - -
19Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception. -Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed. - -
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** -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. - -
21Function **SetRequestAllAppraiserVersions** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
22**RunAppraiser** failed with unexpected exception. -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. - -
23Error finding system variable **%WINDIR%**. -Verify that this environment variable is configured on the computer. - -
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -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. - -
25The function **SetIEDataOptIn** failed with unexpected exception. -Check the logs for the exception message and HResult. - -
26The operating system is Server or LTSB SKU. - The script does not support Server or LTSB SKUs. - -
27The script is not running under **System** account. -The Upgrade Readiness configuration script must be run as **System**. - -
28Could not create log file at the specified **logPath**. - Make sure the deployment script has access to the location specified in the **logPath** parameter. - -
29Connectivity check failed for proxy authentication. -Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting. -
The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. -
For Windows 8.1 computers, 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). - -
30Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled. -The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. -
For Windows 8.1 computers, 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). - -
31There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. -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. - -
32Appraiser version on the machine is outdated. -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](upgrade-readiness-get-started.md#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1. - -
33**CompatTelRunner.exe** exited with an exit code -**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. - -
34Function **CheckProxySettings** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
35Function **CheckAuthProxy** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
36Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
37**Diagnose_internal.cmd** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
38Function **Get-SqmID** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** -or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -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](/windows/configuration/configure-windows-telemetry-in-your-organization). - -
40Function **CheckTelemetryOptIn** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
41The script failed to impersonate the currently logged on user. -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. - -
42Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
43Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
44Function **Diagtrack.dll** version is old and so Auth Proxy will not work. -Update the computer using Windows Update or WSUS. - -
45**Diagtrack.dll** not found. -Update the computer using Windows Update or WSUS. - -
46**DisableEnterpriseAuthProxy** property should be set to 1 for ClientProxy=Telemetry to work. -The ClientProxy=Telemetry scenario requires the **DisableEnterpriseAuthProxy** registry key to be set to 1 at registry path: **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. - -
47**TelemetryProxyServer** property is not present in the Windows registry at **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. -ClientProxy selected is Telemetry. The **TelemetryProxyServer** key is not present at Windows registry path: **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. - -
48The **CommercialID** referenced in RunConfig.bat must be a GUID. -The **CommercialID** that is entered in RunConfig.bat must be a GUID. Copy the commercial ID from your workspace. To find the commercialID on the OMS portal, view Upgrade Readiness > Settings. You will find the commercial ID on the settings page. - -
\ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ + + + + + + + + + + + + + + + + + + + + +
Exit codeMeaningSuggested fix
0SuccessN/A
1Unexpected error occurred while executing the script. 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.
2Error when logging to console. $logMode = 0.
(console only)		Try changing the $logMode value to **1** and try again.
$logMode value 1 logs to both console and file.
3Error when logging to console and file. $logMode = 1.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.
4Error when logging to file. $logMode = 2.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.
5Error when logging to console and file. $logMode = unknown.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.
6The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value.		The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace. +
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.
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Verify that the context under which the script in running has access to the registry key.
9The script failed to write Commercial Id to registry. +
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the deployment script is running in a context that has access to the registry key.
11Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.
12Can’t connect to Microsoft - Vortex. Check your network/proxy settings.**Http Get** on the end points did not return a success exit code.
+ For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
+ For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive. +
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).
13Can’t connect to Microsoft - setting. 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).
14Can’t connect to Microsoft - compatexchange.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).
15Function CheckVortexConnectivity failed with an unexpected exception.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.
16The computer requires a reboot before running the script.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.
17Function **CheckRebootRequired** failed with an unexpected exception.A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult.
18Appraiser KBs not installed or **appraiser.dll** not found.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.
19Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception.Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
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.
21Function **SetRequestAllAppraiserVersions** failed with an unexpected exception.Check the logs for the exception message and HResult.
22**RunAppraiser** failed with unexpected exception.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.
23Error finding system variable **%WINDIR%**.Verify that this environment variable is configured on the computer.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
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.
25The function **SetIEDataOptIn** failed with unexpected exception.Check the logs for the exception message and HResult.
26The operating system is Server or LTSB SKU. The script does not support Server or LTSB SKUs.
27The script is not running under **System** account.The Upgrade Readiness configuration script must be run as **System**.
28Could not create log file at the specified **logPath**. Make sure the deployment script has access to the location specified in the **logPath** parameter.
29Connectivity check failed for proxy authentication. Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting. +
The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. +
For Windows 8.1 computers, 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).
30Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled.The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. +
For Windows 8.1 computers, 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).
31There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. 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.
32Appraiser version on the machine is outdated. 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.
33**CompatTelRunner.exe** exited with an exit code **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.
34Function **CheckProxySettings** failed with an unexpected exception. Check the logs for the exception message and HResult.>
35Function **CheckAuthProxy** failed with an unexpected exception.Check the logs for the exception message and HResult.
36Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception.Check the logs for the exception message and HResult.
37**Diagnose_internal.cmd** failed with an unexpected exception.Check the logs for the exception message and HResult.
38Function **Get-SqmID** failed with an unexpected exception. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
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).
40Function **CheckTelemetryOptIn** failed with an unexpected exception. Check the logs for the exception message and HResult.
41The script failed to impersonate the currently logged on user. 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.
42Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
43Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception.Check the logs for the exception message and HResult.
\ No newline at end of file From 7ba635949471d21edef301527f531716e0141cb4 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:01:08 -0700 Subject: [PATCH 11/22] changing font size for reg keys --- .../upgrade-readiness-deployment-script.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 22ab8bc418..e5ee92c1bf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -114,26 +114,26 @@ The deployment script displays the following exit codes to let you know if it wa
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ 		Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** 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.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** 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).
@@ -303,4 +303,5 @@ The deployment script displays the following exit codes to let you know if it wa -
Exit code43 Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
\ No newline at end of file +
+ \ No newline at end of file From 0ea38f35a6e61ed4c3bdceac99244d65617ef7f3 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:29:08 -0700 Subject: [PATCH 13/22] font size --- .../upgrade/upgrade-readiness-deployment-script.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 6174cfc954..9fd126d7ab 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. - +
@@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - - or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** + @@ -304,4 +304,4 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** + or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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).
Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- \ No newline at end of file +
\ No newline at end of file From e5a85a93b59a3c716794e6af871ad5ad82a24365 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:38:43 -0700 Subject: [PATCH 14/22] trying md table --- .../upgrade-readiness-deployment-script.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 9fd126d7ab..11e09d889a 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -83,7 +83,7 @@ The deployment script displays the following exit codes to let you know if it wa
1Unexpected error occurred while executing the script.Unexpected error occurred while executiEng the script. 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.
Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- \ No newline at end of file + + +| Exit code | Meaning | Suggested fix | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Success | N/A | +| 1 | Unexpected error occurred while executing the script. | 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. | +| 2 | Error when logging to console. | Try changing the $logMode value to **1** and try again.$logMode value 1 logs to both console and file. | +| 3 | Error when logging to console and file. $logMode = 1. | 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. | +| 4 | Error when logging to file. $logMode = 2. | 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. | +| 5 | Error when logging to console and file. $logMode = unknown. | 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.< | +| 6 | The commercialID parameter is set to unknown. Modify the runConfig.bat file to set the CommercialID value. | 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. | +| 8 | Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**,Verify that the context under which the script in running has access to the registry key. | +| 9 | The script failed to write Commercial Id to registry.,Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | Verify that the context under which the script in running has access to the registry key.| From 755b8c2b8ceceb5b605950e675ab350b84cd0f3f Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 15:37:44 -0700 Subject: [PATCH 15/22] replaced font with style:font-size --- .../upgrade-readiness-deployment-script.md | 30 ++++++------------- 1 file changed, 9 insertions(+), 21 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 11e09d889a..97c8f28afa 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -114,26 +114,26 @@ The deployment script displays the following exit codes to let you know if it wa
8Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** + Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** +
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
> 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		 Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>
Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
> 		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.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		 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.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** - or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
> + or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		 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).
Check the logs for the exception message and HResult.
- -| Exit code | Meaning | Suggested fix | -|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 0 | Success | N/A | -| 1 | Unexpected error occurred while executing the script. | 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. | -| 2 | Error when logging to console. | Try changing the $logMode value to **1** and try again.$logMode value 1 logs to both console and file. | -| 3 | Error when logging to console and file. $logMode = 1. | 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. | -| 4 | Error when logging to file. $logMode = 2. | 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. | -| 5 | Error when logging to console and file. $logMode = unknown. | 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.< | -| 6 | The commercialID parameter is set to unknown. Modify the runConfig.bat file to set the CommercialID value. | 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. | -| 8 | Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**,Verify that the context under which the script in running has access to the registry key. | -| 9 | The script failed to write Commercial Id to registry.,Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | Verify that the context under which the script in running has access to the registry key.| From 8f1741f9bf41b00192a7d7986acb4fe7488ffd97 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 15:49:35 -0700 Subject: [PATCH 16/22] trying font size xxsmall --- .../upgrade-readiness-deployment-script.md | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 97c8f28afa..f9206c5c0a 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,8 +70,8 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. -
- +
+
@@ -114,26 +114,26 @@ The deployment script displays the following exit codes to let you know if it wa - - + - + - + @@ -180,7 +180,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +200,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - + From 5d9f0530b051beb35f1a377b4a78cfa43f8f4503 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 16:35:38 -0700 Subject: [PATCH 17/22] fixed font size in table --- .../upgrade-readiness-deployment-script.md | 25 +++++++++---------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index f9206c5c0a..2d803f1012 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -68,9 +68,8 @@ To run the Upgrade Readiness deployment script: 5. 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. +The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. -
Exit code Meaning
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
> + 		Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
> +
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>
Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
> 		An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
 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.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 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.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
> - or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
+ or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 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).
@@ -84,7 +83,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -114,26 +113,26 @@ The deployment script displays the following exit codes to let you know if it wa - - + - + - + @@ -180,7 +179,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +199,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +279,8 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -304,4 +303,4 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code
1 Unexpected error occurred while executiEng the script. 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. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966) from the download center and try again.
2
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ 		Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** 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.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
- or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** + or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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).
Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
-
+ From 81a4d4db2809f7ad773008456a2bc1f6633048a3 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 16:49:01 -0700 Subject: [PATCH 18/22] added font size around the table to try to make text smaller --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 2d803f1012..dbee3d45e1 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,6 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. + @@ -303,4 +304,4 @@ The deployment script displays the following exit codes to let ddfyou know if it
Exit codeFunction **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- + From ed6822497e30a1f9d6ba5c957da7e28c7a2c5a40 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 17:06:24 -0700 Subject: [PATCH 19/22] wrapping table in div tag to try to get smaller font --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index dbee3d45e1..c62727df3e 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. - +
@@ -304,4 +304,4 @@ The deployment script displays the following exit codes to let ddfyou know if it
Exit codeFunction **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- +
From c27b6aeb936f67002088dcf96970d90014d192c8 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 17:38:27 -0700 Subject: [PATCH 20/22] fixed typo in div --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index c62727df3e..2b9e9ed18b 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. -
+
From 54af9e6347fc39ce9009c34b5d15a8dd63f42737 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 18:07:07 -0700 Subject: [PATCH 21/22] collapsed three column table into 2 --- .../upgrade-readiness-deployment-script.md | 134 ++++++------------ 1 file changed, 45 insertions(+), 89 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 2b9e9ed18b..2e289b8a5b 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -73,235 +73,191 @@ The deployment script displays the following exit codes to let ddfyou know if it
Exit code
- - + - - + - - + - - + - - + - - + - - + - - + - - + - - - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - - - + - - + - - + - - +
Exit codeMeaningExit code and meaning Suggested fix
0Success
0 - Success N/A
1Unexpected error occurred while executiEng the script.1 - Unexpected error occurred while executiEng the script. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966) from the download center and try again.
2Error when logging to console. $logMode = 0.
(console only)		2 - Error when logging to console. $logMode = 0.
(console only)		 Try changing the $logMode value to **1** and try again.
$logMode value 1 logs to both console and file.
3Error when logging to console and file. $logMode = 1.3 - Error when logging to console and file. $logMode = 1. 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.
4Error when logging to file. $logMode = 2.4 - Error when logging to file. $logMode = 2. 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.
5Error when logging to console and file. $logMode = unknown.5 - Error when logging to console and file. $logMode = unknown. 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.
6The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value.		6 - The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value.		 The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace.
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.
8Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**8 - Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9The script failed to write Commercial Id to registry. + 9 - The script failed to write Commercial Id to registry.
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**10 - Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11Function **SetupCommercialId** failed with an unexpected exception.11 - Function **SetupCommercialId** failed with an unexpected exception. The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12Can’t connect to Microsoft - Vortex. Check your network/proxy settings.12 - Can’t connect to Microsoft - Vortex. Check your network/proxy settings. **Http Get** on the end points did not return a success exit code.
For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive.
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).
13Can’t connect to Microsoft - setting. 13 - Can’t connect to Microsoft - setting. 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).
14Can’t connect to Microsoft - compatexchange.14 - Can’t connect to Microsoft - compatexchange. 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).
15Function CheckVortexConnectivity failed with an unexpected exception.15 - Function CheckVortexConnectivity failed with an unexpected exception. 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.
16The computer requires a reboot before running the script.16 - The computer requires a reboot before running the script. 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.
17Function **CheckRebootRequired** failed with an unexpected exception.17 - Function **CheckRebootRequired** failed with an unexpected exception. A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult.
18Appraiser KBs not installed or **appraiser.dll** not found.18 - Appraiser KBs not installed or **appraiser.dll** not found. 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.
19Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception.19 - Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception. Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** 20 - An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** 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.
21Function **SetRequestAllAppraiserVersions** failed with an unexpected exception.21 - Function **SetRequestAllAppraiserVersions** failed with an unexpected exception. Check the logs for the exception message and HResult.
22**RunAppraiser** failed with unexpected exception.22 - **RunAppraiser** failed with unexpected exception. 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.
23Error finding system variable **%WINDIR%**.23 - Error finding system variable **%WINDIR%**. Verify that this environment variable is configured on the computer.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**24 - The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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.
25The function **SetIEDataOptIn** failed with unexpected exception.25 - The function **SetIEDataOptIn** failed with unexpected exception. Check the logs for the exception message and HResult.
26The operating system is Server or LTSB SKU.26 - The operating system is Server or LTSB SKU. The script does not support Server or LTSB SKUs.
27The script is not running under **System** account.27 - The script is not running under **System** account. The Upgrade Readiness configuration script must be run as **System**.
28Could not create log file at the specified **logPath**.28 - Could not create log file at the specified **logPath**. Make sure the deployment script has access to the location specified in the **logPath** parameter.
29Connectivity check failed for proxy authentication. 29 - Connectivity check failed for proxy authentication. Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting.
The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
For Windows 8.1 computers, 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).
30Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled.30 - Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled. The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
For Windows 8.1 computers, 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).
31There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. 31 - There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. 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.
32Appraiser version on the machine is outdated. 32 - Appraiser version on the machine is outdated. 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.
33**CompatTelRunner.exe** exited with an exit code 33 - **CompatTelRunner.exe** exited with an exit code **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.
34Function **CheckProxySettings** failed with an unexpected exception. 34 - Function **CheckProxySettings** failed with an unexpected exception. Check the logs for the exception message and HResult.>
35Function **CheckAuthProxy** failed with an unexpected exception.35 - Function **CheckAuthProxy** failed with an unexpected exception. Check the logs for the exception message and HResult.
36Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception.36 - Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception. Check the logs for the exception message and HResult.
37**Diagnose_internal.cmd** failed with an unexpected exception.37 - **Diagnose_internal.cmd** failed with an unexpected exception. Check the logs for the exception message and HResult.
38Function **Get-SqmID** failed with an unexpected exception. 38 - Function **Get-SqmID** failed with an unexpected exception. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** + 39 - For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 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).
40Function **CheckTelemetryOptIn** failed with an unexpected exception. 40 - Function **CheckTelemetryOptIn** failed with an unexpected exception. Check the logs for the exception message and HResult.
41The script failed to impersonate the currently logged on user. 41 - The script failed to impersonate the currently logged on user. 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.
42Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. 42 - Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
43Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception.43 - Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
-
+ From 8ba888ef74a14c1320718fef387622a63b5abb6b Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Thu, 27 Apr 2017 13:50:19 -0700 Subject: [PATCH 22/22] updating MDM policy --- ...windows-operating-system-components-to-microsoft-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index f844b54aa3..e81b1db45a 100644 --- a/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -1288,7 +1288,7 @@ To change the level of diagnostic and usage data sent when you **Send your devic -or- -- Create a REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\Policies\\Microsoft\\Windows\\DataCollection!AllowTelemetry**, with a value of 0 (zero). +- Create a REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DataCollection\\AllowTelemetry**, with a value of 0 (zero). -or-