Administrators would often like to to turn off or reboot a server remotely.
We had this problem every two weeks. Every two weeks we tested our virtualized backup images of all terminal servers. (In future posts I will describe how we managed to backup multiple physical Terminal servers on one virtual using VMWare). Servers are collocated to another continent 
When backup system is tested we need to turn off our terminal servers and boot virtual servers that are identical to the production servers. This is required because in order to avoid duplicate IP or NETBIOS name (virtual servers have the same network configuration as the production servers).
Before we bought ibootbar Appliance we had to call somebody to go to the company and turn on the production servers. This procedure is always tested over weekends so employees were not happy to come to work just to plug in the servers.
We decided to implement remote power control for servers and choose iBootBar appliance because it supports for TCP/IP protocol.
Picture shows a scheme of the implemented solution.
Solid lines are the network connections and bold lines at the bottom are the power lines. Users use the server via regular network connection. iBootBar and backup server are also connected to the same switch because users and administrators enter the network via one switch. Power is plugged into iBootBar and then from iBootBar into servers.
In production only terminal server is turned on. Backup terminal is off. Users connect via network switch to terminal server.
Here is the backup procedure performed via iBootbar:
Turn off the backup server from RDP and use iBootBar to turn on the production server.
iBoorBar console is accessible via web console and the only thing you will need to allow is HTTPS traffic though firewall to iBoorBar.
Our iBoorbar has external IP so we are able to connect to it from anywhere without problem and control power on all of our servers.
For any extra information I would recommend iBootbar homepage at his webiste
