Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring workflows cannot be directed to specific Management Servers or agents #9

Open
gleversluis opened this issue Jun 28, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@gleversluis
Copy link

The MP uses a template, in which the initial discovery is targeted at the Microsoft.SystemCenter.RootManagementServer class. This class has been obsolete since SCOM 2012.
However, this choice of target makes it impossible to control where the monitoring workflows run. That can be remedied by adding a Resource Pool and using that as the discovery target. Directing the workflows is then done simply by populating that resource pool with specific Management Servers. The code for his is not very complicated; I'd be happy to help if needed.

@mikenelson-io mikenelson-io added the bug Something isn't working label Jun 29, 2021
@mikenelson-io
Copy link
Contributor

Thanks for this & thank you for the offer to assist! I have passed it on to engineering with a link to the issue. I'll follow up with them to ensure they look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants