To install the Office Connector (henceforth referred to as "OC"), install an OC the exact same way you would install a Media Manager 5 (MM).

Admin Configuration

Next, download the following file:manifest-localhost.xmllocate the manifest.xml file in the "wwwroot"-folder of the installed OC, and open the file. Alternatively, the file is similar to the following:

Replace all references to localhost, localhost with the OC site reference. E.g. if OC is installed at oc.digizuite.com, then replace localhost with oc.digizuite.com.

The "DisplayName" (title) and the description "Description" should also be changed appropriately. If Centralized Deployment is possible (see Digizuite™ Office Connector 2.0 - 0. Requirements), do the following:

...

there are any labels that need to be changed in the ribbon, they are found in the bottom of the XML file, and can be replaced as one sees fit.

...

Make sure to generate a new ID.

If Centralized Deployment is possible (see Digizuite™ Office Connector 2.0 - 0. Requirements), follow the instructions for "Centralized Deployment" below. 

Otherwise, the OC must be installed separately on all client computers. This can be done for one client computer at a time.

• For Windows users, follow the instructions at: https://docs.microsoft.com/en-us/office/dev/add-ins/

...

• testing/create-a-network-shared-folder-catalog-for-task-pane-and-content-add-ins.

If this approach is used, the "Centralized Deployment" section below can be skipped.

Please note that it might be possible to avoid having to install the OC separately on all client computers. However, this approach has not been tested. The approach can be tried by following the instructions at https://docs.microsoft.com/en-us/office/dev/add-ins/publish/publish-task-pane-and-content-add-ins-to-an-add-in-catalog. This documentation also includes how to access the OC from the client side, and thus, you can skip to the last picture on this page. Please be aware of the limitations of following this approach: Digizuite™ Office Connector 2.0 - 0. Requirements. 

Installing on the client computers

Now make sure that your Office instance is logged inIt involves publishing the OC to an app catalog with an on-premises SharePoint Server. Note that this approach will not make the OC available for Mac users.

Centralized deployment

With an Office 365 admin account, follow the installation steps at: https://docs.microsoft.com/en-us/office/dev/add-ins/publish/centralized-deployment.

To install the OC on client computers, do the following steps for each client.

Installing on client computers

First of all, make sure that you are logged in with your organizational ID in the Office applications.

There are two options for logging in - one is for the licensing of the Office product itself, whereas the other one is for your account.

...

Click the Insert tab in the top of your Office program.

...

In the following dialog, go to ADMIN MANAGED. In here, the connector should OC should now be an option

The Open button will then be available on the insert ribbon page. 

...

You should now have a button called Digizuite to the far right of the connector. Press this button

Login using a user set up to use OC.

Now you should be able to use the connector OC as you'd like to see fit.

If you want to install it for another computer - you need to do the last steps again - starting from the section where you access the Office Add-ins and press ADMIN MANAGED.

If you have installed OC Once you have installed OC on a device for one Office product (e.g. Word), you the OC will automatically get the connector on the be available for the two remaining Office products (e.g. Excel and PowerPoint). 

Updating the manifest file

After updating the manifest file (NOTE: not after updating the website itself), a user might not see the effects of the update immediately. To fix this, try following the steps under "Remove an add-in from local cache" on the user's computer: https://docs.microsoft.com/en-us/office365/enterprise/use-the-centralized-deployment-powershell-cmdlets-to-manage-add-ins?redirectSourcePath=%252farticle%252f94f4e86d-b8e5-42dd-b558-e6092f830ec9#delete-an-add-in