CONNECTION POOL

Follow

Connection pool feature available in version 3.4.6.0 of our Business app w/ Splashtop Enterprise.

Connection pool feature in Scheduled access, allows your users to connect to any available computers in a group. It's a great feature to use for customers who want their users to access any available computers, especially in scheduled access and RDP connection scenario. 

When enabled, a quick Connect button will appear so you can connect to available computers inside the computer group. You can expand the resource group and connect to a specific computer as well. Only owners/admins/group admins can enable this feature. See screenshots below. 

Screen_Shot_2021-05-02_at_1.20.56_PM.png  

connection_pool_sba_desktop.png

iOS_connection_pool.png

You can enable connection pool when creating your resource:  Management > Scheduled Access > Create Resource.

Under Advanced settings you can select Support connection pool for schedules. When selected this enables the ability to use connection pool for all schedules under this resource. When toggled ON it also allows to Set the schedule as connection pool. Which forces all schedules to use connection pool by default.

 

resource_schedule_access.png

connection_pool_setting_zoomed2.png

 

When creating your schedule: Management > Scheduled Access > (Resource name) > Create Schedule.

Under Advanced Setting you have the option to Set the schedule as connection pool.

 

resource_schedule_access2.png

 

connection_pool_setting_zoomed.png

 

Expected Behavior Notes:

  • Users click the Connect below the schedule name to connect to one of the computers in connection pool.

  • You can expand the connection pool to see all included computers and connect to specific computer.

  • If there is an active session, click the connect button should bring the session window to the front.

  • When there is no available computer, no user can connect to connection pool via connect button. No matter what role the user is.

  • Every new remote session would make the streamer cannot be connected again in 30 seconds.

  • Multiple sessions for connection pool is not allowed at this implementation.

  • Users would be auto-connected to the same computer from last session. (successful connection)

 

 

 

1 out of 1 found this helpful