System Center Operations Manager 2007 considers an object that contains a wildcard string to be a member of the group when a group uses a wildcard inclusion formula that targets a principal name

This article has been archived. It is offered "as is" and will no longer be updated.
When you create a group that uses a wildcard inclusion formula that targets a principal name in System Center Operations Manager 2007, System Center Operations Manager considers a computer object that contains the wildcard string in the principal name to be a member of the group. For example, you may use the following dynamic group inclusion formula:
( Object is Windows Computer AND ( Principal Name Matches wildcard is* ) AND True )
This group includes the following members:
This problem occurs because System Center Operations Manager translates the wildcard syntax for the regular expression as follows:
O* --> O.*
This expression matches any string that conatins at least one O. Additionally, this expression is case-sensitive.

A case-insensitive regular expression resembles the following:
To work around this problem, select the Matches Regular Expression match policy in the Computer Name field so that you use ^[Oo] instead of O*.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 969573 - Last Review: 01/15/2015 02:38:35 - Revision: 1.0

Microsoft System Center Operations Manager 2007

  • kbnosurvey kbarchive kbtshoot kbexpertiseinter kbsurveynew kbprb KB969573
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)