Website installation

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

• Create a new website folder and copy the content from SWInstall into the created website folder.

Website configuration

The OC has it own appsettings.json file, identical to the appsettings.json file for MM. Some parameters are of particular interest in the OC.

VersionId

Note that the OC does not have a separate entry in the ConfigManager in the DC. If an OC entry exists, it belongs to the old OC and it will not affect the new one.

Instead, the OC uses an MM configuration, which can be found as a child of the Media Manager 5 node in the ConfigManager. The following options are available:

1. Use an existing MM configuration. If you choose this option, be aware that changing e.g. searches and configuration parameters in the chosen MM configuration will affect the OC. 
   1. Use this option for new installations
2. (Recommended by RND) Create a new child configuration for the OC based on the MM configuration. This makes it possible to change e.g. searches and configuration parameters independently of MM.
3. Use an existing MM configuration.

Create or choose a configuration to use, and then change the "VersionId" parameter in the appsettings.json for the OC appropriately.

SSO

If you want to enable SSO, change "UseFederatedAuthentication" to "true" in the appsettings.json file.

...

• Replace all references to localhost with the OC site reference. E.g. if OC is installed at oc.digizuite.com, then replace localhost with oc.digizuite.com.
• Change the ID to a new, random GUID.
• Change the "DisplayName" (title) and the "Description" appropriately. These affect the displayed text in the ribbon for the end-user.The "DisplayName" is the title in the top of the add-in pane (red line below),
• Go through the labels in the manifest file and ensure that they have the desired values. In particular, the "residOpenButtenText" is the displayed title for the ribbon (blue line below).

Image Added

Manifest deployment

To deploy the manifest and thus make the OC available for users, go through the following steps with an Office 365 admin account: https://docs.microsoft.com/en-us/officemicrosoft-365/devadmin/add-ins/publish/centralized-deployment.

If an issue is encountered, please validate your manifest file with the tool at: https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-manifest

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.manage/manage-deployment-of-add-ins?view=o365-worldwide

Note that the add-in should automatically be pushed to the user for Word, PowerPoint, and Excel. This is also possible for Outlook by choosing the "Fixed" deployment method.

...

Two logins are available. Ensure that the user is logged in with his/her organizational ID in the correct location:

If an issue is encountered while deploying, please validate your manifest file with the tool at: https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-manifest

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

...

in

...

It is possible to configure the OC to show asset crops in the asset list, alongside the original assets:

...