I have reproduced this issue in all my OM12 test environments and see this happening at a customers location as well.
There are two workarounds to ‘deal’ with this bug. The first is running the full blown OM12 Console. But sometimes that isn’t possible for some operators, based on various valid reasons. So the Web Console is their only interface to interact with OM12. This is where the second workaround comes in.
Simply follow these six steps:
- Log on to the OM12 Console with admin permissions. Go to Administration and create a new MP with the name of the department requiring the Microsoft SharePoint Views in OM12;
- Give this name an underscore so it comes on top of the tree shown in the Monitoring pane;
- Go to Monitoring and right click on the name of the new MP you created in Step 1 > New > State View and copy these settings:
- Go to the second tab, Display and copy these settings:
- The new View will be saved now in the MP you created in Step 1.Test the View in the Web Console. It will work as intended:
- Don’t forget to assign this View to the proper User Roles as defined in your OM12 environment.
As stated in previous postings the SharePoint Server 2013 MP has some serious issues. Hopefully an update for this MP will be released containing fixes. Until then this is what we have to work with.