If you are an existing customer, this page is designed to help make the transition to the Hub simple:


What are the steps?


    1. Enable the Hub on Exchange
    2. Test it on just your machine
    3. Deploy to all staff



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


API Permissions


This screen shots shows how your API permissions should be configured once you have updated them.




You will already have some of these and just need to add the ones that are missing.



To add them, follow this link to the 365 Admin Centre: 


the Microsoft 365 admin center portal  https://admin.cloud.microsoft/  (Link opens in a new window)


In the search field type App registrations and select App registrations



If you are presented with a page like this, select Identity:



Then select App registrations from the sidebar:



Select All applications and then the CloudFiler that has a Current certificate:




WARNING: If you are editing an existing registration and you see multiple registrations named CloudFiler in the list, edit the one that displays a Current certificate. In addition, DO NOT DELETE the other registrations.




Next select API permissions and then Add a permission:

Select Microsoft Graph

You will see that there are two types of permissions: Delegated and Application. We need to assign both and will start with the Application permissions.


Our aim is to first assign the new Application permissions:


Group.Read.All

MailboxSettings.ReadWrite




We will do the Group.Read.All first, so select Application permissions

Filter for Group.Read.All, you may need to expand the filtered sections - in this example its in the Group section, select Group.Read.All and select Add permissions



Repeat for the MailboxSettings.ReadWrite above.



Adding Delegated permissions

Whereas were were adding Application permissions in the previous steps, we now need to add Delegated permissions.


The steps are nearly identical:


API Permissions | Add a permission | Microsoft Graph | Delegated Permissions | then the required permission


So now add the following Delegated Permissions:



EWS.AccessAsUser.All

Mail.ReadWrite

MailboxSettings.ReadWrite



Pause and check your work


If you have done everything correctly, your settings will be as shown here. Be sure to check that the type (Delegated/Application) is correct for each one.


Authentication URI's


You now need to add these Authentication URI’s:



Pick Authentication and then Add Redirect URI



From the side menu select Mobile and desktop applications



Add the following for Mobile and desktop applications:


cloudfiler://auth

http://localhost:5000

http://localhost
https://login.microsoftonline.com/common/oauth2/nativeclient


You can add them all at once as it will create a new entry field each time you add one:



Check that they are as shown here, then pick the Configure button.


If you have added them correctly they should appear as shown here:

Step 2: Test it


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


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


  • CloudFiler Helper
  • CloudFiler Shell Extension
  • CloudFiler Location Manager


Ensuring it is not blocked by your anti-virus

We have yet to digitally sign the applications so you may need to whitelist our folders or executables as detailed here: Anti-malware exclusion paths


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 you are logged into the Hub


The Hub should appear as an icon in your tray and depending on the installation process, you may already have logged in via Entra.


Check whether you are signed in by right-clicking the tray icon. If you are not signed in, it will offer these options and you will need to select Sign In.


Check that the Helper behaviour is working

You will have uninstalled 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, 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


  1. 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: