How to Share a File Securely Using ShareFile “Email with ShareFile” Feature

Article Contents (click a link to skip to that section)

Email with ShareFile

Email with ShareFile allows you to send your file(s) via ShareFile’s email system. With this method, the recipient receives an email message containing a secure link to download the file(s). You can send a file stored on your account, or send a file stored on your computer.

To send a file stored on your computer using ShareFile

  • Click Share Files on the Dashboard.

    Note: This method requires File Box access.

    User-added image

To send a file stored in your account using ShareFile

Right-click the file and choose the Share option.

User-added image

OR

Open the file with the Content Viewer and choose a Share option

User-added image

Customize Your Message Before Sending

New ShareFile Users – Email with ShareFile

  1. Enter a Recipient for your message. You can enter an email address manually, or select users from your address books or distribution groups.
  2. Enter a Subject for your message. You may enter additional text in the Body of your message if needed.
  3. Edit Message Options allows you to customize the following:
    • Send me a copy of this email – Receive a copy of the email message
    • Email me when files are accessed – Receive a notification email when the file is Viewed or Downloaded
    • Encrypt message – This feature is only available to users with Encrypted Email enabled.
    • Require recipients to log in – Require that recipients log in with their ShareFile account. If your recipient is not already a user on your account, they will be required to create a username and password before accessing the file.
    • Access expires – Set how long you want the download link to be accessible. If sending a file stored on your computer, this will default to the default length of time files may remain in the File Box
    • Allow Recipients To – This option is available to users utilizing View-Only or IRM-protected sharing features.
    • Accesses per user – Limit the number of views or downloads
    • Always link to the latest version of the file – This feature is only available to users with File Versioning enabled.
    • Remember subject and custom message for next time – Save the subject and custom message so that it will be preset the next time you send a file.
  4. Add More allows you to select additional files to include with your message.
    • If sending files stored on your computer, a copy of the file will automatically be uploaded to your File Box.
    • If adding from ShareFile, use the folder tree menu to select which files to add.
  5. Click Send when ready. You will receive confirmation that the message was sent successfully. If sending files stored on your computer, the file will not send until the file is uploaded to your File Box. Please do not exit the menu until the success message is shown.

User-added image

What Your Recipient Sees

The recipient will receive an email from “mail@sf-notifications.com” on behalf of the the ShareFile user that sent the message. Your recipient can then click the provided link to access the files.

User-added image

I’m a client receiving a file request. What do I do?

When a ShareFile user sends you a Share a File link with the “Require User to Login” option checked, you will be asked to create a ShareFile account in order to access the link you have received. If the ShareFile user sent you a file request via the ShareFile Email System, you will receive an email with a link, as shown below.

  1. Click the link to activate your account and download files.
  2. Before you can download files, you must set a password for your account. For security reasons, please do not close the browser window or navigate away from this page until you have configured your password. If the ShareFile user does not permit users to set their own passwords, your password will be displayed here.
  3. Once you have set your password and clicked Save, you can download files.

User-added image

I closed the window before setting my password. How should I proceed now?

Don’t worry. Simply return to the original email message and click on the link again. Instead of a password configuration page, you will be shown the following:

User-added image

This will also trigger a new email message. Check your Inbox for a new email message containing an activation code, as shown below. This code must be entered in the field shown above within one hour.

Why do I have multiple emails with activation codes? Which one should I use?

  • The first time you click the link in your message, you will be taken to the password configuration page shown further up in this section.
  • If you clicked the link but then didn’t finish setting your password information, an activation code will be generated every time you click the link in the original email message.
  • In order to verify your account, you must use the most recent activation code in your Inbox.

Get a ShareFile Link to Share

Get a Link allows you to quickly obtain a secure download link to your files. With this method, ShareFile generates a link that you can copy and paste.You can send a file stored on your account, or send a file stored on your computer.

To send a file stored on your computer using ShareFile

  • Click Share Fileson the Dashboard

    Note: This method requires File Box access.

    User-added image

To send a file stored in your account using ShareFile

Select the file(s) and use Share in contextual menu

User-added image

OR

Open the file with the Content Viewer and choose a Share option

User-added image

Customize Your Link Before Generating

  1. Edit Link Options allows you to customize the following:
    • Email me when files are downloaded – Receive a notification email when the download link is used by your recipient.
    • Require recipients to enter name and email – Require that recipients enter a name and email address before downloading the file. Note: You cannot require users to sign into their ShareFile account when using the Get a Link option. For the most secure experience, use the Email with ShareFile option if you wish to require users sign in with ShareFile credentials before accessing the file.
    • Access expires – Set how long you want the download link to be accessible.
    • Accesses per user – Limit the number of views or downloads.
    • Always link to the latest version of the file – This feature is only available to users with File Versioning enabled.
  2. Add More allows you to select additional files to include with your message.
    • If sending files stored on your computer, a copy of the file will automatically be uploaded to your File Box.
    • If adding from ShareFile, use the folder tree menu to select which files to add.
  3. Click Get a Link when ready. The link will be generated and displayed on screen.

  4. Click Copy Link to copy it to your clipboard. You may then paste the link into the app of your choice.

User-added image

    Related:

    • No Related Posts

    Best way to restore files from snapshots from Backup to Prod cluster with a GUI

    Hi,

    Hope somebody can assist me with the following:

    Company demands there is a way to restore files from Isilon from a GUI (not (only) CLI).

    Files are backupped from Prod to Backup cluster. /ifs/ path from both clusters are mounted on a RedHat Linux VM (GUI), so being logged on to this VM we can drill-down directories to copy back files from the snapshot directory on the Backup cluster to the Production cluster.

    Now the situation is as follows:

    The /ifs path of the Prod cluster is mounted as R/W, the /ifs path of the Backup cluster is mounted as RO (readonly).

    The key we use to log on to the Isilon is different from the one used to log on to the restore VM, both are AD (ActiveDirectory) keys.

    I noticed I can only create New Folder or paste files from within a File Window in the mounted /ifs directory and not in the directories below

    that.

    Also when copying files from the backup cluster to the Prod cluster file-permissions are not preserved.

    My idea was to add the AD user which is used to log on to the restore VM to the Isilon as a member in Role SuperAdmin.

    Does not seem to change a thing though.

    I hope I have been able to make the situation clear enough with the above to get some help with what would be a good way to solve this.

    Related:

    • No Related Posts

    App Layering error “A failure occurred while publishing the Layered Image: “Failed scanning a directory for files”

    Recommended Solution: This issue has now been fixed in versions 4.6+ of App Layering. The simplest way to resolve this issue is to upgrade the latest version of the App Layering appliance.

    For historical purposes, here is the original fix for those who are still using versions 4.5 or earlier of the App Layering product:

    This error is most frequently caused by Microsoft OfficeHub. The “Program FilesWindowsAppsMicrosoft.MicrosoftOfficeHub” directory has a new type of reparse point that was recently invented by Microsoft, and ntfs-3g is currently unable to handle it. Thus, there is no way for the our Linux virtual appliance (App Layering ELM) to correctly recognize the files. So we’ll need to remove them before working in App Layering. There is no negative effect to removing the OfficeHub files, as the files will be rebuilt automatically on end user desktops.

    The fix needs to be done in the VM or layer where the problem files lie. If the error occurs while publishing a VM (App Layering versions 4.x) or during desktop creation (versions 2/3.x), or while editing/creating layers, then you will need to execute the fix on the specific layer that is causing the issue. Usually the problem lies on the OS layer, so you would need to execute the solution on a new version of the OS layer. However, it is also possible that the offending files are on an application layer or the platform layer, so you may need to experiment to determine which layers the files are located on. If you cannot find them in file explorer for any of the layers, you should open a Technical Support case, and one of our engineers will be able to make that determination.

    Solution 1: PowerShell

    On the OS layer, running the following two PowerShell commands (from command prompt as administrator) might be able to remove the folders without manually setting permissions and deleting them Sometimes, manually deleting the folders can be a long and painful process. Make sure to run the PowerShell commands as the admin that originally created the image. It is possible that OfficeHub may already be staged for the original user, and will deny removal from the following script if that is the case.

    powershell -command "& {Get-AppxPackage -name Microsoft.MicrosoftOfficeHub -AllUsers | remove-appxpackage}"powershell -command "& {Get-AppxProvisionedPackage -online | Where-Object {$_.DisplayName -like "*Microsoft.MicrosoftOfficeHub*"} | remove-AppxProvisionedPackage -online}

    Solution 2: Manually changing the file permissions, and then deleting them

    Check to make sure the files are located in the “Program FilesWindowsAppsMicrosoft.MicrosoftOfficeHub” directory. The files will need to be deleted out of this folder, and typically you’ll need to take ownership and change permissions in order to remove them.

    Additionally, on Windows 10 Enterprise machines, you may also need to check and remove the OfficeHub directory from “usersAdministratorappdatalocalpackagesMicrosoft”

    Lastly, make sure Program Files/WindowsApps/Deleted/Microsoft.MicrosoftOfficeHub_17.8010.5926.0_x64__8wekyb3d8bbweb6a07f30-3c9c-4a53-867e-42e7a1f58db8* is empty.

    _________________________________________________________________________________________________________________________________

    In extreme cases, the $recycle.bin may also need to be completed deleted.

    The following command will delete the $RECYCLE.BIN – then the OS will refresh and recreate it automatically, without any artifacts from OfficeHub.

    RD /S /QDrive-Letter:$Recycle.bin

    Related:

    • No Related Posts

    Error: “XDDS:16489564” When Creating Machine Catalog

  • The full set of invalid characters can vary by file system. For example, on Windows-based desktop platforms, invalid path characters might include ASCII/Unicode characters 1 through 31, as well as quote (“), less than (<), greater than (>), pipe (|), backspace (b), null () and tab (t). For more information refer to MSDN documentation – (Path.GetInvalidPathChars Method ())

  • Related:

    • No Related Posts

    Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’)

    Try to determine which files are taking up disk space. on Identity disk

    For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

    The PsExec tool is available for download at this location

    http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

    Follow these steps to access the Identity disk volume on the VDA:

    1. Open elevated command prompt <Run as administrator>

    2. execute the command under the context of the Local System account via PsExec:

    PSEXEC -i -s cmd.exe

    This it to access to the junction linked to the Identity Disk volume

    3. Navigate to the root of the junction “PersistedData”, and execute the following command:

    DIR /O:S /S > C:{location}Out.txt

    4. Open out.txt using Notepad or text editor

    5. Check the files taking up the disk space.

    6. Move the unwanted files to an alternate location or delete them

    Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

    Related:

    • No Related Posts

    Re: Can’t delete or load VNX  VDM “VDM is not loaded”

    I am trying to delete all the NAS resources to zero the drives, but I have one storage pool for file that won’t delete

    I’m not sure if there are file systems or not – in unisphere they are all deleted, but in the CLI, I am still seeing them and there is a VDM I can’t delete:

    [nasadmin@vnx1 ~]$ nas_fs -list

    id inuse type acl volume name server

    1 n 1 0 10 root_fs_1

    2 y 1 0 40 root_fs_common 2,1

    3 n 5 0 73 root_fs_ufslog

    5 n 5 0 93 root_fs_d3

    6 n 5 0 94 root_fs_d4

    7 n 5 0 95 root_fs_d5

    8 n 5 0 96 root_fs_d6

    9 y 1 0 12 root_fs_2 1

    13 y 1 0 14 root_fs_3 2

    16 y 1 0 115 root_fs_vdm_Researc 1

    38 y 102 0 0 lcsrt v1

    41 y 102 0 0 lcsr v1

    146 n 5 0 458 root_panic_reserve

    [nasadmin@vnx1 ~]$ server_umount Research_VDM lcsrt

    Research_VDM :

    Error 4032: Research_VDM : VDM is not loaded

    [nasadmin@vnx1 ~]$ server_mount Research_VDM

    Research_VDM :

    Error 4032: Research_VDM : VDM is not loaded

    [nasadmin@vnx1 ~]$ nas_server -vdm Research_VDM -setstate mounted

    Error 5005: failed to complete command

    [nasadmin@vnx1 ~]$ Error 5005: failed to complete command

    info on VDM:

    [nasadmin@vnx1 ~]$ nas_server -info -vdm Research_VDM

    id = 1

    name = Research_VDM

    acl = 0

    type = vdm

    server = server_2

    rootfs = root_fs_vdm_Research_VDM

    I18N mode = UNICODE

    mountedfs = lcsrt,lcsr

    member_of =

    status :

    defined = enabled

    actual = temporarily unloaded

    Interfaces to services mapping:

    Related:

    • No Related Posts

    Event ID 1023 Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’). VDAs in Delivery Group losing registration with the Delivery Controllers

    Try to determine which files are taking up disk space. on Identity disk

    For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

    The PsExec tool is available for download at this location

    http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

    Follow these steps to access the Identity disk volume on the VDA:

    1. Open elevated command prompt <Run as administrator>

    2. execute the command under the context of the Local System account via PsExec:

    PSEXEC -i -s cmd.exe

    This it to access to the junction linked to the Identity Disk volume

    3. Navigate to the root of the junction “PersistedData”, and execute the following command:

    DIR /O:S /S > C:{location}Out.txt

    4. Open out.txt using Notepad or text editor

    5. Check the files taking up the disk space.

    6. Move the unwanted files to an alternate location or delete them

    Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

    Related:

    • No Related Posts

    Troubleshooting steps to fix ‘scanpst.exe fails with Fatal Error 80040818’

    Outlook PST powers the smooth functioning of Outlook by acting as a safe-house for all emails, contacts, calendar entries, notes, etc. associated with user mailboxes. However, with time and continued usage, data keeps piling up within PST files pushing them towards size limit breach and eventual corruption. The ScanPST.exe utility offered by Microsoft comes handy to detect and fix errors and corruption within PST files. While it works in most situations, sometimes it can fail due to several reasons and throw cryptic errors like the ‘Fatal Error 80040818’ leaving users confused and clueless as to what should be done next.



    Read on to find out everything there is to know about this error and how you can fix it without much trouble.



    Causes that trigger ‘Fatal Error 80040818’



    Outlook supports PST files of two formats – ANSI and Unicode. Outlook versions 2002 and earlier supported ANSI format PST files which were bound by a 2GB size limit. This limit was extended to 20GB for Unicode format PST files supported by Outlook versions 2003 and beyond. The amount of data that your Outlook PST can handle therefore depends on the format in which it is encoded. Whenever the size of the PST file approaches its limit, it starts facing the threat of corruption.



    Other causes of PST file corruption include:



    • Accessing ANSI format PST file with Outlook 2003 or later versions
    • Over-stuffing PST files with data without cleaning or archiving them once a while
    • Abrupt system termination or Frequent Power surges
    • Virus infection to the files
    • Bad sectors on the hard drive where the PST is saved

    If your Outlook PST file has been corrupted owing to any of the above mentioned reasons, you are bound to face problems. Resolving them at the earliest is the only way to get back to work.



    Solutions to ‘ScanPST.exe fails with fatal error 80040818’



    The Inbox Repair utility ScanPST.exe offered by Microsoft is the first method used by most Outlook users to detect and fix corruptions and other errors within PST files. However, in cases of severe PST corruption, this utility fails to perform its task and terminates throwing errors like ScanPST.exe fails with fatal error 80040818. In such cases, you can try out one of the below mentioned techniques to fix the issue:

    • Reinstall MS Outlook – this might fix any anomalies in PST file behavior
    • Use CHKDSK utility available in Windows OS– this will help repair disk permissions and other system errors
    • Split and Compress PST files – this will help in reducing PST file size which is the original cause of PST file corruption
    • Try moving the corrupted file to a system installed with earlier version of Outlook or convert the Outlook PST file from ANSI format to Unicode format

    Though these tricks should help you fix the problem, if the error still doesn’t budge, read the next section to find out our pick for the best PST repair software which will empower you to defeat this error for sure.



    Sure-shot remedy for PST file corruption



    Extensive research across various popular technical forums point out that the best Outlook repair utility available online is Stellar Phoenix Outlook PST Repair. Powered by advanced scanning and repair algorithms, this software can easily detect and repair corruption within PST files and rid it off all nasty errors. The process is non-intrusive and non-destructive so the format of your PST file data isn’t modified in any way during the repair. A simple 3-step approach (Scan-Preview-Save), fully interactive GUI, and tons of other associated benefits make this software the ideal choice to fix problems like Fatal Error: 80040818.



    Wrapping it up



    Getting on top of PST file corruption is easy when you have inbuilt utilities like ScanPST.exe. However, such utilities fail when severe corruption strikes. Thus, keeping reliable professional software like Stellar Phoenix Outlook PST Repair handy is the best way to handle such errors.



    References:

    https://social.technet.microsoft.com/Forums/Lync/en-US/2d310378-c496-4390-bdfd-3d4257912e2e/corrupted-pst-files-fatal-error-80040818?forum=outlook

    PST Repair Tool to Recover All Outlook Mailbox Items – Free Trial

    Related:

    • No Related Posts

    SEP Application and Device Control (sysfer.dll) blocking McAfee Validation Trust Protection (mfevtps.exe) service from running

    I need a solution

    Hi,

    I’m using SEPM 14 MP2 and having issue in running McAfee Client Proxy (MCP) version 2.3.2.251 installed on Windows 10 (version 1703).

    MCP services run fine when SEP is installed without Application and Device Control feature. I have seen some threads which mention that Symantec injects sysfer.dll into processes for ADC.

    I have added following McAfee files and folders exception but it still doesn’t help in starting McAfee Validation Trust Protection Service (mfevtps.exe).

    However, if I add C:WindowsSystem32 (not including subfolder) under Application Control exception then the services run fine.

    How can I troubleshoot or narrow it down further to the file which is getting called by mfevtps.exe service and getting blocked?

    Exceptions in place (includes subfolders):

    1. C:Program FilesCommon FilesMcAfee
    2. c:program filesmcafee
    3. c:program files (x86)common filesmcafee
    4. c:windowssystem32mfevtps.exe
    0

    Related:

    • No Related Posts

    PARMGEN JOB KCIJPUSS RC 256 OMEGAMON JVM pax FSUM7143

    I have installed SMP/E maintenance to the product or upgrading OMEGAMON JVM to V540 and I am receiving a RC=0256 when I run the PARMGEN job KCIJPUSS. I have APAR OA53974 (PTF UA94193 – PARMGEN 4Q17) applied and I have the following USS directories set in PARMGEN:

    WCONFIG(SYSA): RTE_USS_RTEDIR /u/omeg/

    WCONFIG($GBL$USR): GBL_USS_TKANJAR_PATH /usr/lpp/kan/bin/IBM

    SYSA is the name of my RTE, directory /u/omeg is mounted READ-WRITE. Why am I seeing this in the output from the KCIJPUSS job?

    pax: FSUM6404 directory “hca_31”: EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/bin”: EDC5141I
    READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to
    “hca_31/bin/libhealthcenter.so”: EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib”: EDC5141I
    READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib/ext”:
    EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib/ext/healthcenter.jar”: EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib/healthcenter.properties”: EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib/s390”:
    EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib/s390/libhcapiplugin.so”: EDC5141I READ-ONLY FILE SYSTEM.

    pax: FSUM7143 cannot create parent directory to “hca_31/lib/s390/libhealthcenter.so”: EDC5141I READ-ONLY FILE SYSTEM.

    Related:

    • No Related Posts