wmi mapper issues

[Jason Cordes_2]

Is anybody out there using wbem to track any of their windows systems? I have a few pc's loaded with win2k and win2k3 that I would like to have show up in the 'All Servers' listing without manually entering the info.

The behavior I am seeing is that if I stop and restart the Pegasus WMI Mapper service I can then run an identify task on a few of these systems and they will be identified and I am able to get configuration info via WMI. However, after 3 or 4 get identified then the process stops working, no more systems can be identified, I am no longer able to get configuration info and if a another Identify task is run on these systems or a discovery task runs then the systems that were identified go back into an Unknown state. I can restart the Pegasus WMI Mapper service and it will work again for a few systems.

I am running HP SIM 5.0 on a dl380g2 running Win2k3. Any feedback on this would be appreciated.

Thank you.

[Wiehann Kotze_1]

I have a similar issue where HP SIM 5.0 successfully identifies my systems (using WMI/WBEM). Then as days progress more and more systems suddenly show as unmanaged. Rebooting the SIM box and rerunning discovery normally fixes the problem, but then it just starts again.

I see there are numerous people who have a similar problem, is there a solution out there?

[Nicholas J Williams]

I'm also experiencing the same issue. Would be keen to know if there is a fix/workaround. Restarting the service also has the same effect, works for a few servers then dies.

Thanks
Nicholas