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:



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.

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!