I ran into an interesting issue with a project I am working on. In order to offload some processor cycles from the RMS in SCOM 2007, a seperate server was provisioned to host all 3rd party management packs which run network discoveries, etc.
In order to keep all of the collected data to date, I installed the Jalasoft NMS (Network Manager Server) in parallel on the other server, started it and then migrated the devices. In order to complete the role move, I stopped the NMS server on the RMS and disabled the service.
Interestingly enough, after leaving plenty of time for the topolgy change to be discovered (2 days), the Network Manager Server status still shows up as healthy for both systems!
Jalasoft has confirmed this to be a bug in their product. Here is the source information:
Hello Brad,
After consulting with our Quality Engineering Manager, this bug was internally reported on 01-18-07; please feel free to reference it as follows:
BUGID: 4316
Title: An uninstalled or disabled NMS is not removed from the Xian Database
Date: 01-18-07
Description:
When a Xian NMS service is removed or disabled, its related information is not removed from the Xian database; therefore, the service is still listed on the Xian and Operations Manager consoles.
Severity: low
Priority: medium
Should you have any other questions/requests, please do not hesitate to contact us.