Wake on Lan is working but Kace SMA doesn't see the agent as being connected
Our networking department replaced all the switches on campus and now I am working through Wake on Lan again.
Wake on Lan is working if I set it up on a schedule but even though I can remote into the computers using Windows RDP the Kace agent does not see them as connected or turned on.
When we go into a single computer in inventory and say Wake on Lan direct it never works.
Anyone know why the agent wouldn't see these computers as being turned on and why the Direct Wake on Lan wouldn't work but a scheduled one does?
Any help would be appreciated we have gone backwards with this feature not working and having to do sneakernet.
Thanks
Answers (2)
Are you using WOL with Choose Relay menu option? I suspect the schedule is configured to use a relay.
If you don't see the Choose Relay menu option, you need to upgrade your SMA.
Top Answer
This may be because of the way that a scheduled wake-on-lan works as opposed to an individual device action. I may be wrong but when you wake up a group of devices on a schedule it actually delivers the wake-on-lan packet via the agent to a device on the segment and wakes everything up from the inside of the segment. This was functionality that was changed I thin in version 9 or 10. It meant that ports did not need to be opened and switches did not need to be configured to pass the magic packet as the KACE agent bypassed all of that.
When you wake a machine via the device action, my guess is that it is sent out from the SMA to the target machine and if the infrastructure is not configured to pass the magic packets it will not work. the only way to prove that out is to see if a machine on the same segment as the SMA will wake up from a device action.
My guess is none of the new switches are enabled to pass magic wake-on-lan packages, so your device actions will fail.
