Integrate Upgrade Readiness with System Center Configuration Manager

Upgrade Readiness (formerly Upgrade Analytics) enables you to assess and analyze device readiness and compatibility with Windows 10, to allow easier and smoother upgrades. Integrate Upgrade Readiness with Configuration Manager to access client upgrade compatibility data in the Configuration Manager admin console. You'll then be able to target devices for upgrade or remediation from the device list.

Upgrade Readiness is a solution in the Microsoft Operations Management Suite (OMS). You can read more about Upgrade Readiness in Get started with Upgrade Readiness.

Configure clients

There are several configuration steps that you have to take to ensure that your clients can provide data to Upgrade Readiness:

Create a connection to Upgrade Readiness


  • In order to add the connection, your Configuration Manager environment must first configure a service connection point in an online mode. When you add the connection to your environment, it will also install the Microsoft Monitoring Agent on the machine running this site system role.
  • Register Configuration Manager as a “Web Application and/or Web API” management tool, and get the client ID from this registration.
  • Create a client key for the registered management tool in Azure Active Directory.
  • In the Azure Management Portal, provide the registered web app with permission to access OMS, as described in Provide Configuration Manager with permissions to OMS.


    When configuring permission to access OMS, be sure to choose the Contributor role, and assign it permissions to the resource group of the registered app.

Create the connection

  1. In the Configuration Manager console, choose Administration > Cloud Services > Upgrade Readiness Connector > Create Connection to Upgrade Analytics to start the Add Upgrade Analytics Connection Wizard.
  2. On the Azure Active Directory screen, provide Tenant, Client ID, and Client secret key, then select Next.
  3. On the Upgrade Readiness screen, provide your connection settings by filling in your Azure subscription, Azure resource group, and Operations Management Suite workspace.
  4. Verify your connection settings on the Summary screen, then select Next.


    You must connect Upgrade Readiness to the top-tier site in your hierarchy. If you connect Upgrade Readiness to a standalone primary site and then add a central administration site to your environment, you must delete and recreate the OMS connection within the new hierarchy.

Complete Upgrade Readiness tasks

After you've create the connection in Configuration Manager, perform these tasks, as described in Get started with Upgrade Readiness.

  1. Add the UpgradeReadiness service to the OMS workspace.
  2. Generate a commercial ID.
  3. Subscribe to Upgrade Readiness.

Use the Upgrade Readiness deployment script

You can automate many of the Upgrade Readiness tasks and troubleshoot data sharing issues with the Microsoft Upgrade Readiness deployment script.
The Upgrade Readiness deployment script does the following:

  • Sets commercial ID key + CommercialDataOptIn + RequestAllAppraiserVersions keys.
  • Verifies that user computers can send data to Microsoft.
  • Checks whether the computer has a pending restart.
  • Verifies that the latest version of KB package 10.0.x is installed (requires 10.0.14913 or subsequent releases).
  • If enabled, turns on verbose mode for troubleshooting.
  • Initiates the collection of the telemetry data that Microsoft needs to assess your organization’s upgrade readiness.
  • If enabled, displays the script’s progress in a cmd window, providing you visibility into issues (success or fail for each step) and/or writes to log file.

To run the Upgrade Readiness deployment script:

  1. Download the Upgrade Readiness deployment script and extract The files in the Diagnostics folder are necessary only if you plan to run the script in troubleshooting mode.
  2. Edit these parameters in RunConfig.bat:
  3. Storage location for log information. Example: %SystemDrive%\URDiagnostics. You can store log information on a remote file share or a local directory. If the script is blocked from creating the log file for the given path, it creates the log files in the drive with the Windows directory.
  4. Commercial ID key.
  5. By default, the script sends log information to both the console and the log file. To change the default behavior, use one of the following options:

    • logMode = 0 log to console only
    • logMode = 1 log to file and console
    • logMode = 2 log to file only
    • For troubleshooting, set isVerboseLogging to $true to generate log information that can help with diagnosing issues. By default, isVerboseLogging is set to $false. Ensure the Diagnostics folder is installed in the same directory as the script to use this mode.
    • Notify users if they need to restart their computers. By default, this is set to off.
  6. After you finish editing the parameters in RunConfig.bat, run the script as an administrator.

View Microsoft Upgrade Readiness properties in Configuration Manager

  1. In the Configuration Manager console, navigate to Cloud Services, then choose OMS Connector to open the OMS Connection Properties page.

  2. Within this page there are two tabs:

    • The Azure Active Directory tab shows your Tenant, Client ID, Client secret key expiration, and allows you to Verify your Client secret key if it has expired.
    • The Upgrade Readiness tab shows your Azure subscription, Azure resource group, and Operations Management Suite workspace.

View and use the upgrade information

After you've integrated Upgrade Readiness with Configuration Manager, you can view the analysis of your clients' upgrade readiness and then take action.

  1. In the Configuration Manager console, choose Monitoring > Overview > Upgrade Readiness.
  2. Review the data, which includes the upgrade readiness state and the percent of Windows devices that are reporting telemetry.
  3. You can filter the dashboard to view data for devices in specific collections.
  4. You can view the devices in a particular readiness state, and create a dynamic collection for those devices so that you can upgrade those devices if ready, or take action to bring them to a readiness state.
To submit product feedback, please visit Configuration Manager Feedback