Hello folks. I'm here with a question, and I apologize in advance for the wall of text.
(tl;dr -- is there any way to schedule/guarantee a full power cycle once a week, or month BEYOND just training the customers that this is important? Also, does a scheduled "shut down" actually power off internal components such as the network device? )
Recently we have been hit with a rash of connectivity issues with KFS. For a week or so I was just driving out to the customer location and troubleshooting, until I had noticed that a large majority of these situations were corrected simply by power cycling the machines.
So lately I've been calling the customers, requesting their assistance in performing the power cycle. I'm 3 for 3 today in that regard.
But anyway I began thinking about ways around this issue and it dawned on me that the company I work for as a general rule disables the weekly schedule, and that perhaps configuring the device to power off and power on once/week might correct the issue.
However I am noticing that the device, when that specified time arrives, doesn't actually fully shut down. It goes into sleep mode and can be reactivated simply by pressing the "sleep/wake" button (the moon symbol that illuminates blue when active)-- I do notice that upon rebooting, several options on the operation panel are greyed out/disabled, so I am wondering if this would be enough to accomplish what it is we are aiming for?
that being said, I am noticing that while it is in this sleep mode, the command center is still accessible which leads me to believe the network device is not being powered down. So I had the though that perhaps using "energy saver" and "power saving recovery" as opposed to "quick recovery" and "full recovery" that we use almost as a standard, would be the best route?
But the caveat to that is that I have just spoken with a Kyocera representative and they have informed me that the power saving mode that it enters when the scheduled time arrives simply pulls it's settings from the standard power saver/sleep modes that are scheduled to occur every 1-240 minutes of inactivity.
So I feel as though I have hit a brick wall, and am wondering what creative solutions others in the community may have come up with to rectify issues like the one I've mentioned? So far all that comes to mind is that we need to start training the customers to power the thing down manually once per month or so.
(tl;dr -- is there any way to schedule/guarantee a full power cycle once a week, or month BEYOND just training the customers that this is important? Also, does a scheduled "shut down" actually power off internal components such as the network device? )
Recently we have been hit with a rash of connectivity issues with KFS. For a week or so I was just driving out to the customer location and troubleshooting, until I had noticed that a large majority of these situations were corrected simply by power cycling the machines.
So lately I've been calling the customers, requesting their assistance in performing the power cycle. I'm 3 for 3 today in that regard.
But anyway I began thinking about ways around this issue and it dawned on me that the company I work for as a general rule disables the weekly schedule, and that perhaps configuring the device to power off and power on once/week might correct the issue.
However I am noticing that the device, when that specified time arrives, doesn't actually fully shut down. It goes into sleep mode and can be reactivated simply by pressing the "sleep/wake" button (the moon symbol that illuminates blue when active)-- I do notice that upon rebooting, several options on the operation panel are greyed out/disabled, so I am wondering if this would be enough to accomplish what it is we are aiming for?
that being said, I am noticing that while it is in this sleep mode, the command center is still accessible which leads me to believe the network device is not being powered down. So I had the though that perhaps using "energy saver" and "power saving recovery" as opposed to "quick recovery" and "full recovery" that we use almost as a standard, would be the best route?
But the caveat to that is that I have just spoken with a Kyocera representative and they have informed me that the power saving mode that it enters when the scheduled time arrives simply pulls it's settings from the standard power saver/sleep modes that are scheduled to occur every 1-240 minutes of inactivity.
So I feel as though I have hit a brick wall, and am wondering what creative solutions others in the community may have come up with to rectify issues like the one I've mentioned? So far all that comes to mind is that we need to start training the customers to power the thing down manually once per month or so.
Comment