Better Wake-On-LAN implementation.
Have the K1000 send the WOL request to an Agent (on a PC that is already awake of course) on the same VLAN as the PC that you want to wake up. I need to be able to send WOL packets through VPN Tunnels and across VLANs. This would be a life saver!
This request is planned to be implemented in a release this calendar year
Andrew Curtis commented
Would love to see this implemented also. But given the propensity for Kace to vacillate on all the feature requests I am interested in I am not going to hold my breath. =/
Anytime soon would be great please!
Evan Clay commented
Elijah Case - "Would be great to be able to use our Replication clients as WOL relays." I second this. That's exactly what we need, as we currently have Replication clients on each VLAN.
Dalton Cook commented
Could also use the same idea as Desktop Authority. In DA, they use the Domain Controllers as "beacons" to send the WOL packets.
Elijah Case commented
Would be great to be able to use our Replication clients as WOL relays.
So the status to this was change in June 2015 to Planned and then in July 2016 its now back to Under Review with no plans for a release.
Seriously this is a joke. Now that Dell have sold their software division I can't see things improving either.
Mark H commented
Any update on when this might be in place?
I've got PCs spread across 10 buildings (each with its own VLAN or two) around the city and with power control turning them off after 2 or 3 hours of no activity, having the ability to power a PC on as I need it would be extremely useful.
Elijah Case commented
Thanks a ton Ken!
Make sure it supports Macs!
I put this request in 4 years, 5 months, and 9 days ago. I was hoping for a slightly faster response but I'll take it.
Jonas / Josh - I agree... I manage around 7,000 machines and the K1000/K2000 just isn't up to the task. I am very much looking forward to deploying SCCM so we can dump the KACE products.
Jonas M. Hunziker commented
Josh, we are migrating away from KACE towards SCCM, not for this specific WOL reason, but mainly due to cost.
How has such a simple request not been implemented in 4 years? Now that SCCM is included as part of my businesses annual licensing costs I'm starting to think that moving over would be a better solution for us than sticking with KACE.
We have a big problem with machines going to SLEEP as well. Would save us time from having to physically go wake machines up (or use other methods).
Jarred Wheeler commented
Also, how many of you know that the WOL packets are dependent on the router/switch ARP tables? Having the ARP tables cleared anytime over 5 minutes is a security risk for the organization. So, our WOL only works within 5 minutes of the machine booting up and getting an IP address. ARP WOL is about a 10 year old technology and should be revised using something else (like SQL database). Usually, machines will not move ports - making a database feasible for this cause.
Just my $.02
Georges Khairallah commented
This is an absolute must!
A big bonus, which may need to go in a different request, and that is to allow WOL to be triggered in conjunction with patch schedules,
Kurtis Cochrane commented
I would like to see this improved upon because one of our biggest problems isn't "Wake on LAN" so much as it is "Wake from SLEEP." Hopefully the packet going to the agent to wake up the PC can give this other part a nudge as well.
Kurtis Scott commented
Crafting of a magic packet for wake on LAN is fairly simple so I would hope they could deploy this with the agent fairly easily. I would love to see this feature added.
Camren Quarton commented
We successfully implemented WOL across VLANS by using IP Helpers on the core router. This connects the VLANS to the K2000 IP address. It appeared to work, but only as long as the workstation ARP records existed in the edge switches. Within a couple of days it would no longer work. To resolve the edge switch issue we used the Directed Broadcast command. It allows WOL broadcasts to be executed from a source on a different VLAN. WOL has been very solid for over a year now. We use Cisco for the core router and HP for edge switches.
Derrek Williams commented
Yes, you can set it up to relay across your network (already did that), but what about networks that you don't have access to? You've already got a client/agent installed on every computer, so why not use the SCCM 2012 SP1 method of relaying/proxying WOL via another client on the same subnet (one that's already powered on)?
I also agree with Fred - the scheduling is currently very limited.
This is already built in to competing products.