Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4629
  • Last Modified:

Orphaned systems in SCOM 2007 R2 monitoring window

I have a number of obsolete servers that were removed from our network before I had a chance to uninstall the SCOM agent via the SCOM console.  I have deleted these machines from within the Administration/Agent Managed window, however they remain within the Monitoring/Computers window with a greyed-out critical state.  I've searched for a way to remove these ophaned objects, but so far nothing has worked.  I do seem to recall having read an article that indicated that this may happen if there are unclosed alerts or events that reference the machine object.  However, I have can't find any open alerts or events for these machines.  Anyone know how to get rid of these pesky dead machines from SCOM?
0
UrHuckleberry
Asked:
UrHuckleberry
1 Solution
 
ssiimmpplleeCommented:
You will need to remove the objects from the Database. This is fairly easy to do. Here are the steps that i use when i have this issue.

System Center Operations Manager 2007 stores all "entities" it "manages" in the BaseManagedEntity table in the Operational database (named "OperationsManager", by default). This is the place where we will be manually telling SCOM that this computer does not exist anymore. There's a column called "IsDeleted" that stores if the agent was removed.


1. Connect to the SCOM SQL server and open SQL Management studio
2. Right click on OperationsManager database and select new query
3. Run the following query in the right window  to see the status of ALL computers in SCOM
 

SELECT * FROM dbo.[BasemanagedEntity] where FullName Like '%Windows.Computer%'


4. To see the status of a specific computer in SCOM (replace the text "fqdn" with the server name)

SELECT * FROM dbo.[BasemanagedEntity] where FullName Like '%Windows.Computer%' and Name Like '%FQDN.of.my.computer%'
 

 
5. In the results scroll to the right to find the "IsDeleted" column. 0(Zero) means the database does not know the computer has been deleted. If it is zero then we will run the next command to change it to 1 (one)

replace the text "fqdn" with the server name


UPDATE dbo.[BasemanagedEntity] SET IsDeleted = 1 where FullName Like '%Windows.Computer%' and Name Like '%FQDN.of.my.computer%'

 
 

Going back to the Operations Console to the Monitoring & Computer section, shows us that the computer does not show in the list already. It will still take some time before it really gets deleted in the database, but visually you are already set. (Do note that the machine and its child objects like disk and CPU are still there in the Data Warehouse. This will stay there until that expired there also; which is 360 days by default).

 

0
 
UrHuckleberryAuthor Commented:
Worked like a charm!  Thank you very much for sharing that with me!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

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.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now