From 5d9f0530b051beb35f1a377b4a78cfa43f8f4503 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 16:35:38 -0700 Subject: [PATCH] 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. -
@@ -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.
-
+