The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.



Go to last post Go to first unread
#1 Posted : Friday, November 11, 2016 11:20:34 PM(UTC)

Rank: Newbie

Joined: 2/4/2015(UTC)
Posts: 2
Location: Guelph


As per this page: https://help.screenconnect.com/Server_architecture

I was wondering if anyone had used the horizontal scaling illustrated in the above document. Reading it it speaks more about the application than about some sort of configuration change but I was hoping there might be some hints regarding that sort of setup.

My ideal scenario would be having the Session Manager and Relay on one box and Web Server on another because of the way I've setup my environment.

I would be fine using Firewall rules to forward traffic to the second server so that the configuration from a ScreenConnect client's perspective wouldn't be anything too odd.



#2 Posted : Thursday, November 8, 2018 4:55:52 AM(UTC)

Rank: Newbie

Joined: 4/27/2015(UTC)
Posts: 30

Thanks: 6 times
Was thanked: 3 time(s) in 3 post(s)
I'm wondering about this too.

And I find it odd that, despite stating:
"Horizontal scaling is not a supported implementation at this time, but our team is available to answer questions in our forum"
on the page that jon@risolv linked to above, CW still hasn't answered his question after 2 years.

P.S. I just found the following feature request, also from 2 years ago:

Edited by user Thursday, November 8, 2018 4:58:40 AM(UTC)  | Reason: Not specified

#3 Posted : Monday, November 12, 2018 12:43:40 PM(UTC)

Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
So that document refers to the ability for our process to run in a few different ways. By default, starting the process will start each of the three parts (Web Server, Relay, and Session Manager) within the single process itself. By making a minor modification to the ImagePath setting within the Service definition in the registry for the three services you can tell each service to start only its specific part. This allows for the application to essentially run the Web Server, Relay, and Session Manager as its own process. There are a number of reasons why this can be beneficial but they are mainly centered around development and bug investigating. When the server process was still running on the 32bit architecture it would increase the available memory pool up to 3x. As of an early 6.x release, however, the server now runs at 64bits and the available memory pool is astronomically larger.

The Feature Request to which @aslee refers is similar but not quite the same thing. Right now the above configuration can only be done on a single server, as in the interop communication must be on the same machine. If you are interested in configuring your On-Premise instance in this way you can find mostly unofficial documentation here. I call it mostly unofficial because while it was written by members of the ConnectWise Control team, it is important to note that we do not guarantee it to work and we cannot support the setup.
ScreenConnect Team
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.