In a multinode environment, session could not be started when "ClientMenuconfiguration none" is set on the node
This problem has been reproduced in a multinode environment with Cloud Server v9.
When the "ClientMenuconfiguration none" is set in the server.cfg file on the node host, connections stuck at login stage and don't complete, users continue to see the connecting spinning wheel.
As a workaround, it's possible to set "ClientMenuconfiguration none" in the server.cfg of the Cloud Server host, this setting will apply to all nodes.
