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, December 30, 2016 6:03:44 PM(UTC)

Rank: Newbie

Joined: 11/2/2012(UTC)
Posts: 11

Hi - we're looking at migrating from on-premise to the new cloud version...is there a simple process to switch all the Windows clients? We have around 450 so keen not to have to manually remote on to each one and download the new client package?

I was wondering whether there was a tool to do this? Or a script? Is it as simple as changing the ScreenConnect ID in the registry?

I'm assuming we'll have to do the Macs manually!!

Thanks, Nick

#2 Posted : Wednesday, January 4, 2017 2:06:06 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, I do have an experiemental method that has had success in the past with similar migrations, it basically changes the cloud instance's asymmetric key to that of your on-premise install. Then you update the on-premise install to change the location to where client's callback and push out a reinstall to each client. As each client processes the reinstall, it is repointed to the new cloud instance which accepts its asym key. Again, though, it's highly experimental and I cannot guarantee results. If you're interested, shoot an email to our Support team and mention my name (Scott) in the title and it'll find it's way up to me.

Alternatively, you could just place an Access client installer into your server's toolbox and then use the Run Tool option on the Host page to execute it on each remote machine. This is significantly safer.
ScreenConnect Team
#3 Posted : Sunday, July 9, 2017 1:23:58 PM(UTC)

Rank: Newbie

Joined: 11/2/2012(UTC)
Posts: 11

Hi - just looking at our options for switching to cloud from on-premise...is this method any less experimental than it was 6 months ago?

If not, what is the "approved" process? Or what do most people do?

We can install the cloud ScreenConnect client from the command line...but how do we identify clients on the on-premise console that have got the cloud Screenconnect client installed as well, so we can remove them from the on-premise console?

I'd rather not risk orphaning a machine by trying to automate uninstalling the on-premise client and then having a failed cloud client installation?
#4 Posted : Monday, July 10, 2017 7:44:23 PM(UTC)

Rank: Administration

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

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

Thanks: 56 times
Was thanked: 82 time(s) in 68 post(s)
At this time, we don't have anything to assist with the migration. This is a project we're going to be looking at in Q3. It would be helpful to know what items you'd like migrated. For example, are you primarily only concerned with agents?
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.