After Management Server removal, some orphaned objects remain
After the deletion of a management server according the description in https://technet.microsoft.com/en-us/library/hh456439(v=sc.12).aspx some objects will remain
Those objects can just get deleted through manual operations in the database. ==> Custom SP dbo.sp_RemoveObjectByTypedManagedEntityId
The Health Service Watcher Object always remains after deletion.
This behaviour is reproducible with SCOM 2012 R2 and SCOM 2016
The customer expects that if he strictly follows the step-by-step instructions to remove a management server from the management group, nothing should remain somewhere, neither in the database nore in the filesystem, registry or somewhere else
I reproduced the problematic behavior in two different environments with two different SCOM versions and the outcome was always the same, the Management Server Health Service Watcher Object always remains after deletion.
The remaining object leads to confusion at the customer because he is not sure if the MS is now deleted or not. Furthermore, it can no longer install MS with the same name as long as the orphaned object exists.
This seems to be a bug. We will look into this and update the thread.
Kevin Holman commented
This is VERY common and has been since SCOM 2007. I clean this up for my customers using this process. I talk about this bug here: https://blogs.technet.microsoft.com/kevinholman/2018/05/03/deleting-and-purging-data-from-the-scom-database/
It is a bug for sure. But it does not cause any harm. Messes up the health state views for customers who monitor those.