logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Zebedee  
#1 Posted : Saturday, August 4, 2012 12:58:54 PM(UTC)
Zebedee


Rank: Newbie

Joined: 8/4/2012(UTC)
Posts: 2
Location: Oxford, England

Hi,

Could some one please tell me the best way to move my ScreenConnect install to a new Windows Server 2008?

Old server needed replacing, so I have built a VMware ESX server to host ScreenConnect on a fresh build of Server 2008r2.

Is it a case of running the install and copying certain files & folders over?

Many thanks.

Zebedee.
Mike  
#2 Posted : Monday, August 6, 2012 8:40:16 AM(UTC)
Mike


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 5/30/2012(UTC)
Posts: 494
Location: Raleigh, NC

Thanks: 53 times
Was thanked: 78 time(s) in 64 post(s)
Hi Z,

Follow these steps to move a ScreenConnect installation. We will use the term server below to denote the machine, VPS, or VM where the ScreenConnect web application is installed. (This can also be found on our help site, help.screenconnect.com)

Moving or Changing Installations

1. You should familiarize yourself with the ScreenConnect layout by reading INFO-0003: Installation Layout.

2. Run a backup of your existing ScreenConnect installation. Our knowledge article on backing up ScreenConnect is a good resource for this process.

3. Download an MSI installer file from the ScreenConnect download center.
The versions of ScreenConnect on the new and old server need to match to simplify this process. If the old server installation is a different revision than the MSI you downloaded, first run the MSI on the old server to upgrade its version. Browse ScreenConnect on the old server to verify everything is working before proceeding.


4. Next run the same ScreenConnect MSI on the new server. Browse ScreenConnect to verify everything is working properly. You should now have identical versions installed on both servers.

5. Now copy and paste the entire contents of the ScreenConnect folder from the older server to the ScreenConnect folder of the new server. At minimum you must move the following files and directories:

%INSTALLDIR%\web.config
%INSTALLDIR%\App_Data
%INSTALLDIR%\App_GlobalResources

6. If you have made advanced customizations by editing ScreenConnect files directly, make sure those are also transitioned to the new server.

7. If there were any manual changes to the web.config file that rely on a network configuration that has changed between machines, you will need to update the web.config file to reflect the new network configuration.

8. The final step is to set up or modify the URL mapping to the new installation. It is important to do this step last so that any unattended installations that call in will see the proper encryption key and ScreenConnect configuration when they first make contact. If an unattended installation calls into a ScreenConnect installation that has the wrong public/private key the unattended client will shut down until that machine is rebooted.

Notes:

ScreenConnect licenses are not bound to machines, so simply copying and pasting the existing license into your new ScreenConnect installation will work just fine.

Please be aware of the path where your current unattended installations are calling back. Unattended installations call back to a particular URL path and then check that the correct encryption key is present. You can check the path, by right-clicking on the ScreenConnect icon, in the _systray_ of the unattended system, and choosing status. The Relay Server: address will show the path of the connection. For more information please reference HOWTO-0007: Unattended Remote Sessions.

Hope this helps.

Please let us know if you need any additional assistance.




ScreenConnect Team
wavesound  
#3 Posted : Tuesday, August 7, 2012 10:55:45 AM(UTC)
wavesound


Rank: Advanced Member

Joined: 11/25/2011(UTC)
Posts: 35

You may find this tool useful: http://www.analogx.com/c...rk/pmapper/Freeware.htm.

After you update your host you can use this (or a similar tool) to forward the old relay port on your old server to the new relay port on your new server.
Zebedee  
#4 Posted : Sunday, August 12, 2012 12:19:25 PM(UTC)
Zebedee


Rank: Newbie

Joined: 8/4/2012(UTC)
Posts: 2
Location: Oxford, England

Sorry for the delay in replying.

Many thanks for the very helpful info posted guys, I will see how it goes.

Once again many thanks.

Zeb.
ShaneC  
#5 Posted : Monday, December 18, 2017 12:35:57 AM(UTC)
ShaneC


Rank: Guest

Joined: 2/4/2017(UTC)
Posts: 1
Australia
Location: Australia

Originally Posted by: Mike Go to Quoted Post
If an unattended installation calls into a ScreenConnect installation that has the wrong public/private key the unattended client will shut down until that machine is rebooted.


Is this still the case? A single misstep during migration or a single bit error during transmission and you're SOL? Because that's a terrible failure mode for unattended machine(s) that may be multiple hours travel away from a manual reboot.

Edited by user Monday, December 18, 2017 12:39:49 AM(UTC)  | Reason: Not specified

Scott  
#6 Posted : Wednesday, January 10, 2018 2:14:01 PM(UTC)
Scott


Rank: Administration

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

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

Thanks: 3 times
Was thanked: 338 time(s) in 292 post(s)
Quote:
Is this still the case? A single misstep during migration or a single bit error during transmission and you're SOL? Because that's a terrible failure mode for unattended machine(s) that may be multiple hours travel away from a manual reboot.


No that is not the case. If a client callsback and is unable to establish a secure connection due to a key mismatch it will just continue retrying. The time interval between retry attempts does increase but I believe it's maximum length is ~30 minutes.

The only instance when a client will not attempt to reconnect is if the session has been Ended on the server. In that case, the client callsback, sees its been ended, and then stops attempting to reconnect. Restarting the service will reattempt this connection (rebooting restarts the service).
ScreenConnect Team
Users browsing this topic
Similar Topics
Information about moving Screenconnect to a new server (Installation Help)
by Midlandtech 1/20/2014 2:21:33 PM(UTC)
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.