How to add a normal SCOM-agent as a ressource-pool-member

Sandro D'Incà 226 Reputation points
2023-03-02T09:20:12.47+00:00

hi everyone

we are using a simple scom-infrastructure with one management-server (no HA-features or additional management-servers)

a 3rd-party-management-pack's recommendation is, to add additional SCOM-agents to a ressource-pool to reduce high workloads on the management-server.

kevin holman wrote a great article about ressource-pools:

https://kevinholman.com/2016/11/21/understanding-scom-resource-pools/

and at the end of the article is also mentioned to add SCOM-agent to a ressource-pool:

If you want to play with adding AGENTS as a resource pool member or observer (not supported) then simply change “Get-SCOMManagementServer” above – to “Get-SCOMAgent”

does someone already done this before? any experiences? i'm a bit affraid of just adding a normal SCOM-agent to a ressource pool because of possible problems with distributed runas-accounts / profiles / unsufficient rights to start agent-tasks / impacts to other management-packs.

and if we add an additional agent in a ressource-pool, will future workloads automatically splitted to both pool-members?

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,419 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. SChalakov 10,266 Reputation points MVP
    2023-03-08T15:01:23.89+00:00

    Hi Sandro D'Incà

    I would not recommend doing that, I have not done it, but I know enough not to try it. Here are my considerations:

    • the first and most important would be, like Kevin says, it is "not supported". This means that you cannot open a case and your support request would be declined if this actions leads to major issues.
    • As Kevin mentioned a resource pool helps

    To provide a mechanism for high availability of agentless/remote workflows, such as Unix/Linux, Network, and URL monitoring, among others.

    This being said, having an gent in your resource pool can cause some workflows to fail simopley bcasue of isssue with this particular agent.

    About your question:

    If we add an additional agent in a ressource-pool, will future workloads automatically splitted to both pool-members?

    Yes, if those are agentless/remote workflows, targeted at Ressource pools, instead of targeted to a dedicated management server (example most of the workflows, running on Windows agents). All the agentless/remote workflows are targted to a ressource pools and as such those will be distributed amongst the members of a resource pool.

    I hope i could help you with that!

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
    Regards
    Stoyan Chalakov

    0 comments