This software has been discontinued. If your organization uses Office 365, check out
CodeTwo Email Signatures for Office 365.
Supported platforms and requirements
CodeTwo Email Signatures for Email Clients is designed to work in Windows operated networks (either domain or workgroup) with or without Exchange Server or Exchange Online. There are two main components that have to be installed. Each has a different purpose and slightly different requirements. Study the description and table below to get an overview of supported systems and requirements enabling its smooth and uninterrupted operation.
CodeTwo Email Signatures for Email Clients Administration Panel is a set of components (Updating Service, Administration Panel) allowing administrative management and responsible for updating signatures on Exchange, Office 365 and pushing signatures changes to Client Apps.
CodeTwo Email Signatures for Email Clients Client Apps insert signatures to emails sent from Outlook.
| Software components | |
|---|---|
| Server side: | One instance of Administration Panel must be installed within local network. |
| User side: | End-users must install Client Apps if they wish to add signatures to emails sent from MS Outlook or OWA on Exchange 2007. |
| Administration Panel | |
|---|---|
| Required permissions: | Local Administrator rights are necessary to install and use Administration Panel module. |
| The Administrator's account used for establishing a connection to Exchange Server on-premises or Exchange Online needs to have impersonation rights granted on users' mailboxes. By default, such rights are granted to users with the Global Admin role (Exchange Online / Office 365) and to members of the Organization Management group (on-premises Exchange Server). Google Apps (G Suite) require some additional configuration steps. See our KB for Role Based Access Control (RBAC) compliance. | |
| Multi-factor authentication (MFA) is supported. Be sure to use the app password instead of your regular password when configuring a connection to an Office 365 server. Learn more | |
| Requirements: |
(*) Make sure your operating system includes the latest updates. Learn more. |
| Client Apps | |
| Required permissions: | Local Administrator rights are necessary to install Client app manually. Automatic installation via GPO or SCCM does not require the Local Administrators' rights on the target machine. |
| Requirements: |
|
| Other | |
|---|---|
| Hybrid setup support | The software will work with hybrid setups providing proper, separate policies (OWA / Office 365) are configured. Service accounts must have mailboxes in desired target environments. |
| ADFS is not yet supported. Single Sign On (SSO)-enabled accounts may be used for target server connection configuration but only when a UPN in a non-federated target domain address is used (e.g. *.onmicrosoft.com). | |
| Notes and warnings: | Outlook Add-in works only with Outlook for Windows. Outlook for Mac is not supported. |
| In non-domain environments, the program's components must not be installed together with the 64-bit version of Microsoft Outlook. | |
| Supported email clients | ||
|---|---|---|
| Category | Application | Support |
| Exchange Server (on-premises) |
OWA 2007 |
|
| OWA 2010 |
|
|
| OWA 2013 |
|
|
| OWA 2016 |
|
|
| Exchange Online (Office 365) |
OWA 365 |
|
| MS Outlook for Windows PC |
Outlook 2007 |
|
| Outlook 2010 |
|
|
| Outlook 2013 (including click-to-run) |
|
|
| Outlook 2016 (including click-to-run) |
|
|
| Google Apps (G Suite) | Gmail webmail |
|
| Inbox by Gmail |
|
|
| Android mobile apps |
Native mail app |
|
| Microsoft Outlook |
|
|
| iOS mobile apps |
Native mail app |
|
| Microsoft Outlook |
|
|
| Windows Phone mobile apps |
Native mail app |
|
See also
Installation process - this article describes step-by-step how to install and configure the program.