Hello, I’m not sure how this happened, but we have 5 Windows Computer objects that do not appear in any of the Administration\Device Management nodes (ex.: Agent Managed, Agentless Managed, etc.) As such, I am not quite sure as to how I should proceed to purge them from our Management Group. I suspect that I’ll have to issue a SQL DELETE command against the OpsMgr DB, but need some guidance. Any ideas? Thanks, Larry

doing the SQL delete thing is the absolute LAST thing you should do. Try the following first. close the opsmgr console, modify the shortcut that starts it to clear the opsmgr cache by adding -clearcache to the command line. also consider recycling the opsmgr services on the RMS. Did the 5 windows computer objects have agents installed on them? Scott Moss MVP (Operations Manager) | President - System Center Virtual Users Group | Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you!

Hello Scott, I understand your point regarding playing in the database; I share that opinion. I already updated the shortcut with the /clearcache switch. Recycling the OpsMgr services on the RMS did not resolve the problem. :( The 5 servers are part of a Management Group that is out of our administrative control. Any other suggestions? Larry

Hi, Did you see any error/event log regarding this issue. To troubleshoot this kind of issue, please refer to the following article: Fixing troubled agents http://blogs.technet.com/b/kevinholman/archive/2009/10/01/fixing-troubled-agents.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello Vivian, I went through the document, which mainly covers agent-related issues. The problem is that these 5 servers do not appear in any of the agent views in the console. Depite this, they appear as Windows Computer objects ("Not monitored") in views scoped on that class. Though these servers do exist, they are not part of my Management Group (MG), much less our AD domain. Furthermor, the OpsMgr admin of the MG hosting them maintains that they are reporting just fine to his MG. I am thinking that maybe they were discovered via a Proxy Agent out there, not unlike virtual cluster servers are discovered. If so, how could I determine which proxy agent discovered them? Thanks, Larry

Hello Vivian, I went through the document, which mainly covers agent-related issues. The problem is that these 5 servers do not appear in any of the agent views in the console. Depite this, they appear as Windows Computer objects ("Not monitored") in views scoped on that class. Though these servers do exist, they are not part of my Management Group (MG), much less our AD domain. Furthermor, the OpsMgr admin of the MG hosting them maintains that they are reporting just fine to his MG. I am thinking that maybe they were discovered via a Proxy Agent out there, not unlike virtual cluster servers are discovered. If so, how could I determine which proxy agent discovered them? Thanks, Larry

They were probably discovered at some point by a gateway. They would not be in a computer view if they aren't discovered. You may want to try the delete-disabled trick - since they seem to be disabled for monitoring in some way. since they aren't monitored, is there really any issue?Microsoft Corporation

They were probably discovered at some point by a gateway. They would not be in a computer view if they aren't discovered. You may want to try the delete-disabled trick - since they seem to be disabled for monitoring in some way. since they aren't monitored, is there really any issue?Microsoft Corporation

Hello Dan, I agree with your comment about discovery (i.e. they were discovered at some point in the past; maybe the admin of the other MG initially pointed them to my MG by mistake). By "delete-disabled trick", did you mean running the Remove-DisabledMonitoringObject cmdlet? If so, I can report that this did not work. My understanding is that this cmdlet requires that a specific discovery override exists for each object disabling its discovery. I've used this trick before, but in this particular case, I would need to find the discovery for the Windows Computer object. Where can I find this beast? I've created groups that we use to determine the the # of physical versus virtual computers in our environment. Unfortunately, these "ghost" objects end up skewing the statistics, and simply lead to confusion for the Windows support group when they use views scoped on Windows Computer. Thanks, Larry

Hello Dan, I agree with your comment about discovery (i.e. they were discovered at some point in the past; maybe the admin of the other MG initially pointed them to my MG by mistake). By "delete-disabled trick", did you mean running the Remove-DisabledMonitoringObject cmdlet? If so, I can report that this did not work. My understanding is that this cmdlet requires that a specific discovery override exists for each object disabling its discovery. I've used this trick before, but in this particular case, I would need to find the discovery for the Windows Computer object. Where can I find this beast? I've created groups that we use to determine the the # of physical versus virtual computers in our environment. Unfortunately, these "ghost" objects end up skewing the statistics, and simply lead to confusion for the Windows support group when they use views scoped on Windows Computer. Thanks, Larry

window computer object is created when you click "approve agent" or automatically if option "AutoApprove" is set.

Pavel, Agreed, though once approved, they would normally appear in one of the views in the Administration\Device Management space. The problem is that I cannot find them there, and therefore cannot Delete them from the Management Group. Larry

Hello, Happy day! It turns out that the AD-related AD Topology Discovery discovery (target: RMS) was responsible for the discovery of the superfluous Windows Computer objects. Setting its DiscoverAgentOnly override to True solved the problem. For those who are interested, here is the SQL that identified the discovery associated with a particular object: SELECT BME.FullName, DS.DiscoveryRuleID, D.DiscoveryName FROM typedmanagedentity TME Join BaseManagedEntity BME ON TME.BaseManagedEntityId = BME.BaseManagedEntityId JOIN DiscoverySourceToTypedManagedEntity DSTME ON TME.TypedManagedEntityID = DSTME.TypedManagedEntityID JOIN DiscoverySource DS ON DS.DiscoverySourceID = DSTME.DiscoverySourceID JOIN Discovery D ON DS.DiscoveryRuleID=D.DiscoveryID WHERE BME.Fullname LIKE '%<NameOfObject>%' Enjoy, Larry