I'd like to create a state views for computers by matching on the first char of the principal name. Not sure exactly how to to this. If I do "with n% Principal Name" I get any server that has an n in the name, but I'd like to get just servers that start with n. Really I'd like to do a range, e.g. [nm]% but I'm not sure this works at all. The point of this is to reduce the load when I open the computers state view. We have over 3000 servers and the console takes way too long to open the view, go somewhere else, and oh now I got to go back and open a health explorer. I'd like to have 4 or 5 subsets of servers, e.g. [a-d], [e-i], etc. The assumption is that it would take less time to load, and the product would suck a little less. Would be nice to have a prompted health explorer launcher that doesn't insist on loading every object ever created before you can launch it.

I also notice if I do "with n Principal Name" I get the same exact results. What is the point of the % and the statement "SQL style wildcards are accepted" if they're not.

we also faced this issue, here is our connect suggestion. https://connect.microsoft.com/OpsMgr/feedback/details/681284/view-filter-is-using-sql-wildcard Posted by Microsoft on 8/13/2011 at 12:10 AM thanks for the feedback. this is not something we can change now as it could break other MPs that already depend on the existing behavior. Thanks, Vlad Joanovic | Program Management

we also faced this issue, here is our connect suggestion. https://connect.microsoft.com/OpsMgr/feedback/details/681284/view-filter-is-using-sql-wildcard Posted by Microsoft on 8/13/2011 at 12:10 AM thanks for the feedback. this is not something we can change now as it could break other MPs that already depend on the existing behavior. Thanks, Vlad Joanovic | Program Management Not surprised. Either this was not tested, as it obviously doesn't work, or because it breaks other MPs it's designed behavior. Just another example of shoddy workmanship with SCOM.

One solution here might be to define dynamic groups that have the group membership based on the Principal Name. Once you have your groups, then create views that target these groups. That should do what you want here. Let me know if you need more details on this, I just recently did something similar in my testing.Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

This article explains how wildcards are used in SCOM. http://blogs.technet.com/b/jonathanalmquist/archive/2010/10/13/regular-expression-syntax-in-scom-for-filtering-groups-monitor-elements-operational-views-notification-subscriptions-etc.aspx Scroll to the middle, where you see "Wildcards..."HTH, Jonathan Almquist - MSFT

This article explains how wildcards are used in SCOM. http://blogs.technet.com/b/jonathanalmquist/archive/2010/10/13/regular-expression-syntax-in-scom-for-filtering-groups-monitor-elements-operational-views-notification-subscriptions-etc.aspx Scroll to the middle, where you see "Wildcards..."HTH, Jonathan Almquist - MSFT

Jonathan, good article. the issue is that SCOM by default adds "%" at the begging and at the end of the pattern. this "by-design-won't-fix" issue deserves dedicated blog-post or KB article.