Installing Aligned Elements Web Server
  • Elements SPA Installation
  • Preparing the Windows Server
    • Before you get started
    • Install and Configure SQL Server for Aligned Elements
    • Install .NET 4.8
    • Install/Activate the IIS
    • Enable ASP.NET 4.5/4.6/4.7
    • Optional: IIS Always running part 1
    • Installing Web Platform Installer and Web deploy
    • Install URL Rewrite Module
    • Install IIS Crypto to disable Weak Ciphers and Protocols
  • Deploying the Aligned Elements Web Solution
    • Install the Aligned Elements Web Server Package
    • Setting HTTP Strict Transport Security (HSTS)
    • Optional: Open Ports in the Network on Azure hosted Virtual Machines
    • Optional: Get a SSL certificate from Let’s Encrypt
    • Binding your SSL certificate to the Aligned Elements web site
    • Creating the „Temp“ and „Files“ directories
    • Remove stdole.dll from bin directory
    • Move ElementsSPA.xml from the "App_Data" folder to the "bin" folder
    • Add the Aligned Elements License Files
    • Set the necessary security permissions for directories
    • Optional: IIS Always running part 2
    • Install necessary Unicode Font
    • Install and Configure File Server Resource Manager
  • Configure Application Options in web.config
    • Configure Application Options in web.config
    • Set the Server and connection string
    • Always Require SSL
    • Referring to the Project Templates
    • Email Configuration
    • Word Add-in Configuration and deployment
      • Distribute an Add-in using the Office 365 admin center
      • Distribute the Add-in using sideloading for Windows
      • Distribute the Add-in using sideloading for Mac
    • Optional: Integration of the Aligned Elements Automation Tool
      • Importing Dashboards with Rename using the Automation Script
    • Optional: Enabling Active Directory Integration
  • Optional: Configuration of AI Features
  • Optional: Enable editing of Configuration Sections from the UI
  • Create an Initial User
    • Option 1: Aligned Elements Projects already exist
    • Option 2: New Web server, no Aligned Elements Projects exist
  • Upgrading the Aligned Elements Web Server
    • Upgrading a Server
  • Troubleshooting
    • Generic Server Error
    • Missing version of stdole.dll
    • Missing Dependencies for Txic.dll
    • Error shown: Could not load file or assembly “System.Net.Http”
    • 500 Internal Server Error
    • Error when trying to start application
    • The server is not starting after upgrading to v2.5 SP 4 Part 1
    • The server is not starting after upgrading to v2.5 SP 4 Part II
    • Load a project works but when clicking on a design Item, you are re-directed to the login
    • The application cannot connect to the license server
    • The urls in email notifications are incorrect/missing port information
    • Missing Font
    • Mismatch of server name between Windows-client and Web.
  • Cannot upload Templates
  • Running 'ElementsSPAPackage.deploy.cmd' closes the Command-Prompt window
  • Web.config Settings
    • Settings of the Web.config
  • Configuring Aligned Elements
    • Introduction to rvt templates
    • Type Info Element
    • Compulsory Trace Holders Element
  • Attributes Element
    • String Attribute
    • Enum Attribute
    • Rich Text Attribute
    • Dynamic List Attribute
    • Multiselect Attribute
    • Enum User Attribute
    • Date Time Attribute
    • Boolean Attribute (Checkbox)
    • Int Attribute
    • Double Attribute
    • Int Range Attribute
    • File Attribute
    • Table Attribute
    • Traced Objects Attribute
    • Approval Attribute
  • Trace Holders Element
  • Positive Cues Element
  • Validation Rules Element
    • Traced To Rule
    • Traced From Rule
    • Illegal Trace To Rule
    • Illegal Trace From Rule
    • Obsolete Linked Trace Rule
    • Suspect Trace Rule
    • Missing Execution In TestRun Rule
    • Incoming Suspect Trace Rule
    • Object In File Rule
    • Objects In File Up To Date Rule
    • Not Reviewed Rule
    • Object In Completed Signature Rule
    • Has Open Issue Rule
    • Related Attribute Value Rule
    • Date Overdue Rule
    • Executed From Last Revision Rule
    • Signature Missing Rule
    • Linked Attribute Value Rule
    • Objects In File Not Reviewed Rule
  • Attribute Workflows
    • Sign Action
    • Email Action
    • Set Attribute Action
    • Copy File Action
    • Lock Action
    • Unlock Action
    • Generate Object Action
    • Add PDF Footer
Powered by GitBook
On this page
  • Before you Start
  • Perform the Deployment
  • Troubleshoot Word Add-In problems
  • Word Add-In does not appear

Was this helpful?

  1. Configure Application Options in web.config
  2. Word Add-in Configuration and deployment

Distribute an Add-in using the Office 365 admin center

PreviousWord Add-in Configuration and deploymentNextDistribute the Add-in using sideloading for Windows

Last updated 1 year ago

Was this helpful?

If your organisation uses Microsoft Office 365 and have user licenses that include the use of the Exchange Server, you can deploy the Aligned Elements Word Add-In using the Office 365 Admin Center.

Note that not all Office 365 license types support Centralized Add-In deployment!

From Microsoft: "Centralized deployment of Add-Ins requires that the users are using Microsoft 365 Business licenses (Business Basic, Business Standard, Business Premium), Office 365 Enterprise licenses (E1/E3/E5/F3), or Microsoft 365 Enterprise licenses (E3/E5/F3) (and are signed into Office using their organizational ID), Office 365 Education licenses (A1/A3/A5), or Microsoft 365 Education licenses (A3/A5), and have Exchange Online and active Exchange Online mailboxes.”

Before you Start

Make sure that you have received the Aligned Elements Word Add-In Manifest xml file from your Aligned representative.

Perform the Deployment

Open the Microsoft Office 365 Admin Center and go to Settings/Integrated apps

Select Upload Custom App in the Integrated Apps view:

Select Upload manifest file from device and browse to the add-in manifest xml file using the Choose File button. Then click Next.

You can then assign users who may use the add-in:

It will take up to 10 minutes or so for the add-in to be deployed. You will receive an email notification confirming your successful deployment. Users might need to relaunch ‎Office‎ to see the add-in icon in the ribbon.

Troubleshoot Word Add-In problems

Word Add-In does not appear

1. Sign in to Word with your Office 365 account

Make sure that the user signed in with his/her Office 365 account in word. See upper right corner of Word or go to File => Account to see the currently signed in user account.

If the user is signed in with a non-Office 365 account or an Office 365 account to which the Word Add-In was not distributes, then the Add-In will not appear.

2. Restart Word

You might have to close all open Word applications and restart Word for the Add-In to show up.

3. Office 365 License compatibility issues

Some Office 365 license types do not support Add-In deployments. Make sure you have an Exchange Online mailbox activated for your account.

Microsoft states: “Centralized deployment of add-ins requires that the users are using

  • Microsoft 365 Business licenses (Business Basic, Business Standard, Business Premium)

  • Office 365 Enterprise licenses (E1/E3/E5/F3), or

  • Microsoft 365 Enterprise licenses (E3/E5/F3) (and are signed into Office using their organizational ID),

  • Office 365 Education licenses (A1/A3/A5), or

  • Microsoft 365 Education licenses (A3/A5),

...and have Exchange Online and active Exchange Online mailboxes.”

4. The Deployment takes more time

For large organizations, the deployment can take some time. Make sure that you are on a network that (for some organisations this means being on a VPN) where the deployment can reach your computer.

Source:

https://docs.microsoft.com/en-us/microsoft-365/admin/manage/centralized-deployment-of-add-ins?view=o365-worldwide#requirements