Versions Compared

Version Old Version 3 New Version Current
Changes made by

Utkucan Saraç (Unlicensed)

serdar ak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

GEODI Classifier consists of a set of tools for manual and automatic classification. Part of this tool is installed as a GEODI module, with separate client installation for Desktop and Office add-ins.

They are only installed on

  • Outlook Web App

  • Outlook 365

  • Exchange.

Table of Contents

OWA Setup

Separate installation method for individual users or for all users is provided for OWA/Office 365 environment.

Web Service Address: No matter which method you use, you must provide the address used to access OWA. You must add /ews/exchange.asmx at the end. If OWA has an SSL, GEODI must also work with an SSL.

OWA Setup for Single User

Username and password must be given. Username, if it is in the domain, should be written as domain@username, if not, should be written directly. After entering the information, "Install to Server" completes the installation for the relevant user.

...

The bulk installation steps are described below in the "Installation for All Users" step.

OWA Installation for All Users

With this process, we will be able to deploy the OWA plugin to all users defined on the Exchange Admin Center. In the installation tab in the GEODI Classifier settings, we download our xml file that we will use during installation with "Download Manifest".

We click + in the Exchange Admin Center Organization / Add-ons section.

...

On the screen that opens, click Choose File, select our downloaded xml manifest file and upload it. Classifier OWA plugin has started to be distributed to all users in the organization. Depending on the number of people, the distribution process will take between 6-24 hours. In order for the plugin to serve smoothly, the OWA plugin must have access to GEODI.

...

Now our classification plugin can also be used in Outlook, which we access through the browserFor GEODI classifier OWA installation, you have to download Manifest.xml file with the method stated below and then forward it to Exchange Admin.

Table of Contents
stylenone

Tip

Minimum Setup requirements

  1. This extension can be installed on the Outlook Web App , Exchange On-Premises, or Exchange Online.

  2. The OWA server must access the GEODI server, (The mail server requires SSL for GEODI Url)

    1. For Exchange Online GEODI Url must be public.

  3. The user name and password for the token should not be changed. Otherwise, you will have to repeat the installation.

Creating Manifest File

  1. Create the Manifest → You can download the .xml file with “Download Manifest” button in the setup tab.

  2. Load the manifest → Use Add-In upload in Microsoft 365 Admin Center/Built-In Apps for all defined users or desired ones.

  3. After this process, the system will start distribution. Deployment may take 3-24 hours.

...

Troubleshooting

Expand
titleOWA add-in puop-up does not show while sending an e-mail.

  1. Your policy settings may be so, change the settings

  2. For On-Prem Exchange environment: This is an issue that must be solved in Microsoft side. You should take the actions in the link below. It should work afterwards. You don’t have to re-create the manifest file.

https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/outlook-on-send-addins?tabs=classic#install-outlook-add-ins-that-use-on-send

View file
nameEnablingonSenDforclassicOWA.pdf

Expand
titleAdd-in did not activate in OWA e-mail users.

There may be several reasons.

  1. Is the GEODI server running?

  2. Before creating the manifest file, make sure the GEODI URL address in the UI is correct. Otherwise, repeat the installation.

  3. Microsoft OWA servers must see the GEODI server. If you are using Exchange Online, the GEODI address must be public.

  4. SSL must have been defined for the GEODI address. Be sure that SSL is defined and that it is not expired.

Expand
titleAdd-in stopped working!

  1. Is the GEODI server running?

  2. Is the project that is used to create the manifest file still active? If not, revert the project or re-create it. In case of re-creation, the manifest process must be repeated.

  3. Is the TokenUser and its password still valid? If not, the manifest process must be repeated.

Expand
titleDoes Policy changes require Manişfest to be reloaded.

  1. No, all changes applied automatically.

  2. Manifest reload is required in cases like GEODI Url or Tokenuser changes.

Expand
titleCan i create 2 or more manifest?

  1. Yes, It can be done for testing or other requirements. Create multiple projects and manifest files for each.