CodeTwo Signatures Add-in for Outlook - global installation & updating

Follow this guide for step-by-step instructions on how to automatically install and update CodeTwo Signatures Add-in for Outlook for users in your organization using GPO. You can deploy the add-in for all users, selected security groups or OUs. Use the links below for instructions (if you prefer individual users to install the add-in manually on their machines, see this guide).

Read this before you install

For the add-in to work, the CodeTwo software needs to work in client-side or combo mode (learn more about signature modes). You also need to prepare an email signature template and assign users who should get it. To do so, create and set up a client-side signature rule(s) in the Manage Signatures App by following our Quick guide.

The add-in requires .Net Framework 4.7.2 installed on users' machines to work correctly.

To keep synchronizing signatures, the add-in will automatically turn off the Roaming Signatures (cloud signatures) feature in Outlook when the feature is released by Microsoft. Learn more

Deploy the add-in to the whole organization

Follow the steps below to install CodeTwo Signatures Add-in for Outlook for the whole organization.

  1. Download CodeTwo Signatures Add-in for Outlook. To do so, log in to CodeTwo Admin Panel, go to the Tenants tab and click a tenant name (or the ESIG for O365 settings button2 13px button next to it) to access tenant management pages. Use the menu on the left to go to Signature options > Client-side > Signatures add-in for Outlook and click the download link (Fig. 1.). Download the MSI installation file to a shared network location.

ESIG 365 signatures add-in for Outlook page
Fig. 1. CodeTwo Signatures Add-in for Outlook installation instructions in CodeTwo Admin Panel.

  1. On your Windows Server, press Win + R to launch the Run console, type gpmc.msc and click OK (Fig. 2.) to open the Group Policy Management Editor.

Run group policy management console
Fig. 2. Using the Run console to launch the Group Policy Management Editor.

  1. Go to Forest > Domains, right-click your domain and choose Create a GPO in this domain, and Link it here... (Fig. 3.).

Create a new GPO and link it
Fig. 3. Create a new GPO in your domain.

  1. Name your new GPO, set Source Starter GPO as none (Fig. 4.).

Name the new GPO
Fig. 4. Name the new GPO.

  1. Right-click the newly created GPO and choose Edit... from the shortcut menu (Fig. 5.).

Edit GPO
Fig. 5. Edit the new GPO.

  1. Go to User Configuration > Policies > Software Settings, right-click Software installation and choose New > Package from the shortcut menu (Fig. 6.).

GPO install software package
Fig. 6. Create a new software deployment package.

  1. Select the package from the network share (Fig. 7.) specified in Step 1.

GPO pick CodeTwo Add-in installer
Fig. 7. Select the CodeTwo Signatures Add-in for Outlook.

  1. In the new window, select Assigned and click OK (Fig. 8.).

GPO deploy software assigned
Fig. 8. Choose the deployment method.

  1. Double-click the newly created package (Fig. 9.).

GPO double-click CodeTwo Addin
Fig. 9. Double-click the deployment package.

  1. On the Deployment tab, select Install this application at logon, then select Basic and click OK (Fig. 10.). You can close the Group Policy Management Editor afterwards.

Set add-in installation properties
Fig. 10. Set up add-in deployment properties.

  1. The next time a user in your organization restarts their machine and logs in, CodeTwo Signatures Add-in for Outlook should be installed automatically at startup (Fig. 11.)

GPO add-in installed automatically
Fig. 11. CodeTwo Signatures Add-in for Outlook is being installed at system startup.

  1. (Optional) If the add-in is not installed, after the restart, it might be that the GPO settings have not propagated yet. You can use the gpupdate /force command in the Run (Windows +R) console  on the client’s machine to force-apply the GPO settings. After the user logs out and logs in, the add-in should be installed immediately.
  2. After installation, the add-in is available in Outlook and opens in the right pane. (Fig. 12.). Users can change its width to resize it. Using a dedicated button on the ribbon hides/shows the add-in pane.

ESIG 365 Signatures Add-in for Outlook first v3
Fig. 12. This is how CodeTwo signatures add-in appears in Outlook right after installation.

  1. To have CodeTwo signatures automatically added to Outlook, each user needs to click Sign in in the add-in pane. When a Microsoft sign-in screen appears, a user needs to sign in using their Office 365 work account credentials and accept the permissions to synchronize the add-in with Outlook and get signatures.
  2. When a user is signed in, the add-in pane shows signatures that are available for them. Depending on your organization's settings, these signatures can be added automatically (when users compose a new message or reply to/forward a message) or users can add them on their own in compose mode in Outlook, just as they would normally add Outlook signatures: they need to go to the Message tab, click Signature on the ribbon and choose any signature that is available. Learn how to use the add-in.

Deploy the add-in to a security group

This section explains how to apply the GPO which installs CodeTwo Signatures Add-in for Outlook for all members of a security group.

  1. Follow steps 1-4 from section Deploy the add-in to the whole organization.
  2. Select the newly created GPO. In the Security Filtering section, click Add (Fig. 13.) and select the security group or (groups) to which you want to deploy the add-in.

Apply GPO for a security group
Fig. 13. Filtering GPO deployment for a security group.

  1. On the Delegation tab, make sure the security group(s) you have chosen in the previous step and the Authenticated Users group are all listed (Fig. 14.). Use the Add button if any group is missing. Next, click Advanced to manage group permissions.

GPO delegation tab
Fig. 14. GPO delegation tab.

  1. For the GPO to work correctly, you need to assign Read permissions to the Authenticated Users group (Fig. 15., left), and assign the Read and Apply group policy permissions (Fig. 15., right) to the security group(s) you selected for the add-in deployment.

GPO Delegation rights for security groups
Fig. 15. Delegation rights for security groups.

  1. Follow steps 5-15 from section Deploy the add-in to the whole organization, to deploy the add-in for the chosen security group(s).

Deploy add-in to an Organizational Unit (OU)

It is also possible to deploy CodeTwo Signatures Add-in for Outlook to a chosen OU. To do that, follow all the steps from section Deploy the add-in to the whole organization but in step 3, instead of right-clicking your domain, right-click the OU for which you want to have the add-in installed (Fig. 16.).

Deploying GPO for Organizational Unit
Fig.16. Create a GPO for an Organizational Unit.

How to update the add-in

When the CodeTwo Signatures Add-in for Outlook is installed via GPO, the administrator can control when to update it for users in the organization.

Info

If the add-in has been installed manually by users, it will be updated to the newest version automatically.

To update the CodeTwo add-in distributed via GPO to the most recent version, follow the steps below:

  1. Log in to CodeTwo Admin Panel, go to the Tenants tab and click a tenant name (or the ESIG for O365 settings button2 13px button next to it) to access tenant management options. Use the left menu to access Signature options > Client-side > Signatures add-in for Outlook. On this page, click the download link (Fig. 1.) to download the most recent MSI installation file to a shared network location.
  2. On your Windows Server, open the Group Policy Management Editor, find the GPO you have used to deploy CodeTwo Signatures Add-in for Outlook, and follow steps 2 and 5 from Deploy the add-in to the whole organization to start editing it.
  3. Go to User Configuration > Policies > Software Settings and you should see the software package you previously deployed. Right-click below it and click New > Package (Fig. 17.).

Deploying a new software installation package
Fig. 17. Deploying a new software installation package.

  1. Choose the .msi file you just downloaded (in step 1) and click Open (Fig. 18.).

Opening the add-in installation file
Fig. 18. Opening the add-in installation file.

  1. In the new window, choose Advanced as the deployment method (Fig. 19.).

Choosing the Advanced deployment method.
Fig. 19. Choosing the Advanced deployment method.

  1. Deployment settings’ window opens automatically. On the Deployment tab (Fig. 20.) choose the Assigned deployment type, highlight the Install this application at logon checkbox and select Basic user interface options.

Setting the deployment options.
Fig. 20. Setting the deployment options.

  1. Go to the Upgrades tab (Fig. 21.), click Add and choose the software package you have deployed previously. The new package will upgrade the previously deployed add-in to the newest version. Click OK in both windows and close the Group Policy Management Editor.

Adding the Upgrade Package.
Fig. 21. Adding the Upgrade Package.

  1. The next time the users defined in your GPO’s scope log on to their machines, the add-in should be updated automatically. You can use the gpupdate /force command in the Run (Windows +R) console on each user’s machine to force the GPO settings to apply immediately. After the user logs off their Windows account and logs on again, the add-in will be updated automatically to the new version.

See next

CodeTwo Signatures Add-in for Outlook - learn how to use the add-in in your Outlook

Was this information useful?