Step 1: Enable the Hub

The first step is to enable the Hub on Exchange. 

When can you do this?

You can do this immediately as it has no impact on current users.

To do this we need you to add some permissions via the Microsoft 365 Admin Center. They are documented in the link below. You will have previously added some of these to get CloudFiler working in the first place, so you now just need to add a few more.

NOTE: Ignore the request at the end of the instructions to send us the 3 ID numbers as we already have those. All you need to do is ensure that you have granted the following permissions

These screen shots show how your API permissions and Authentication URIs should be configured once youi have followed the steps detailed in the link at the foot of this page.

These are the API permissions:

…and these are the Authentication URI’s:

So follow this link which takes you to the page where new customers grant CloudFiler permission to access Exchange On-line, and update your settings: Give CloudFiler permission to connect to Exchange Online

As mentioned above, you do not need to send us the 3 ID numbers, you only need to add the required permissions.

Step 2: Test it

We recommend that you test the Hub on your own machine before deploying to all staff.

The Hub provides and number of new features and replaces the following ones. So you first need to un-install these:

• CloudFiler Helper
• CloudFiler Shell Extension
• CloudFiler Location Manager

Ensuring it is not blocked by your anti-virus

The Hub has two main EXEs which you may need to whitelist:

CloudFiler.Bootstrap.exe

CloudFiler.Launcher.exe

You may also find that you need to whitelist the following:

CloudFiler.Authenticator.exe

CloudFiler.LocationManager.exe

CloudFiler.FolderDiscovery.exe

CloudFiler.LegacyLocationDiscovery.exe

CloudFiler.LinkHelper.exe

CloudFiler.ShellIntegration.exe

CloudFiler.AddLocation.exe

CloudFiler.Helper.exe

CloudFiler.BulkImporter.exe

CloudFiler.PublicFolderExport.exe

CloudFiler.CategorySync.exe

CloudFiler.AclRunner.exe

Next install the Hub

You will find it on our Installers page, the URL for which will have been provided via email.

We recommend that you read this Help page as it explains what the Hub provides and has some tips which you are likely to find helpful: The Hub

So now that you are more familiar with it and have hopefully pinned it to your taskbar too, try the following:

Check that the Helper behaviour is working

You will have un-installed the old CloudFiler Helper application which opens emails in Outlook when you double-click them in our Pico search tool, as the Hub now provides this, so first click the Hub's cloudFiler icon in the Windows tray and then try double-clicking an email in Pico. It should open in Outlook.

Next check that the Add Location capability which was previously provided via our Shell Extension, is working.

Open Windows File Explorer, navigate to a folder and right-click it. Select Show more options from the bottom of the list and it should include our three tools:

Select Add Location to CloudFiler 

You should find that this works as expected.

If you are a CloudFiler Admin or are in the CF Admin group, when you right-click the Hub icon you should find that you can launch the Location Manager and that it no longer requires a tenant key.

If all these work as expected, your Hub is working fine and you can now choose a time to deploy it to staff.

Step 3: Deploy to all staff

We recommend that you make your staff aware of what to expect first and this page with help you with that: The Hub

All you then need to do is:

1. Un-install the following from all machines:

• CloudFiler Helper
• CloudFiler Shell Extension

2. Install the Hub on all machines

Installation options

When deploying to many users via a tool like InTune, you can opt to either install it silently in which case it will deploy to the user's tray but won't activate, or you can make it immediately activate, in which case the user will be presented with the authentication prompt upon logging in: