Authentication proxy support added in new version (12.28.16) of the Upgrade Analytics deployment script


On December 28, 2016, we released an updated version of the Upgrade Analytics Deployment script.  If you are using an older version of the script, we encourage you to download the latest script from the Microsoft Download Center.

 

To allow data to be sent from the machine to the Upgrade Analytics service in an environment where user authenticated proxy is being used, authentication proxy patches must be installed and enabled on the machine.  The authentication proxy patches are available as part of cumulative updates for Windows 7 SP1, Windows 8.1, and Windows 10 version 1511.  The patch is enabled by default on Windows 7 machines, but you must enable it via regkey on Windows 8.1 and Windows 10 version 1511 machines.  For instructions on how to do so, see the “Registry information” section of the KB support pages for Windows 8.1 or Windows 10 version 1511.

The Upgrade Analytics deployment script has also been updated to support user-authenticated proxies and make connectivity checks under those scenarios.   The latest Upgrade Analytics deployment script is available on the download center.

 

When authentication proxy is enabled, the client impersonates the logged on user to send data to the Upgrade Analytics service.  When you run the latest Upgrade Analytics deployment script, it replicates the behavior of impersonating the user when it checks for connectivity to the Upgrade Analytics service.  If the connectivity check fails, you will see the following error codes:

* Exit code 29:  This means that the connectivity check failed, and the most likely cause is the updates required for authentication proxy are not installed.  Install the cumulative updates on the machine and enable the authentication proxy settings through registry settings.  You can find the instructions and the updates here:  Windows 7 SP1, Windows 8.1, Windows 10 version 1511.

* Exit code 30:  This means that the connectivity check failed, and the most likely cause is that the registry key is not set correctly.  For detailed instructions, see the section titled “Registry information” on the KB support page for Windows 7Windows 8.1, or Windows 10 version 1511 machines.

 

If you have any questions about the auth proxy patches, don’t hesitate to reach out by commenting below or sending us an email.


Comments (0)

Skip to main content