Installer Guide – empower® AI Assistant

Available from Version: 9.5

Operating System: Windows

Required Permissions: User, IT Admin

Introduction

This document describes the installation process of the empower® AI Assistant on a Windows system as well as important requirements.

Note

If there are any questions reading this document, contact empower® Support.

Hardware Requirements

  • 2GHz or faster processor

  • At least 4GB of RAM

  • At least 250MB of free hard disk space for the installation package

  • Possible HTTPS connection to the empower® Backend Services (Application Server)

    • usually via the default HTTPS port 443

  • Possible HTTP connection to the empower® Activation Server

Software Requirements

  • Operating System: Windows 11

  • 32-bit and 64-bit supported

  • Office 2021*, 2024

  • Office 365 ProPlus and Enterprise E3 and E5

  • .NET Framework Version 4.8 or higher

Important

*End of life as of October 2026.

As of October 2026, empower does no longer support this Office version. Please ensure that you switch to a supported version in time.

For further information from Microsoft, see End of support for Office 2021.

Note

ARM-based systems are not supported.

Installation Files

The installation package consists of two components:

  • .msi file (either per Machine or per User)

    • per User: Installs the empower® AI Assistant only for the current user

    • per Machine: Needs elevated permissions and installs the empower® AI Assistant on the local machine for all users

  • Payload folder

The two components must be stored right next to each other.

The .msi file is the execution file.

Important

Before you start the installation, make sure that all Office applications are closed.

The following files are located in the folder Payload:

  • AccessKey – accesses the backend and checks available prompts.

  • License file: licensekey.txt

    • If the empower® AI Assistant is installed in addition to empower® Solutions, the license file is placed in a subfolder called Suite.

      The file licensekey.txt must then include all solution license keys including the AI Assistant license key.

      AIA_Payload_Solutions.png
      AIA_Payload_Solutions_Suite_Folder.png
    • If the empower® AI Assistant is installed in addition to empower® Products, the license file is placed on the first level of the payload folder.

      The file licensekey.txt must then only include the AI Assistant license key.

      AIA_Payload_Products.png
  • empowerAiBackendUrl – URL for the empower® AI Backend, enables access via the empower® Client.

  • usagetracking.config – optional file for telemetry tracking.

Step-by-Step Installation Guide

The empower® AI Assistant is installed using the installation package that we have made available to you.

Before installing the empower® AI Assistant, check if the installer type corresponds to the installer type that you have used to install the empower® Solutions or Products.

To install the empower® AI Assistant, follow the following steps:

  1. Execute AI Assistant Setup PerMachine.msi or AI Assistant Setup PerUser.msi, depending on the installer type you have received.

  2. Continue the installation by clicking on the button Next.

    If you are using a per Machine installer, a dialog box opens.

Installation_AIA_Welcome.png
  1. Click on the button Yes to allow the .msi file to be executed and installed.

    If you are using a per User installer, this step is skipped.

    The installation starts.

Installation_Allow_Installation.png
  1. Finish the installation by clicking on the button Finish.

Installation_AIA_Finish.png

After Installation

After you have completed the installation, start PowerPoint, Word or Outlook.

After successful installation, the group AI is displayed in the empower® Ribbon in PowerPoint and Word and the button empower AI Assistant is available via the context menu.

AIA_Group_AI_Assistant.png
AIA_Context_PPT.png

After successful installation, the group AI is displayed in Outlook in an open e-mail draft in the tab Message and the button empower AI Assistant is available via the context menu.

AIA_Group_AI_Assistant.png
AIA_Context_Outlook.png

Note

The empower® AI Assistant can also be accessed using the shortcut Ctrl + Alt + A.

License Activation

In order to activate the license, the client needs to be able to connect to the internet.

The licensing server is available under the address activate.empowersuite.com via Port 443.

This connection needs to be allowed in proxy or firewall settings.

Note

If this online activation is not possible, empower® can provide an alternative license file (license.key).

This file needs to be distributed to all machines where no internet activation is possible.

Note

For further information regarding the license activation and storage paths, see Licensing for empower®.

Installation Paths

Once the empower® AI Assistant has been installed, the license key is saved as .txt files on the file system.

If you have installed empower® Products, the license key for the AI Assistant can be accessed via the following path:

per User: %localappdata%\empower\AiAssistant

per Machine: %ProgramData%\empower\AiAssistant

If you have installed empower® Solutions, the license key for the AI Assistant can be accessed via the following path, together with all other solution license keys:

per User: %localappdata%\empower

per Machine: %ProgramData%\empower

Install the empower® AI Assistant via Command-Line

To install the AI Assistant via command-line, the following command can be used:

msiexec /i "[PATH TO .MSI FILE]" /l*v install.log 

Alternatively, you can execute a silent installation using the following command:

msiexec /i "[PATH TO .MSI FILE]" /q /l*v install.log 

Note

The parameter /l*v install.log creates an installation log file in the same path where the .msi file is located.

The following command provides an example for a silent installation per Machine:

msiexec /i "C:\Users\[USERNAME]\Desktop\empower AI Assistant\AI AssistantSetup PerMachine.msi" /q /l*v install.log 

Was this article helpful?

/

Comments

0 comments

Article is closed for comments.