My Console disconnects from Gateways during startup, is there a way to stop this?

Once a work space is selected the console will start the process of connecting to all the (Enabled) gateways in parallel. It does this because communication with the gateways across the LAN / WAN is asynchronous and the specific timing and state of the gateways is an unknown (at least at the start).

However this causes significant load on the console and it can create a constant cycle of disconnects and re-connects which may take a long time to resolve (assuming it recovers at all). This connection behavior can be changed by use of the following flag in the ActiveConsole.gci file (assuring no leading or trailing spaces).

-queueConnections

This will force the console to connect to each gateway in full one by one, and in order.  While this can slow down the process in most systems, it can help in others where the gateways are large and connections takes time since it can stop the disconnection of already connected gateways.

To find the ActiveConsole.gci file, navigate to the ActiveConsole's installation directory and ensure you either have file extensions enabled or change your view to "Details", so you can sort by Type and look for "GCI File". Once you find it, open it with Notepad or Notepad++ (Word is not recommended, due to formatting issues). Add "-queueConnections" to the end of the file, but make sure that there are no trailing spaces after the flag. Save it and relaunch your ActiveConsole.

Keep in mind that since this will now change the behavior of how ActiveConsole connects to Gateways (in sequence, rather than in parallel), it can take longer for all your Gateways to connect. In an environment where there are hundreds, or thousands of Gateways, this can be a substantial amount of time.