How To Add Sharefile To Outlook

citrix-sharefile-outlook-plugin
One of the near popular tools for Citrix ShareFile is the ShareFile Outlook Plug-in. It'south a very lightweight install that allows a user to use ShareFile to share and asking files without always having to leave Outlook. The way the plugin works is ingenious and leverages the user's existing electronic mail attachment workflow, they don't have to larn a new way of doing things. Information technology volition generate a spider web link and embed it into the body of the email automatically if the file is detected to exist over a certain size (5 MB is the default and you can set it to any you like). When the user sends the message, that'south when the file is actually uploaded into the ShareFile environment. For this usability factor alone information technology has become what I would telephone call a critical tool you lot need to deploy as role of every Citrix ShareFile deployment. The ShareFile Sync for Windows physical endpoints, ShareFile On-Need Sync for XenApp/XenDesktop, and the newer ShareFile Drive Mapper are also of import clients you should leverage in your environment but goose egg is an essential equally the ShareFile Outlook Plugin in my opinion.

Near the Citrix ShareFile Outlook Plug-in

The description from the download page does a great job summarizing what the Outlook plugin offers:

The ShareFile Outlook Plug-in automatically detects and uploads attachments to your ShareFile account and provides the recipient with a link to the attachment in the body of the electronic mail. This integration provides users with the ability to transport large attachments via email with ease and verify attachments are delivered securely. This plug-in supports both 32-bit and 64-chip versions of Outlook 2007, 2010, 2013 and 2016. ShareFile business relationship authentication is supported as well as accounts using Active Directory credentials and Single Sign On (SSO).

The latest version of the plugins is 4.0 which changes the plugin options UI (merely options, not the actual attach and request UI) also equally bring some additional features many people have been waiting for. The biggest addition is back up for View-Only sharing. Friendly reminder, if yous leverage the View But Sharing Option, retrieve in addition to getting Citrix ShareFile Support to flip it on the back end, you lot may demand to make some content switching changes on your NetScaler depending on how your environs is setup. In most organizations I've come across these days I've not had to do this:

http://docs.citrix.com/en-u.s.a./storagezones-controller/3-4/sf-install-storagezones/sf-deploy-cfg-netscaler-sorcerer.html

If you practise things right yous should run across something similar this when yous share a file in View Only mode:

When downloading the plugin for XenDesktop/XenApp usage on a master prototype for use with Provisioning Services, make certain you download the per machine .msi package, it will be the third one downwardly:

The plugin options UI now looks like this:

the per email Attach Files options (aka Use Custom Settings) now looks like this:

and the per email Request Files options (aka Use Custom Settings) looks similar this:

Using AppSense Environment Director to do a controlled deployment

Pooled not-persistent VDI environments using Citrix PVS usually have 1 master "gold" image with all necessary apps baked in, just a cadre set up of apps baked in, or no apps baked in with everything streamed in via XenApp or App-Five or even any number of other app commitment methods using layering, masking, containerization, etc. such as AppDisk, FSLogix, Liquidware Labs, Unidesk, Turbo, etc. You can even apply a combination of technologies (and believe me, many companies practise). The one matter I want to stress no matter what method you are using, if you are wanting to deploy a whole other master image just for a gradual deployment of an Outlook plugin you're doing it wrong. The whole point of PVS is to accept the OS layer managed centrally while keeping the app layer separately managed and flexible. I have to brand sure and say this because I have to explain this commitment concept to people virtually weekly at present. It's too easy to make a mistake and have to deal with image sprawl and all the headache that goes with it. Don't manage your PVS environment this way.

Since the Citrix ShareFile Outlook plugin is an Outlook Add-In you can't really gradually deploy it to your user base in a controlled manner the same way as whatever other app in a pooled VDI environs. In environments where AppSense Application Manager is being used to enforce awarding usage and licensing, you simply enforce the app policies at the executable level. You can't really do this with an Outlook plugin since it runs under the OUTLOOK.EXE process. Trying to enforce a gradual deployment of the Outlook plugin at that process level would crusade many users to not be able to use Outlook and that's commonly frowned upon in most enterprise environments. So the elementary answer is to use AppSense Environment Manager to condition out the ShareFile Outlook Plugin to a security group. The security group will contain users that volition be allowed to use the ShareFile Outlook Plugin so you tin perform a controlled roll out. This will permit you to give access to the plugin to only those that are role of your airplane pilot/QA testing until y'all determine to flip the switch and requite your whole user base of operations access.

Here are the steps you lot need to perform in your AppSense Surround Manager config:

i. Create a new Pre-Desktop node in your AppSense config for the ShareFile Outlook Plugin.

2. Add together any SSO related keys you lot may need. If you are using AD FS, SAML IdP, etc. you will need these iii keys:

To break these keys down:

Main central = HKEY_CURRENT_USER
Sub fundamental = Software\Citrix\ShareFile\SSO
Value proper noun = Method
Value type = REG_SZ
Value = saml-forms

Note, depending on your environs at that place'southward a few options here:

'standard': Authentication will exist done with username/countersign entered into the plug-in options menu
'saml-basic': Uses SAML provider to cosign users to ShareFile using their domain (not ShareFile) username/password in the options menu.
'saml-integrated': Uses SAML provider to authenticate users to ShareFile using their Windows credentials
'saml-forms': Uses SAML provider to cosign users through forms authentication to ShareFile using their domain (not ShareFile) username/countersign in the options menu.
'receiver': Uses the Receiver/ FollowMeData authentication to sign a user into ShareFile

Primary central = HKEY_CURRENT_USER
Sub primal = Software\Citrix\ShareFile\SSO
Value proper noun = Subdomain
Value blazon = REG_SZ
Value = yourcompanyname

Main central = HKEY_CURRENT_USER
Sub cardinal = Software\Citrix\ShareFile\SSO
Value proper name = UserConfigurable
Value blazon = REG_DWORD
Value = 00000000 (Hexadecimal)

3. At present permit's move on to the conditioning office. The ShareFile Outlook Addin is controlled past a subkey in your registry called Malone.AddinModule. So we demand to create an If Else Group like this:

to break this downwardly, the "If Citrix ShareFile Plugin Access" portion should exist the security group that permits the ShareFile Outlook Plugin to run. All users in this group will exist able to employ the plugin:

The setting for the If is to set the registry value to allow the plugin on the Malone.AddinModule. In this example we need to set it to a value of 00000003 which allows it to run:

Main cardinal = HKEY_CURRENT_USER
Sub key = Software\Microsoft\Part\Outlook\Addins\Malone.AddinModule
Value proper name = LoadBehavior
Value blazon = REG_DWORD
Value = 00000003 (Hexadecimal)

4. Lastly nosotros move on to the Else function. We demand to tell Malone.AddinModule to not allow the plugin to run for all other users by using a value of 00000002.

Master key = HKEY_CURRENT_USER
Sub key = Software\Microsoft\Office\Outlook\Addins\Malone.AddinModule
Value name = LoadBehavior
Value type = REG_DWORD
Value = 00000002 (Hexadecimal)

And that's it! Test logging into a virtual desktop with with a user that has admission vs. a user that does non. Hope this helps. Delight leave a comment or questions beneath if y'all demand aid.

Jason Samuel lives in Houston, TX with a chief focus on strategic advisory and architecture of finish-user computing, security, enterprise mobility, virtualization, and deject technologies from Citrix, Microsoft, & VMware. He too has an extensive background in web architecture and networking over his 20+ yr career in IT. He is an Author, Speaker, and Local User Grouping Community Leader. He is certified in several technologies and is 1 of 63 people globally that is a recipient of the prestigious Citrix Engineering Professional (CTP) laurels. He is 1 of 42 people in the earth that has been awarded every bit a VMware EUC Champion and VMware vExpert. He is a featured author on DABCC which provides the latest IT Customs News on Cloud, Data Center, Desktop, Mobility, Security, Storage, & Virtualization. In his spare time Jason enjoys writing how-to articles and evangelizing the technologies he works with. Disclaimer: The content and opinions expressed in articles and posts are his own and are past no means associated with his employer.