From fa6f5fdff863fcb9061dbfcf8f816e879cb72ba7 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 28 Feb 2017 14:45:09 -0800 Subject: [PATCH] jj --- windows/deploy/upgrade-readiness-deployment-script.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deploy/upgrade-readiness-deployment-script.md b/windows/deploy/upgrade-readiness-deployment-script.md index a5a5b726f3..1e07083756 100644 --- a/windows/deploy/upgrade-readiness-deployment-script.md +++ b/windows/deploy/upgrade-readiness-deployment-script.md @@ -65,7 +65,7 @@ The deployment script displays the following exit codes to let you know if it wa - + -
Exit code
Exit code Meaning Suggested fix @@ -99,7 +99,7 @@ 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.
8Failure to create 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..