logo

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.

Notification

Icon
Error

Options
Go to last post Go to first unread
Jake  
#1 Posted : Friday, June 3, 2011 11:53:34 AM(UTC)
Jake


Rank: Administration

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

Joined: 4/9/2010(UTC)
Posts: 2,061

Thanks: 1 times
Was thanked: 393 time(s) in 188 post(s)
ScreenConnect creates a folder "ScreenConnect" (or something else if you've customized Client.ApplicationTitle) off your user Documents directory to use for your videos, toolbox, and received files. Generally this will be created on a local disk and generally it will only be accessible to the current user.

Use NTFS symbolic links to share this information. To accomplish this, recreate your "ScreenConnect" directory as a symbolic link to a network share:

Code:
C:\Users\jmorgan\Documents>ren ScreenConnect ScreenConnect2

C:\Users\jmorgan\Documents>md \\commonserver\commonshare\screenconnect

C:\Users\jmorgan\Documents>mklink /d ScreenConnect \\commonserver\commonshare\screenconnect
symbolic link created for ScreenConnect <<===>> \\katmandu\distribution\temp\screenconnect

C:\Users\jmorgan\Documents>copy ScreenConnect2\* ScreenConnect
ScreenConnect2\autoruns.exe
ScreenConnect2\BltTest.exe
ScreenConnect2\compmgmt.lnk
ScreenConnect2\Mdbg_x64.exe
ScreenConnect2\Mdbg_x64.zip
ScreenConnect2\Mdbg_x86.exe
ScreenConnect2\Mdbg_x86.zip
ScreenConnect2\MSE_x64.exe
ScreenConnect2\MSE_x86.exe
ScreenConnect2\procexp.exe
ScreenConnect2\Procmon.exe
ScreenConnect2\proxy.exe
ScreenConnect2\Reflector.exe
ScreenConnect2\resetScreenConnect.bat
ScreenConnect2\setenv.bat
ScreenConnect2\taskkill.exe
       18 file(s) copied.


C:\Users\jmorgan\Documents>rd /s /q ScreenConnect2


If you don't want to share everything, but only a few common tools, you can create a symbolic link to a network share under the "ScreenConnect" folder, rather than replacing it entirely.

In the future we may use different subdirectories for videos, toolbox items, and received files. This will give you even more granularity in what you share vs what you keep private.

Also in the more distant future, we may just keep everything on the web server, so you can access it even when off the network.
ScreenConnect Team

jamie.stubbe  
#2 Posted : Tuesday, November 22, 2011 10:00:42 PM(UTC)
jamie.stubbe


Rank: Member

Joined: 11/21/2011(UTC)
Posts: 21
Location: Red Deer

Thanks: 1 times
Jake Morgan wrote:

Also in the more distant future, we may just keep everything on the web server, so you can access it even when off the network.



Yes PLEASE!!

This would help so much and is closer to the top of the list on many users wish list,

A priority for sure!


In the mean time.. allowing us to select the directory where we store the files would be handy as a stop gap..

and able to use a network share.

\\server\toolbox <---example.


I assume that getting server side storage working is a nightmere in logistics.

once the server hands off the connection too the 2 clients. (host/guest) there-for creating a point to point connection..
I would assume the server is not able to send files across the encypted tunnel..

So can we maybe get a build that allows the customization of the toolbox location with network support until we get server side storage hashed out?

Thanks Jamie.

Edited by user Tuesday, November 22, 2011 10:01:18 PM(UTC)  | Reason: Not specified

bigdessert  
#3 Posted : Tuesday, November 22, 2011 11:23:07 PM(UTC)
bigdessert


Rank: Advanced Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 3: Shirt off your back! Received 25 Thanks!

Joined: 9/13/2010(UTC)
Posts: 708
Location: Minnesota

Thanks: 1 times
Was thanked: 44 time(s) in 32 post(s)
It is coming, they practicly rewrote the whole relay service to facilitate this, auto update for unattended, multiple hosts per session. I am sure this will also facilitate doing many....many things.

One thing that comes to mind is an offline toolbox where you could build vbscript WMI calls and gather system information without actually connecting to the machine.

Now all we have to do is wait for the 2.4 pre-release....I am hoping it is an early christmas present!
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.