When using System Center Configuration Manager current branch Build 1610, you can extend it to OMS and you don’t need the OMS portal or the Classic portal. All from the Azure Resource Manager portal.
When opening the SCCM Manager it maybe that the OMS Connector option is not available, This connector is currently in preview and therefore you need to enable this option by hand. All the SCCM servers need to have a OMS Agent (at least the service connection point site system role Server)
In the Option can be enabled in Consent to Use Pre-Release Features.
Navigate to the Administration workspace in your Config Manager console, expand Site Configuration and select Sites.
Click on the Hierarchy Settings tab at the top of your screen.
select the General tab, and read the disclaimer under the Consent to use Pre-Release features.
After that You need to enable the feature in update and servicing. Right Click and turn it on.
Close and open the Management console and the option is there.
But before we can use this we need to configure the Web Api in Azure Resource Manager.
Create a New APP Pick a name and Sign-on URL as we are not using the url it does not Mather what name it is.
When created we can change some properties like a Custom Logo
Placing a custom logo is not needed but it looks nice when you search the app
Next Step is creating a KEY for the APP SCCM is using this key to connect to OMS.
Just choose a Name and a valid certificate expire date and a value and check save else the key is not saved.
Now to give the application the proper permissions in OMS we need to give the APP rights on the Resource Group where OMS based.
Go to the OMS resource group and pick Access Control IAM and add a new USER.
Select the Contributor Role and add this to the Just create application.
Now the Azure part is ready the next step is Creating the Connector in SCCM.
In the Cloud Services open the OMS connection Click on “Create connection to Operations Management Suite”
Now you’ll need to enter the details of your Azure AD tenant (The name) and the Client ID and Key from the Azure AD Application created previously then click Verify to ensure the details are correct and finally click Next.
The Tenant is your Tenant azure Account.
the Application ID is the Client ID
and the Client Secret is the Key that you created.
If you are using the Classic portal you should use the Client ID
With this we are almost ready just pick the groups that you want to populated in the OMS site.
Selecting the Groups and you are ready. In the OMS site you can see the SCCM option connected.
It could take some time to connect to all the groups. and only Groups with an agent are connected to azure so empty groups will not be used or seen in OMS. the connector runs every 6 hours so just wait.
Type=ComputerGroup (GroupSource=”SCCM”) | measure count() by Group
As I just set this up I did not have any results. and this is also the option for a Part 2 SCCM with OMS. But with the results you can create a custom dashboard to show the status.
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w