Windows Upgrade Analytics

May 26

How to setup Microsoft Upgrade Analytics tool to Evaluate Windows 10 Readiness. I will show you some steps to set up Upgrade Analytics. I will use OMS Workspace with a free data plan. So you need an Azure subscription and an OMS Workspace.

These software updates needs to be installed on win7 and win8 clients:

Windows 7 Sp1 with the following updates
KB 2976978
KB 3150513
Windows 8.1 with the following updates
KB2952664
KB 3150513

Start your Azure Portal and Start Microsoft Operations Management Suite (see pic 1). You must select or create a workspace
(I use free pricing tier).

pic 1 Microsoft Operations Management Suite

When you have started your OMS Workspace click on OMS Portal and a new tab in your browser starts up with your OMS portal (see pic 2).

The next step you must take is to add Upgrade Analytics to your OMS Workspace. Click on Solutions Gallery (see pic 3).

In the solutions gallery add Update Complience, Upgrade Readiness and Device health. Look for Windows Analytics (see pic 4).

When you have added the tools your OMS portal will show you the tools (see pic 5).

Next step is to download the Upgrade Readiness Deployment Script. In my Test I download the Deployment Script on my windows 10 client (see pic 6).

Next step click on the settings (see pic 7).

In the settings go to Connected Sources and click on Windows Telemetry (see pic 8). You need the Commercial Id key in your downloaded deployment script.

pic 8 Windows Telemetry, commercial ID key

When you open the folder that you downloaded you will see two folders, Deployment and Pilot (see pic 9).

The Pilot folder contains advanced logging that can help troubleshoot issues and is intended to be run from an elevated command prompt. The Deployment folder offers a lightweight script intended for broad deployment through ConfigMGR or other software deployment system.

Open the folder Pilot and edit RunConfig (see pic 10).

In the file there are some sections you can edit. In the sections Commercial ID copy ID from OMS portal and paste in to your file. You do this so Microsoft can identify your organization.

More info : https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-readiness-deployment-script

Also edit logPath and Log mode (see pic 11).

It might be good to know that the Deployment script doesn’t install an agent or client in itself. When the script is running, the computer is invented and the information is sent to your Microsoft OMS workspace.

In your production you will have to schedule this with your configMGR for example. For my test I just open the folder and run the script on my Windows 10 client (see pic 12).