deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 10:53:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

trying md table

Browse Source
This commit is contained in:
Liza Poggemeyer
2017-04-26 11:38:43 -07:00
parent 0ea38f35a6
commit e5a85a93b5
1 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
windows/deployment/upgrade/upgrade-readiness-deployment-script.md
View File

@ -83,7 +83,7 @@ The deployment script displays the following exit codes to let you know if it wa
</tr>
<tr>
<td>1</td>
<td>Unexpected error occurred while executing the script.</td>
<td>Unexpected error occurred while executiEng the script.</td>
<td> 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.</td>
</tr>
<tr>
@ -305,3 +305,15 @@ The deployment script displays the following exit codes to let you know if it wa
<td>Check the logs for the exception message and HResult.</td>
</table>
</div>
| 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.|