ShareFile

Deployment of ShareFile for Outlook with Custom Registry Keys

In an enterprise environment, the IT department can configure the plug-in for deployment through the registry settings as given below.

If using Windows Integrated Authentication for Single Sign-On, the user will not be required to sign-in to the Outlook Plug-in. You may need to create the following path if it does not exist:

HKEY_CURRENT_USER\Software\ShareFile\SSO

The following options are required:

Name Description
Subdomain (string) For example, if you log into ShareFile at http://widgetco.sharefile.com this entry would be “widgetco”.
ApiCP (string) To configure the plug-in for use with a ShareFile account on the US Control Plane (e.g. widgetco.sharefile.com), this entry would be “sf-api.com” To configure the plug-in for use with a ShareFile account on the EU Control Plane (e.g. widgetco.sharefile.eu), this entry would be “sf-api.eu”.
AppCP (string) To configure the plug-in for use with a ShareFile account on the US Control Plane (e.g. widgetco.sharefile.com), this entry would be “sharefile.com” To configure the plug-in for use with a ShareFile account on the EU Control Plane (e.g. widgetco.sharefile.eu), this entry would be “sharefile.eu”.

Administrative Installation

  • Download the Per-Machine MSI installer for the ShareFile for Outlook.
  • In order to install ShareFile for Outlook for all users on the PC, the Per-Machine MSI must be used. Do not use the EXE as it is Per-User install context.
  • If upgrading from a Per-User EXE to a Per-Machine MSI, you must first uninstall the Per-User EXE. Click here for instructions on how to perform a Per-Machine upgrade of ShareFile for Outlook.

Note:

The Per-Machine MSI installer does not support Auto-Update.

Deployment of ShareFile for Outlook with Custom Registry Keys