OMS Journey – Adding a Local Server As a Data Source To OMS

Now that I have a new OMS workspace, I need to add some data sources (AKA computers) to it, so I have some data.

I’ve recently rebuilt my home server with Windows Server 2016 so I want to add it as a source in OMS. To do this, I need to install the Microsoft Monitoring Agent on the server.

To get started, I navigate to my OMS workspace, in my case mickeygmms.portal.mms.microsoft.com.  On the left side of the screen, click the Settings icon.

 

image

 

In the settings aread, select Connected Sources | Windows Servers.  The click the Download Windows Agent (64 bit) link to download the OMS agent (also called the Microsoft Monitoring Agent). This downloads the MMASetup-AMD64.exe executable.

image

Make a note of the workspace ID and keys, as those will be needed as part of the install, the configure the agent to send data to the appropriate workspace.

I now need to run this executable on my home server. This is pretty much a click, click, click install.

image

image

image

 

The Microsot Monitoring Agent can be used to send data directly to OMS, or, if you are using System Center Operations Manager, can also be used to send data to SCOM as well.  I don’t have SCOM installed right now, so I’ll select Connect the agent to Azure Log Analytics (OMS).

 

image

 

Here is where you enter the workspace id and workspace key, so the agent knows what workspace to report back to.  The MMA can be multi-homed, so you can report back to up to four different OMS workspaces.

 

image

 

image

 

image

 

Click Finish to complete the installation.

Back in the OMS Dashboard, we can see a data source has been connected.

 

image

 

image

 

image

Right now the only thing being returned is a heartbeat message. I’ll show you how to change that in a future post.  But we have data!  We are on our way to monitoring our environment.

  • Add Your Comment