To install the Office Connector (henceforth referred to as "OC"), install the Media Manager 5 as normal. OC is available as a Subapplication of MM. Next, download the following filean OC the exact same way you would install a Media Manager 5 (MM).
Admin Configuration
Next, locate the manifest.xml file in the "wwwroot"-folder of the installed OC, and open the file. Alternatively, the file is similar to the following:
| View file | ||||
|---|---|---|---|---|
|
Replace all references to "localhost", localhost with the OC site reference. E.g. if OC/MM is is installed at "mm oc.digizuite.com", then replace "localhost" with "mm localhost with oc.digizuite.com/oc". .
The "DisplayName" (title) and the "Description" should also be changed appropriately. If there are any labels that needs need to be changed on in the ribbenribbon, they are found in the bottom of the XML file, and can be replaced at your leasure. Now that the XML file is ready, have the Office 365 administrator upload the file, following the documentation hereas 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. It 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
Once that is done, Office needs to be connected to that installation.
This is done by opening an Office program, e.g. Word, going to File → Account, and logging in there, with an account that is part of the organization the plugin was distributed to. .
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.
Go to File → Account and login. The image below shows which is the correct option to login with:
| Note | ||
|---|---|---|
| ||
Logging it with the "wrong option" above, will not have any effect on the OC. Just be aware that, only the option to the left will grant you access to the OC. |
Click the Insert tab in the top of your Office program.
Now click My Add-ins (See image)
In the following dialog, go to ADMIN MANAGED. In here, the 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. Press this button
Login using a user set up to use OC.
Now you should be able to use the OC as you'd like to see fit.
Once you have installed OC on a device for one Office product (e.g. Word), the OC will automatically 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