diff --git a/windows/deploy/upgrade-analytics-get-started.md b/windows/deploy/upgrade-analytics-get-started.md index 5dc8cc72d9..55c480daba 100644 --- a/windows/deploy/upgrade-analytics-get-started.md +++ b/windows/deploy/upgrade-analytics-get-started.md @@ -77,7 +77,7 @@ For Upgrade Analytics to receive and display upgrade readiness data from Microso To enable data sharing, whitelist the following endpoints. Note that you may need to get approval from your security group to do this. -Note: The compatibility update KB runs under the computer’s system account. If you are using user authenticated proxies, read [this blog post]()to learn what you need to do to run it under the logged on user account. +Note: The compatibility update KB runs under the computer’s system account. If you are using user authenticated proxies, read [this blog post](https://go.microsoft.com/fwlink/?linkid=838688)to learn what you need to do to run it under the logged on user account. | **Endpoint** | **Function** | |---------------------------------------------------------|-----------| @@ -170,39 +170,40 @@ The deployment script displays the following exit codes to let you know if it wa
-
Exit codeMeaning -
0Success -
1Unexpected error occurred while executing the script -
2Error when logging to console. $logMode = 0. -
3Error when logging to console and file. $logMode = 1. -
4Error when logging to file. $logMode = 2. -
5Error when logging to console and file. $logMode = unknown. -
6The commercialID parameter is set to unknown. Modify the script. -
8Failure to create registry key path: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection. -
9Error when writing CommercialId to registry. -
10Error when writing CommercialDataOptIn to registry. -
11Function -SetupCommercialId: Unexpected failure. -
12Can’t connect to Microsoft – Vortex. Check your network/proxy settings. -
13Can’t connect to Microsoft – setting. Verify that the required endpoints are whitelisted correctly. -
14Can’t connect to Microsoft – compatexchange. Verify that the required endpoints are whitelisted. -
15Error connecting to Microsoft:Unexpected failure. -
16Machine requires reboot. -
17Function -CheckRebootRequired: Unexpected failure. -
18Outdated compatibility update KB package. Update via Windows Update/WSUS. -
19The compatibility update failed with unexpected exception. -
20Error writing RequestAllAppraiserVersions registry key. -
21Function – SetRequestAllAppraiserVersions: Unexpected failure. -
22RunAppraiser failed with unexpected exception. -
23Error finding system variable %WINDIR%. -
24SetIEDataOptIn failed when writing IEDataOptIn to registry. -
25SetIEDataOptIn failed with unexpected exception. -
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 Analytics configuration script must be run as system. -
28Could not create log file at the specified logPath. -
29 Connectivity check failed for proxy authentication. Install the cumulative updates on the machine and enable the authentication proxy settings : [Win 7](https://support.microsoft.com/en-us/kb/3192403), [Win 8.1](https://support.microsoft.com/en-us/kb/3192404), [Win 10 Build 1511 (TH2)](https://support.microsoft.com/en-us/kb/3192441). -For more information on authentication proxy support, see [this blog post] (). -
30This means that the connectivity check failed, and the most likely cause is that the proxy setting is not enabled correctly. For instructions on setting the registry keys, see [Win 7](https://support.microsoft.com/en-us/kb/3192403), [Win 8.1](https://support.microsoft.com/en-us/kb/3192404), [Win 10 Build 1511 (TH2)](https://support.microsoft.com/en-us/kb/3192441). For more information on authentication proxy support, see [this blog post] (). -
30There is more than one instance of the Upgrade Analytics data collector running at the same time on this machine. This could be because a scheduled task was running when the script was run, or a second instance of the script was launched before the first one was completed. +
Exit codeMeaningSuggest fix +
0Success +
1Unexpected error occurred while executing the script The files in the deployment script are likely corrupted. Download the latest script from the [download center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and try again. +
2Error when logging to console. $logMode = 0. Try changing the $logMode value to **1** and try again. +
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 script.Set the value for CommercialID in runconfig.bat file. +
8Failure to create registry key path: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection. Verify that the configuration script has access to this location. +
9Error when writing CommercialId to registry.Verify that the configuration script has access to this location. +
10Error when writing CommercialDataOptIn to registry.Verify that the configuration script has access to this location. +
11Function -SetupCommercialId: Unexpected failure.Verify that the configuration script has access to this location. +
12Can’t connect to Microsoft – Vortex. Check your network/proxy settings.Verify that the required endpoints are whitelisted correctly. +
13Can’t connect to Microsoft – setting. Verify that the required endpoints are whitelisted correctly. +
14Can’t connect to Microsoft – compatexchange. Verify that the required endpoints are whitelisted. +
15Error connecting to Microsoft:Unexpected failure. +
16Machine requires reboot. The reboot is required to complete the installation of the compatibility update and related KBs. Reboot the machine before running the Upgrade Analytics deployment script. +
17Function -CheckRebootRequired: Unexpected failure.he reboot is required to complete the installation of the compatibility update and related KBs. Reboot the machine before running the Upgrade Analytics deployment script. +
18Outdated compatibility update KB package. Update via Windows Update/WSUS. +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 Analytics solution. Use the latest version of the Compatibility update for Windows 7 SP1/Windows 8.1. On Windows 10, the Compatibility update is part of the cumulative updates and is not available as a separate package. +
19The compatibility update failed with unexpected exception. The files in the deployment script are likely corrupted. Download the latest script from the [download center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and try again. +
20Error writing RequestAllAppraiserVersions registry key. This registry key is required for data collection to work correctly. Verify that the configuration script has access to this location. +
21Function – SetRequestAllAppraiserVersions: Unexpected failure.This registry key is required for data collection to work correctly. Verify that the configuration script has access to this location. +
22RunAppraiser failed with unexpected exception. Check %windr%\System32 directory for a file called CompatTelRunner.exe. If the file does not exist, reinstall the required compatibility updates which include this file, and check your organization group policy to make sure it does not remove this file. +
23Error finding system variable %WINDIR%. Make sure that this environment variable is available on the machine. +
24SetIEDataOptIn failed when writing IEDataOptIn to registry. Verify that the deployment script in running in a context that has access to the registry key. +
25SetIEDataOptIn failed with unexpected exception. The files in the deployment script are likely corrupted. Download the latest script from the [download center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) and try again. +
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 Analytics 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. +
29 Connectivity check failed for proxy authentication. Install the cumulative updates on the machine and enable the `DisableEnterpriseAuthProxy` authentication proxy setting. The `DisableEnterpriseAuthProxy` is enabled by default for Windows 7. For Windows 8.1 machines, set the `DisableEnterpriseAuthProxy` 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` is enabled by default for Windows 7. For Windows 8.1 machines, set the `DisableEnterpriseAuthProxy` to **0** (not disabled).For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688). +
30There is more than one instance of the Upgrade Analytics data collector running at the same time on this machine. Use the Windows Task Manager to check if CompatTelRunner.exe is running, and wait until it has completed to rerun the script. +**The Upgrade Analytics task is scheduled to run daily at 3 a.m.**