Setup Upgrade Analytics for your Windows 10 migration projects

Here is a step-by-step guide for setting up Upgrade Analytics for a Windows 10 migration project written by Ami Arwidmark (@aarwidmark).

Update October 18, 2016: Since the initial release of this article, I also added some screenshots from my lab following this guide.

Full details:


If you're URL filtering you'll want to make an exception for these URLs.  If you need to go through change review, start on this now!

Step-by-step guide

Step 1:

Sign up for Upgrade Analytics here:

Step 1.5:

Create an Azure subscription (it will ask for a credit card to verify your identity – Upgrade Analytics is currently a free service)
If you already have an Azure subscription, you can Upgrade Analytics to your work space

Step 2:
Now the fun begins.  In your work space, you need to add the feature. 

  • Go to Solutions Gallery from the left navigation pane and pick Upgrade Analytics
  • Copy your key from Settings / Connected Sources / Windows Telemetry and save it to a text file.
  • Subscribe to the Upgrade Analytics solution, by navigating to Settings / Connected Sources / Windows Telemetry – pick subscribe

Getting the Commercial ID Key from OMS Settings.

Step 3:

Deploy the following Windows Updates based on client (note – not all the KBs are provided to WSUS so you will need to manually download)

Windows 8.1

Windows 7

Note: The last KB (3170106) is only needed if you want to enable the Site Discovery feature, where data is collected on all sites visited by Internet Explorer, except during InPrivate sessions. This is disabled by default in the setup script.


Step 4:

Download, edit, and run the deployment script

  • Extract the zip file to somewhere that makes sense to you J
  • Go to . UpgradeAnalytics092816Deployment and edit the RunConfig.bat file (which in turn runs the ConfigScript.ps1 script) to include the following
    • Where you want the logs to go, in this example C:UADiagnostics.
    • Commercial ID (go back to that text file)
    • Log behavior (LogMode=1)  
    • AllowIData and IEOptinLevel (for site discovery, if you want to use that)

Here are the settings used when piloting this feature in the proof-of-concept environment.

Note: You can also set this by registry later if you forget/make a mistake

Once the script is configured, run it, or push it via SCCM (or preferred stinky third party solution) I guess Intune is ok to use too 🙂 #CloudFirst, right?

Step 5:

More fun – wait 24/48 hours (sleep, work, go to the amusement park, write a blog post, read a book – the choice is yours because it's like a free vacation)

THEN and only then will your endpoints show up in your workspace J. If you check any sooner than that you'll drive yourself crazy. Don't shoot the messenger, I'm not the one that made it take that long 🙂

Troubleshooting tips:

If you feel like it's not working, check on URL filtering, and Policy settings that deal with Automatic Updates. You basically need Auto Updates set anyway for this to be beneficial in the long run.

The Upgrade Analytics dashboard after indexing has completed.

About the author

Johan Arwidmark

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments