Archive for the ‘OMS’ Category

Connect System Center Configuration Manager to OMS sync device collection data #MSOMS #sysctr #Azure #ARM   Leave a comment

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)

image image

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.

image

Close and open the Management console and the option is there.

image

But before we can use this we need to configure the Web Api in Azure Resource Manager.

Logon to the Azure Portal and go the the Azure Active Directory and check the App registrations and ADD a new APP
image

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.

image

When created we can change some properties like a Custom Logo

image

Placing a custom logo is not needed but it looks nice when you search the app Winking smile

image

Next Step is creating a KEY for the APP SCCM is using this key to connect to OMS.

image image

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.

imageimage

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.

image

Now the Azure part is ready the next step is Creating the Connector in SCCM.

image

In the Cloud Services open the OMS connection Click on “Create connection to Operations Management Suite”

image

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.

image 

If you are using the Classic portal you should use the Client ID

imageimage

With this we are almost ready just pick the groups that you want to populated in the OMS site.

imageimageimage

Selecting the Groups and you are ready. In the OMS site you can see the SCCM option connected.

image

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

Type=ComputerGroup GroupSource=SCCM

image

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.

image

 

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

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog

Posted March 27, 2017 by Robert Smit [MVP] in OMS

Tagged with

Install the OMS agent using GPO automation with Powershell OMS WorkSpace lookup #MSOMS #Azure   1 comment

Suppose you want to deploy the OMS ( Microsoft Operations Management Suite ) Agent but you don’t want to do this by hand. Well Supposed you could run a Powershell script that installs the Agent. But in this case it is about deployments and a lot of VM’s are getting deployed and removed and you don’t want to put the Agent in the Template VM. I recently had to build a poor man’s lightweight deployment solution. As there is noting yet in the Cloud I used the good Old Active Directory.

https://www.microsoft.com/en-us/cloud-platform/operations-management-suite

Microsoft Operations Management Suite

So Old Skool deployment by GPO as you could use this for any file or solution. and yes Powershell could also be handy but in this case the VM’s can be remote controlled as the remote Port is firewalled.

https://robertsmit.wordpress.com/

Create a GPO in my case “ Deploy-OMS”

Edit the GPO

image

and Go to the Computer Settings right Click on the folder choose New and folder 

image I use Update the folder Pick a name

Now the GPO Creates a folder on all targeted Machines I did place this GPO on top be carful with that!

 

image

Next same as on the Folder new file

image

In this new file I’ll use the Source and destination keep in mind the destination is on the machine where the agent needs to be.

imageimage

Do this for both files or if you have more then do this per file and If you want to limited this a bit there a a few options to do that.

the Apply once option and the Item-Level targeting based on your Query the GPO will Execute or Not. (this is not needed but it is optional )

image

As I used a CMD batch file you need to create one with your task

I used this one liner to install the OMS Agent use your own key and save this file as a CMD file

"c:\Package-deploy\MMASetup-AMD64.exe" /C:"setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_ID=d69d8969-1111-4586-80f0-4a11bc111199c OPINSIGHTS_WORKSPACE_KEY=3zNTcggsfsfsdgjhkldsaOyQ0/dgMwsbdtrgQVPXqu== AcceptEndUserLicenseAgreement=1"

 

image image

In case you can’t find the Workspace ID check your portal and go to the settings Dashboard. and get your info.

image

But In case you want to do a little bit of Powershell.  OMS Powershell

First let me check if the Modules are installed if not Install the modules.

 

Find-Module AzureRM.OperationalInsights | Install-Module
Install-Module AzureRM.OperationalInsights -Scope CurrentUser
Get-Module AzureRm.OperationalInsights

https://robertsmit.wordpress.com/

Next we need to login to your Subscription

Login-AzureRmAccount
Get-AzureRmSubscription

If you have Multiple subscriptions pick the right one

Select-AzureRmSubscription –SubscriptionId

#Get your WorkSpace ID
Get-AzureRmOperationalInsightsWorkspace |select Name,ResourceGroupName,CustomerId

image

I use these two as variable

$ResourceGroupName = "OI-Default-East-US"
$WorkSpaceName = "clustermvp"

Now we get the key that we needed.

Get-AzureRmOperationalInsightsWorkspaceSharedKeys -ResourceGroupName $ResourceGroupName -Name $WorkSpaceName

image

See how easy Powershell is just take baby steps find the info and you will learn every day step by step.

 

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

  • Twitter

  • %d bloggers like this: