I suggest you ...

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

Expected Behavior
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

Analysis
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.

97 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Holger shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base