Save Config breaks Hub Autodiscovery Workarounds

Explanation
When a Desktop Station is booted and does not have access to a Hub it can set it's Hub configuration to blank ("no Hub found).

If an administrator saves the configuration while the Hub setting is blank, the bug causes the saved configuration to include settings indicating that the Desktop should _not_ connect to a Hub.

As a result, if the Desktop is subsequently connected to a network with a Hub it will not attempt to connect to the hub.

Symptoms
The most obvious symptom is that the Desktop will not create the 'Shared Files' desktop folder and will not allow access to file shares on the Hub.

Workaround 1: Manually enter Hub Address

 * 1) Make sure the desktop is connected to the Hub's LAN network
 * 2) Boot the desktop
 * 3) Open the 'Configure Inveneo Servers' panel: Start->Administration->Configure Inveneo Servers
 * 4) Choose the 'Connect to a specific hub station' option
 * 5) Enter the Hub server's IP address into the field
 * 6) Close the panel
 * 7) Save configuration: Start->Administration->Save Configuration
 * 8) Reboot the Desktop

On reboot, the Desktop should display the 'Shared Files' folder and have access to the Hub server's file share.

Workaround 2: Force Hub re-discovery

 * 1) Make sure the desktop is connected to the Hub's LAN network
 * 2) Boot the desktop
 * 3) Open a terminal: Start->Administration->Terminal
 * 4) In the terminal enter the following command to force discovery of the Hub. Enter the standard amdin password when prompted:  sudo /opt/inveneo/bin/find-hub-station.py
 * 5) Save configuration: Start->Administration->Save Configuration
 * 6) Reboot the Desktop

On reboot, the Desktop should display the 'Shared Files' folder and have access to the Hub server's file share.