...
Right after the installation of the Office add-in, it can be distributed to users fairly easily, since no installation on the users device is required (but optional).
There are two ways to deploy the add-in:
| Status | ||||
|---|---|---|---|---|
|
...
Learn on this page how to deploy the Office add-in centrally to all users.
...
| Status | ||||
|---|---|---|---|---|
|
...
Responsibility
The central deployment of the Office add-in
...
needs to be done via
...
the Microsoft admin.
| Info |
|---|
📌 Please follow instructions if /wiki/spaces/TSD/pages/3838476295 |
Deployment via Microsoft 365
If you want to deploy the Office add-in centrally to all or only to a certain subset for your users, there are two options. If required by the guide, please use this AppSource listing: Office Add-in in AppSource: https://appsource.microsoft.com/de/product/office/WA104381095.
Via Office 365 admin center
📌 Please check this guide in the official https://docs.microsoft.com/en-us/office365/admin/manage/manage-deployment-of-add-ins?view=o365-worldwide on how to do this.
Via centralized deployment Powershell commands
📌 If you prefer to use powershell commands, you can use this guide.
...
Deployment via Exchange on Premise
You can deploy the Office add-in on an Exchange server centrally, by using EAC or Powershell. Please read the guide in the official documentation: Install or remove Office add-ins.
...
The COM add-in comes as an executable, installable file (.exe or .msi), which can only be used on Windows computers.
Depending on your environment, one of the following deployment methods can be used.
| Info |
|---|
The COM add-in is not available on other platforms. |
Depending on your environment, one of the following deployment methods can be used.
Responsibility
The central deployment of the COM add-in needs to be done via the Microsoft admin.
| Info |
|---|
📌 Please follow instructions if /wiki/spaces/TSD/pages/3782410275 |
Admin guide (per user installer)
If you just want to test the add-in first, we recommend starting with the “Per User” “per user” installer, as it’s the most easiest to start with.
Per User
The per-user installer is the default download in the Jira admin area.
If you quickly want to get started or distribute this to your users manually, this is usually the best option. It has the following benefits:
Does not require administrative rights to install.
Has an automatic updater, which will keep the add-in fresh.
Download per-user installer (.exe)
...
If you do not want this, and instead prefer an installation to %ProgramFiles%, please check the other installer types.
Automatic updater
If you do not use a central software deployment at your company, keeping the users computer up to date is usually quite hard. For this reason, most popular software features an automatic update routine, which will keep the software up to date. Chrome & Firefox are certainly the most popular examples.
For this reason, we also ship the per-user installer with an auto-updater. It will check for new versions of our add-in twice per day.
...
Internally, we currently have multiple release channels which cannot be chosen (yet). As we are currently early in the stage of rolling out V3, we try to release updates more often (every second week). This will become less frequent starting early 2020, at least for users not in a fast channel.
...
Deploy centrally (on Citrix/Terminal
...
server/VDI)
To install the COM add-in on a central VM or virtualized environment, we recommend using the per-machine installer, which you can download from the “More Options” button in Jira. If you do not want to have an automatic updater in place, you can also use this option.
...
It is possible to add a default configuration for the COM add-in. Most importantly it can be used to default the Jira url to make it easier for the users. It requires a dataStore.json file in the Installation folder. This configuration file will get copied into the user-specific AppData folder on first-use.
Create the configuration file
You can download an example file here and adjust to your needs. The example contains all settings to adjust and a server system configured.
...
| Code Block |
|---|
%Program Files%/Outlook Email for Jira/data |
Software Deployment Tools
We create our installer using the “AdvancedInstaller” tool. We provide a bootstrapped .exe-version, as well as a bare .msi-file. You should be able to use either of those files with the most popular software deployment tools, such as SCCM. Both files support all common Windows Installer command line switches, e.g. /qn for silent installs.
...