3 votes1 comment · General Operations Manager Feedback » Other Management Packs · Flag idea as inappropriate… · Admin →Tyson Paul commented
Source is the instance of the targeted class for the workflow. The Path is the hosting path; the class that hosts the targeted class. This might seem like a flagrant plug (sortof) but there is a tool to generate a visual graph for SCOM class taxonomy which includes discovery and hosting relationships here: https://blogs.msdn.microsoft.com/tysonpaul/2018/08/06/scomhelper-powershell-module-a-scom-admins-best-friend/
87 votes8 comments · General Operations Manager Feedback » Administration · Flag idea as inappropriate… · Admin →Tyson Paul shared this idea ·
3 votes1 comment · General Operations Manager Feedback » Administration · Flag idea as inappropriate… · Admin →Tyson Paul commented
I would love to see your description of the issue expanded with more specific scenarios in which more columns are needed. We all know there are numerous screens where more columns are needed but if you itemize a larger list I think this idea would get more traction. I don't know if it's possible to revise your suggestion once it's posted. Maybe revise the title as well. Maybe something like: "Path, MP, Class Columns Needed in Numerous Screens" and then list those screens/areas. Examples:
- Groups: Add column for MP (where group is defined)
- Group Explicit Members: Only the DisplayName of classes appear. There are many, many duplicate class names and it's nearly impossible to select the correct one. Add columns for MP and class Name.
- Performance View: when adding specific rules to a perf view only the DisplayName of the rules appear. Add columns for Name and MP.
44 votes2 comments · General Operations Manager Feedback » Administration · Flag idea as inappropriate… · Admin →Tyson Paul supported this idea ·