Deploy OMS Agent with ConfigMgr

I have recently been looking at the Microsoft Operations Management Suite and decided to deploy it throughout my datacentre.  First you’ll need to sign up, to start with go for the free version.  This limits you to a certain amount of data per month and only 7 days data retentions. Other plans are available at a cost.

Once you’ve signed up you can start by adding solutions.  I have added in all a few, I went for AD Assessment, Capacity Planning, Malware Assessment and System Update Assessment.  Once you’ve added in your chosen solutions you move on to step two which is to connect your data source(s).  This is the step I’m going to concentrate on in this blog post. It is my intention to deploy the agent available to us through SCCM.  Here’s how I did It.  First, within the Operations Management Suite console, we select step 2 Connect a data source and then in the left pane we can see we can now download our architecture specific agents and we are shown our unique workspace ID and Primary key (blacked out on my screen shot below)

image

I downloaded the 64 bit agent to its own folder within a sources directory (this sources folder is also a network share) on my ConfigMgr server and then proceeded to manually install it.  Notice this is a .exe file?  Well don’t worry, there is a silent install command I’ll show you. I ensure during installation that I select the option to Connect the agent to Microsoft Azure Operational Insights and specify my WorkspaceID and primary key from the screen shot above.

image

I can now see that I have a new program installed (by looking in Programs and Features within control panel) called Microsoft Monitoring Agent.  I now need to look within the registry to find its uninstall key – the reason for this will become clear when we add the application into ConfigMgr ready to deploy.

I open up the registry and browse to the following location HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and notice that the uninstall key for Microsoft Monitoring Agent resides under the GUID of {E854571C-3C01-4128-99B8-52512F44E5E9}.

image

Excellent, right now I fire up ConfigMgr and create a new application so browse to Software Library \ Overview \ Application Management \ Applications right click and new application.

image

Select to Manually specify the application information then Next,

image

Give it a name and select Next,

image

Select Next on the Specify the Configuration manager Application Catalog entry page and on the Configure deployment types and the priority in which they will be applied for this application page, click on the Add… button.

Again, specify you wish to Manually specify the deployment type information and elect Next,

image

Give it a name and select Next.   Specify your server share in the content location and then use this code for the Installation Program: option

MMASetup-AMD64.exe /C:"setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_ID=<your workspace id> OPINSIGHTS_WORKSPACE_KEY=<your workspace key> AcceptEndUserLicenseAgreement=1"

..replacing the two highlighted sections with your own individual WorkspaceIDs and Keys, like this:

image

Next we need to specify a Detection Method, so from the Specify how this deployment type is detected I click on Add Clause…

image

I select a Setting Type of Registry and then click Browse…

image

I drill down to the registry key we found earlier (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{E854571C-3C01-4128-99B8-52512F44E5E9}) and click OK.

image

I click Next to move onto the Specify the user experience settings for the application page and chose the ones I want, you may want different options here so I’ll let you decide on these.  Finally, I didn't set any Requirements or Dependencies for this application so the rest of the wizard id Next, Next Finish.

Once the application is created don’ forget to distribute the content and then deploy it to the collection of your choice.  It wont be long before you see your servers populating in the console and now all you have to do is decide on whether the free version of OMS is enough for your business needs. That and setting up your logs for the final step.

Hope this has helped you & thanks for reading.

Jonathan.