Reboot from Admin Panel - For windows and linux

[BrenttG]

I realize this is technically possible on linux servers due to the console feature, but it has been asked for by numerous clients if we could get support to have a reboot button in the admin panel which was functional to both windows and linux 3CX Servers, as windows servers do not have the console feature this makes the most sense.

For linux the backbone is already there, just map the function to a button instead of requiring it to be typed in by hand.

For windows, its as simple as "shutdown /r /f /t 1" Which is the windows shell command for force reboot in 1 second, the force option is only there that way if some program like notepad or something with a dialog is up on the screen it forces the reboot process to automatically close that and continue rebooting and not get stuck there for eternity until someone clicks save or dont save.

This would also make it simple to reboot a server, without having to resort to RDP, remote console, or other third party remote access tools to be able to reboot the windows servers, and it would mean it could be uniform between linux and windows if it were just a button as again, windows doesn't have the console option.

Please and thank you 3CX Dev Team!

 

[KFACTA]

+1

 

[StefanW]

What is the business requirement behind to reboot the host? 3CX as the application does not require host reboots. Also, you will have no vision if the host will then apply windows updates or not.

 

[BrenttG]

1. Because on occasion windows servers especially, get bogged down if they have not been rebooted in a while, they start to do what i best described as "stutter" and they can also mass un-released virtual memory as well, which a reboot corrects, we make it a point to reboot windows servers once a month, and it has actually alleviated a lot of strange issues that crop up without the reboots.

2. Im not saying the reboot is to correct any 3CX issue, more it seems to be the underlying OS that will occasionally need it. Additionally, if a user reboots one during business hours and is marred by windows update, that is kind of their own doing, one should be smart enough to know that is a possibility and to only use such a feature during maintenance windows. Plus, they could also adopt a policy we use on of of the critical 3CX servers we run, in which the Windows Update service, and the Windows Modules Installer service are disabled, this effectively prevents windows machines from running updates during a reboot process and remedy's the issue, we have a maintenance window once a month in which we re-enable those services and allow the Windows Server to then do its updates, and then we disable those services once more, so it is managable, with proper windows server experience. And while we would always prefer a critical 3CX Server be built on Linux, that particular customer is "afraid" of linux, so we had no choice.

The point is, sometimes things just need a reboot, issues arise, glitches happen, life happens, and not having that ability is cumbersome.

 

[DTI Tech]

+1

 

[Cutshaw]

+1