Allow WOL across subnets without relay or allow the relay agent to
The old method of WOL in 7.2 and below was able to send packets across subnets. The new relay agent method cannot. If all machines are powered off in a subnet, then it is not possible to wake up the machines at all starting in version 8.0. I have had to resort to using another product for WOL scheduling. This feature was a nice selling point. I'm pretty sure the other suggestion was to have the option to use a relay.. not be forced to.
Eric Pagan
shared this idea
-
William Mullen
commented
Ideally, KACE should already know which network/subnet a device is on if the KACE agent is installed, and should automatically choose another device on that same subnet to issue the WoL packet to the targeted device. Having the direct/relay choice and create a label for it is confusing and bewildering. If any have used Faronics Deep Freeze, it's WoL implementation works similarly and is MUCH better and more dependable.
-
Andrew McNaughton
commented
Allegedly, there was a security issue that forced Quest's hand with this one. I think it was rushed. The so-called advanced schedule is rudimentary. No custom option. No weekdays option. It also seems to have limitations because when I asked it to send magic packets to all of our Windows devices it didn't work. It works with labels with smaller numbers of devices. This means we need more schedules. Combine that with the missing weekdays option and we've multiplied the number of schedules we'll need to create by a factor of 10. It's an admin nightmare.