SCOM R2 agent removed but stays in Computer field under monitoring
We have servers that needs retired, so I uninstall from the console and the servers disappear from the agent managed view. But if you look under computers in the monitoring view the server is still there. When we were on SP1 we had a similar issue and i contacted MS and we got a script to clear it out out of the database (Orphaned Servers)now that we are on R2 it seems the script doesnt work because it can not locate the name..any suggestion on thisagent manage and computers are off by 22 when they should be the same
December 10th, 2009 8:34pm
Is it possible to delete them in one of the administration panes?do you see them in pending or so?Greetz,
Arie de Haan
MVP SCOM
This posting is provide "AS IS" with no guarantees, warranties, rigths etc.
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2009 1:33am
We have servers that needs retired, so I uninstall from the console and the servers disappear from the agent managed view. But if you look under computers in the monitoring view the server is still there. When we were on SP1 we had a similar issue and i contacted MS and we got a script to clear it out out of the database (Orphaned Servers)now that we are on R2 it seems the script doesnt work because it can not locate the name..any suggestion on thisagent manage and computers are off by 22 when they should be the same
Computers should be left in the "Windows Computers" view for up to 3 days after you delete the agent - this is by design.You should not manually delete anything in the OpsMgr databases... as "orphaned objects" are exceedingly rare.... and manual deletes are unsupported.If you still see a Computer showing up - even after 3 days - then there is still a discovery associated with it.To find the discovery -
To determine what discoveries are still associated with a computer – helpful in finding old stale computer objects in the console that are no longer agent managed, or desired.
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 '%ComputerName%'Run this query - and find the discovery still associate with that computer.
December 22nd, 2009 2:59am
Hi,
Take a look at
http://www.techlog.org/archive/2008/07/29/stale_computer_objects_in_oper
Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se
Page not found :-(Tiago Lock
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 9:02pm
We have servers that needs retired, so I uninstall from the console and the servers disappear from the agent managed view. But if you look under computers in the monitoring view the server is still there. When we were on SP1 we had a similar issue
and i contacted MS and we got a script to clear it out out of the database (Orphaned Servers)
now that we are on R2 it seems the script doesnt work because it can not locate the name..any suggestion on this
agent manage and computers are off by 22 when they should be the same
Computers should be left in the "Windows Computers" view for up to 3 days after you delete the agent - this is by design.
You should not manually delete anything in the OpsMgr databases... as "orphaned objects" are exceedingly rare.... and manual deletes are unsupported.
If you still see a Computer showing up - even after 3 days - then there is still a discovery associated with it.
To find the discovery -
To determine what discoveries are still associated with a computer – helpful in finding old stale computer objects in the console that are no longer agent managed, or desired.
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 '%ComputerName%'
Run this query - and find the discovery still associate with that computer.
Hello,
I did run this query but none os my "stale" computers are there. Ther's another way supported ?
Thanks for your time.Tiago Lock
June 27th, 2011 9:03pm
I am having this problem with one computer, which I removed from SCOM and would like to re-add (still in a testing phase). I cannot install the agent because I get an error telling me that there is already an agent installation active. If I run the above
query, I get a list of discoveries associated with the removed computer. What should I do with them? Or do I just need to wait until the grooming happens?
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2011 10:33am