diff --git a/windows/deploy/upgrade-readiness-deployment-script.md b/windows/deploy/upgrade-readiness-deployment-script.md index 1e07083756..1c2d6a3913 100644 --- a/windows/deploy/upgrade-readiness-deployment-script.md +++ b/windows/deploy/upgrade-readiness-deployment-script.md @@ -99,22 +99,22 @@ The deployment script displays the following exit codes to let you know if it wa
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**. +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. 10 -Error 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. @@ -154,7 +154,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. 20 -An 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. 21 @@ -170,7 +170,7 @@ For previous operating systems, connectivity is verified by connecting to https: Verify that this environment variable is configured on the computer. 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**. +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. 25 @@ -235,8 +235,8 @@ For previous operating systems, connectivity is verified by connecting to https: Check the logs for the exception message and HResult. 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: 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). 40