- New in Application requests in SCCM 1906 - Mon, Sep 16 2019
- Application approval in SCCM 1810 and beyond is a game changer - Fri, Jan 25 2019
- Windows 10 1809 kiosk mode with an AD domain account - Mon, Nov 26 2018
If Windows Upgrade Analytics flags clients as "ready to upgrade," Configuration Manager automatically starts the upgrade process. You can create new collections based on existing collections and the assessments of Windows Upgrade Analytics. In the example below, I created a collection status "Ready to upgrade with WU Driver in HR," which is based on my HR collection.
This integration turns Upgrade Analytics into a really powerful tool. I also like the fact that admins who plan, verify, and test upgrades can mark computers as ready for upgrade without having access to the Configuration Manager console. SCCM admins don't have to manually configure the upgrades because everything is automated.
Let's see how we can integrate Windows Upgrade Analytics ino Configuration Manager 1610. To start with, we need an Operations Management Suite (OMS) Workspace with Upgrade Analytics up and running. Our Configuration Manager site must have version 1610 or later installed. Next, we have to execute the following steps.
- Create an application in Azure AD that Configuration Manager can use to access the OMS workspace and ensure that Upgrade Analytics is active.
- Grant permissions to the Resource Group that the OMS workspace uses for our newly created Azure AD application.
- Configure the integration with Upgrade Analytics in the Configuration Manager console.
Start by launching https://manage.windowsazure.com where you will create an application and grant permissions to access the OMS workspace that Configuration Manager can use.
After you log into the Azure Management Portal, you have to navigate to Active Directory and select Applications. Now click Add as shown in the screenshot below.
Then you select the kind of application you want to create. For this purpose, you have to choose Add an application my organization is developing.
Then you give the application a name.
Next you have to specify two URLs that are actually never used; so you can basically enter any URL here.
After you create the application, you can now generate a key that can be used by Configuration Manager together with the Client ID to access the Windows Upgrade Analytics data. Select your newly created application and click Configure.
Next select the duration to determine how long the key will be valid.
After you select lifetime, the key will be generated and becomes visible after you click Save.
You now have to take note of the Client ID and the key. Note that the key will disappear once you leave this view. If you missed copying the key, you will have to create a new one.
You can now proceed to the Resource Group where the OMS Workspace that we use for Upgrade Analytics lives. Next select Access control (IAM) and then click Add.
Now click the Contributor role.
Next, select the name of the Azure AD application that you created earlier and grant the permission that allows the application to communicate with Upgrade Analytics (in our example, "WindowsUpgrade Analytics").
Your application now has the correct permissions to access the Resource Group and the OMS Workspace because the permissions are inherited from the Resource Group. In the next step you have to configure the integration with Configuration Manager.
In the Configuration Manager console under Administration > Cloud services > Upgrade Analytics Connector, select Create Connection to Upgrade Analytics.
Now click Next.
After that, you need to enter the Tenant. In my example, it is my MSDN subscription. You also have to specify the Client ID and the Client secret key that you copied earlier. Next click Verify to ensure that the information entered is correct.
You will now be prompted to select your subscription if the Client ID and the corresponding Client secret key have permission to access more than one OMS Workspace. Make sure to select the correct one here.
The connector is now configured. Note that downloading the data can take a while. You can follow progress in the DMPDownloader.log log file in the Configuration Manager Site server. You should see the lines from the screenshot below when SCCM synchronizes with Upgrade Analytics.
The Upgrade Analytics view in the Configuration Manager console should now be updated and you can start creating collections based on upgrade readiness.
Note that that the five collections that are pre-listed in the collection dropdown menu are those collections that contain most of the members in the site.