WOL fails when using proxy to wake machines on different subnet.

Target device that resides on a subnet other than where the server resides is unable to be woken up using the WOL proxy.

The loader-messages.log on the ZCM server contains the following stack trace:

[Loader.QueueRunner] [] [java.lang.NullPointerException
          at com.novell.zenworks.loader.modules.SubnetMembers.getQuickTaskData(SubnetMembers.java:202)
          at com.novell.zenworks.loader.modules.WakeOnLANHandler.doWOLProxyTask(WakeOnLANHandler.java:420)
          at com.novell.zenworks.loader.modules.WakeOnLANHandler.processAction(WakeOnLANHandler.java:316)
          at com.novell.zenworks.loader.modules.queue.runner.QueueThreadWorker.processAction(QueueThreadWorker.java:208)
          at com.novell.zenworks.loader.modules.queue.runner.QueueThreadWorker.run(QueueThreadWorker.java:139)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
         at java.lang.Thread.run(Thread.java:595)

This is fixed in version 10.3 - see KB 7005455 "ZENworks Configuration Management SP3 (10.3) - update information and list of fixes" which can be found at https://www.novell.com/support