William Mullen
My feedback
16 results found
-
3 votesWilliam Mullen
shared this idea
·
-
38 votesWilliam Mullen
supported this idea
·
An error occurred while saving the comment -
564 votesWilliam Mullen
supported this idea
·
-
1 voteWilliam Mullen
shared this idea
·
-
105 votesWilliam Mullen
supported this idea
·
-
202 votes
Thank you for your very thorough desciption of the issue. We will consider this as a feature request in the future. We prioritize based on feedback like yours – so we encourage others to vote for this feature request.
William Mullen
supported this idea
·
-
120 votesWilliam Mullen
supported this idea
·
-
47 votes
An error occurred while saving the comment William Mullen
commented
Still waiting on this???
-
7 votesWilliam Mullen
supported this idea
·
-
16 votesWilliam Mullen
supported this idea
·
-
19 votesWilliam Mullen
supported this idea
·
-
40 votes
Thank you for your input. We are investigating this and encourage others to vote for this feature/functionality if they think it would be useful
William Mullen
supported this idea
·
-
1 voteWilliam Mullen
shared this idea
·
-
3 votes
An error occurred while saving the comment William Mullen
commented
Should be able to approach something close to what you want to do with cron, i.e., cron 0 9 15-21 */2 5
-
443 votes
This feature request is under review. We encourage others to vote for it to be considered in a future release.
William Mullen
supported this idea
·
-
6 votesWilliam Mullen
shared this idea
·
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.