How to Configure the SCCM Upgrade Readiness Connector

Benoit LecoursOMS, SCCM11 Comments

Upgrade Readiness (formerly Upgrade Analytics) enables you to assess and analyze device readiness with Windows 10.  You can integrate Upgrade Readiness with SCCM to access client upgrade compatibility data in the SCCM admin console. You are able to target devices for upgrade or remediation from the device list.

Support for integrating Upgrade Analytics (now Upgrade Readiness) was introduced in SCCM 1610. With the 1706 release, there’s an improved integration of SCCM and Azure Services. These improvements streamline how you configure the Azure services you use with Configuration Manager. We thought this was a good opportunity to describe how to configure SCCM with the Upgrade Readiness Connector.

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.

Prerequisite for SCCM Upgrade Readiness Connector

This post assumes that you have the following:

Configuration steps

To connect SCCM to Upgrade Readiness the following steps are required :

Register SCCM as web application in Azure AD

This step will create an application in Azure AD for the SCCM Upgrade Readiness Connector.

SCCM OMS Connector

  • click New Application Registration

SCCM OMS Connector

  • Enter the following information :
    • Name: Specify a name for the application
    • Type: Web app / API
    • Sign-on URL: Specify any URL. (This URL doesn’t need to resolve)

SCCM Upgrade Readiness Connector

  • Click Create at the bottom to create the application
  • Select your application and click on All Settings
  • Click on Keys, enter a name, select a duration and click Save. The key will be created after clicking Save and can only be retrieved on this page

SCCM Upgrade Readiness Connector

  • Copy the Key and Application ID from this page. It will be needed later.
  • Still in your application, click on General / Properties and copy the App ID URI

SCCM Upgrade Readiness Connector

Give SCCM Application permission

We will now provide the Azure AD App permissions to access the Upgrade Readiness service.

  • Go to Ressource groups, select the resource group in which you create your OMS Workspace
  • Select Access Control (IAM)
  • Click Add
  • Select the Contributor Role and select your application, click Save

SCCM Upgrade Readiness Connector

Upgrade Readiness Configuration

We will now add the Upgrade Readiness solution to your Operation Management Suite portal.

  • Log to your OMS portal
  • In the Home pane, select Solution Gallery

SCCM Upgrade Readiness Connector

  • Locate Upgrade Readiness and click on it

SCCM Upgrade Readiness Connector

  • Select Add

SCCM Upgrade Readiness Connector

  • Once the setup is completed you’ll see the upgrade statistics in your OMS portal. You can see your Commercial ID Key by clicking the Solution Settings button. This key will be needed in the deployment script that you’ll be sending to your client.

SCCM Upgrade Readiness Connector SCCM Upgrade Readiness Connector

Configure the SCCM Upgrade Rediness Connector

To create the connection, you’ll need the information of the Azure AD App you just created.

  • Open the SCCM Console
  • Go to Administration / Cloud Services / Azure Services
  • Right-click Azure Services and select Configure Azure Services

SCCM OMS Connector

  • On the Azure Services tab, name your connection and select Upgrade Readiness Connector

SCCM Upgrade Readiness Connector

  • On the App page, select your Azure environment and click Import

SCCM Upgrade Readiness Connector

  • On the Import Apps page, specify the following information :
  • Azure AD Tenant Name: Specify any name
  • Azure AD Tenant ID: Specify the Azure AD tenant – You can find this information under Azure Active Directory / Properties

SCCM OMS Connector

  • Application Name – Specify your application name
  • Client ID: Specify the Application ID of the created Azure AD app. You can see where to find this information in the previous steps
  • Secret key: Specify the Client secret key of the created Azure AD app. You can see where to find this information in the previous steps
  • Secret Key expiry: Specify the expiration date of your key
  • App ID URI: Specify the App ID URI of the created Azure AD app. You can see where to find this information in the previous steps
  • Click on Verify then Ok

SCCM Upgrade Readiness Connector

  • On the configuration page, the information will be pre-populate once the Azure AD app has enough permissions on the resource group. If the fields are empty, your application doesn’t have the necessary rights.

SCCM Upgrade Readiness Connector

  • On the Summary page, click Next

SCCM Upgrade Readiness Connector

  • On the Completion page, click Close

SCCM Upgrade Readiness Connector

Run and Deploy Upgrade Readiness Script

The computers that you want to evaluate needs to run a script to send their data.

To do so :

  • Download the Upgrade Readiness deployment script
  • Extract the zip file
  • Edit .\ UpgradeAnalytics092816\Deployment\RunConfig.bat file
  • Change the following values :
    • LogPath : Where you want the logs to be saved
    • CommercialIDValue : Enter your commercial key
    • Logmode : 1

SCCM Upgrade Readiness Connector

Save the script, create a package and deploy it to your Windows 7 or 8 computers.



Once run, it can take betweek 24 to 48 hours for the first number to show in your OMS workspace and another 24-48h to show up in the SCCM Console. Be patient!

After the configuration is completed you can view the numbers in Monitoring / Upgrade Readiness.

SCCM Upgrade Readiness Connector

Share this Post

11 Comments on “How to Configure the SCCM Upgrade Readiness Connector”

  1. I have not run the script yet but computers are reporting. I AM CONFUSED. Is setting the upgrade readiness client settings enough? What is triggering the data upload.

  2. great guide. only thing I messed up on was not making the proper OMS instance first. So just make sure you have your OMS instance setup, and then look in Azure Portal and you’ll see a resource group called MMS-???. Thanks so much.

  3. Do you happen to know if the data plan within OMS makes a difference in the data that is being reported in the Monitoring Upgrade Readiness area in SCCM? WE are seeing “mixed” results with the use of the free data plan (7 days retention). Not sure if the data plan in the OMS suite makes a difference?

  4. I messed up the ‘Resource Group’ portion, since I didn’t see the Azure Subscription parts at the end. I closed out of that in ConfigMgr, fixed the issue in Azure, went back to add everything and it now says ‘App already exists’ and won’t let me proceed.

    Any ideas?

    1. @Adam — Wayyyy late reply, but I was setting this up for a client and ran into that issue. You just need to go into Administration > Cloud Services > Azure Active Directory Tenants and select your Application in the list in the bottom pane, then click “Delete” in the top bar. Repeat the import process and you’ll be good to go. Hopefully this helps someone else who runs into it, if not you!


Leave a Reply