Something to keep in mind when you're rolling out System Center Operations Manager R2 is how the Agents work when you're dealing with Unix and Linux servers.
On the Windows side of things when you deploy an agent to the server, you are in effect deploying a Health Service that will run the workflows related to the providers that target that machine. So if you deploy an agent, and then discover SQL Server on the machine, most of the work in terms of gathering information from that SQL Server instance will be done on the host machine itself. This helps OpsMgr scale out in large environments and works because the calls to gather information is generally script or WMI based.
For Unix and Linux agents, this changes. The Unix and Linux agent is just a CIM server, it's sitting around waiting for queries to be sent from a Management Server, it looks up what class is being requested, maps that to a provider and returns the data that the provider serves up.
The big difference here is that the Unix and Linux agent does not handle workflows, the management server must be able to handle all of the workflows being used to gather the information. So for the Unix/Linux side of things, you need to ensure that you have enough Management Servers to handle the amount of data collected and you have properly balanced the Unix/Linux servers across your Management Servers.
This is something to be aware of when you're planning out how you are going to pull your Unix/Linux infrastructure into OpsMgr.
Comments