All issues have been fixed.

You could now use wmi-config.xml for credentials, but you could also override the values (if you want) by adding the proper parameters in the detector configuration.

Committed on revision 1296cc897a23cc23866b34d84a52b51fafef301d for 1.10 and cherry-picked on revision 54ffd3cac3262082c57582bedad10f83b0970a73 for 1.8

Even after adding the login/password in provisioning parameters (bad for
security... should use wmi-config.xml), the service is detected but not monitored.

So, that's another bug: serviceName parameter is ignored and 'WMI' is used
instead. But since my poller service name is 'WMI-Service-mcafee', it won't be
polled...

Sad... I'm sure that's a 2 lines fix in the code.

In WmiDetector.java in onInit() we have:
setServiceName(PROTOCOL_NAME);

2nd bug:

I get the following error:
2010-11-15 16:14:29,256 INFO [scanExecutor-4] IpInterfaceScan$1: Exception occurred while trying to detect service WMI on address 127.0.0.1
java.lang.IllegalArgumentException: Authentication information was not supplied. [0x00001010]
at org.jinterop.dcom.core.JISession.createSession(JISession.java:421)
at org.opennms.protocols.wmi.WmiClient.connect(WmiClient.java:227)
at org.opennms.protocols.wmi.WmiManager.init(WmiManager.java:258)
at org.opennms.netmgt.provision.detector.wmi.WmiDetector.isServer(WmiDetector.java:105)

If I look at the WmiDetector's code, it seems that the WMI config file contraining credentials is not read.

With ONMS 1.8.5 there's a bug when the 'timeout' param is missin:

2010-11-15 16:07:02,763 DEBUG [scanExecutor-5] SyncTask$1: Exception occurred
executing task org.opennms.core.tasks.TaskBuilder$1 <at> b5459
java.lang.IllegalStateException: ServiceName and/or timeout of 0 is invalid.
ServiceName can't be null and timeout must be > 0

Adding the 'timeout' is a work around.