Solved

Problem adding computers to group

Posted on 2008-06-11
1
266 Views
Last Modified: 2008-06-16
I have created some groups, and then wanted to add some servers to these groups. Most of them I had no problem adding, but some groups I get this error:

I dont really know what is causing this.

For some groups I tried renaming them, and suddenly I could add the servers, but for others this solution doesnt work
Note:  The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.
 
: Verification failed with [1] errors:
-------------------------------------------------------
Error 1:
: Failed to verify Discovery [UINameSpace140e4aac3df244f4ba437150a3d5b649.Group.DiscoveryRule]
Failed to verify referenced module : ID=GroupPopulationDataSourceInvalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
-------------------------------------------------------
 
Failed to verify Discovery [UINameSpace140e4aac3df244f4ba437150a3d5b649.Group.DiscoveryRule]Failed to verify referenced module : ID=GroupPopulationDataSourceInvalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Failed to verify Discovery [UINameSpace140e4aac3df244f4ba437150a3d5b649.Group.DiscoveryRule]
Failed to verify referenced module : ID=GroupPopulationDataSourceInvalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Failed to verify referenced module : ID=GroupPopulationDataSource
Invalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Invalid configuration specified for Module [GroupPopulationDataSource]
Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$

Open in new window

0
Comment
Question by:mhjortby
1 Comment
 
LVL 5

Accepted Solution

by:
madhusk earned 500 total points
ID: 21759946
Does the account used for discovery have appropriate permissions on the target computer?


Open a command window with the "Run As" option using the account used for discovery, normally this is the MOM server action account.  
Use the command "net view ComputerName to verify that the account can connect using the API NetworkStationGetInfo.  This command may return the result, "There are no entries in the list."  This simply means that, the machine does not have any publicly visible shares.  
If the result is "Access denied.", then the account used does not have permission to contact the machine.
If the result is The command completed successfully. then the computer is properly configured for discovery.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Dentrix G4 1 86
Independent domain networks for setup 6 123
Windows server 2003 bootable iso 9 273
RAID / SATA Drivers for Intel Server Board SE7525GP2 and SE7320SP2 4 111
The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server. We would only need to create and run scripts using thi…
by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

761 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question