Tutorial - Local mapped shares

Rev 1.05, 2024.04.05

How to read this tutorial

Summary

This tutorial is targeted companies that:


Wishing to:


This tutorial is a complete walkthrough covering:


Video

Schematics

Installing and configuring accsyn workspace and main on-prem(hq) server


The following guide is a short summary of the installation process described in detail here: Admin Manual

Note: it's perfectly fine to skip Windows drive letters, and go 100% on UNC paths. Drive letters simplifies remote workflows, enabling sites and employees to have a local drive letter keeping project file paths consistent across locations.


You now have a fully working file transfer setup, replacing FTP and similar, allowing you to deliver files to users by their email address.


We will now cover two scenarios, first how to have a restricted user map a share locally and then how to do it for an employee.

Invite user and install app


Next, we are going to setup a accsyn at home for an employee (agnes@mycompany.com).

Prerequisites:


Invite the employee


Install desktop client

This is the most common and simple option - enable file access as long as the desktop app is running.  To have the setup active 24/7, regardless if a user is logged in or not, consider the service option below.

 


User is now all set to start transferring files, but we have not yet configured the local share mapping at proxy storage - enable mirrored path transfers and access by workspace users.


Alternative - install as service

If you seek a 24/7 stable experience, not depending on users running desktop app or not - install the background Windows service version instead:


Notes:


For more detailed information on how to manage the accsyn background daemon installation or how to install it on Mac and Linux, refer to the Admin manual.

accsyn will now launch with your computer, staying online regardless if any user is logged in or not.

Configuring accsyn to map a share locally


By default, local storage is never exposed in accsyn - users choose in the desktop app were to save deliveries and what to upload. To enable mirrored path downloads and uploads, and share the local storage with workspace elevated users (employees and admins), accsyn support something called mapped local shares.

Prerequisites

If you have invited the user as an employee, the will have full access to root shares. If invited as an standard user, you will first need to create a share and grant user full (read & write) access to it. 


Mapping a root share for employee


From this point on: 


Mapping a share for a standard restricted user are done the same way, except that instead of choosing the entire root share/volume (projects) you choose the share user have been granted access to.

Send a directory to employee

To describe how it would work, we are going to send a directory on server/hq to the employee:

If employee has client running, transfer will start directly sending the directory the their local projects storage (P:) and emitting an Email to user when finished.


Pull a file from an employee

Another important usage example is the case when an employee have file locally that is needed by production on-prem:

If employee has client running, transfer will start directly sending the directory from their local projects storage (P:) back to on prem server, emitting an Email to you when transfer has finished.

Conclusion


With accsyn in a working from home/remote endpoint setup, your employees gets tightly integrated when it comes to file management, with encrypted high speed file transfers that resumes were left off and no missing or corrupt parts. 


For more information/tutorials, please head over to support.accsyn.com.