Domain installation Registered E-mail
  • 5 Minutes to read
  • Dark
  • PDF

Domain installation Registered E-mail

  • Dark
  • PDF

Article Summary

This document has been compiled in the context of installing the Registered E-mail plug-in within a Windows Domain Environment. The installation of applications/plug-ins on a Citrix server is the same as on a 'normal' Terminal Server environment.

However, this document has been written to answer some questions and to illustrate some minor differences.


The plug-in can only be installed when the following conditions are present.

.NET Client Full 4.0

This software consists of a subset of .NET Framework 4 which is optimised for Client Applications.

This package is available for download from:

Visual Studio Tools for Office

This package is necessary for running applications in Microsoft Visual Studio. It is provided free of charge by Microsoft.

The package can be downloaded from:

De installatie

For a standard installation there is no difference from the regular installation. Therefore, the document "Installation Guide Registered E-mail" can be used.

Deployment from Active Directory

The regular MSI deploys the Registered E-mail software automatically and places the basic keys in the registry. It is also possible to place these keys in the registry manually with specific set preferences. For this purpose we have a special domain MSI available:

MSI installer

The domain MSI installer is identical to the regular MSI in terms of installation. Various parameters can be given to the .msi. A few of these parameters are described below and can be used by a system administrator to perform a "silent" installation without the end-user noticing this.

Option to use a .msi installer:

msiexec /Option

Install options:

Installs or configures a product


Administrative install - Installs a product on the network


Advertises a product - m to all users, u to current user

Uninstalls the product

Display options:


Quiet mode, no user interaction


Unattended mode - progress bar only


Sets user interface level
n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)


Help information

The following command will install the software without the user's knowledge.

AangetekendMailensetup<versie>.msi" /passive /quiet

Plug-in available per user

The software is developed in a way that it can be deployed from a GPO. It is also possible to make the add-in available for individual users.

Short explanation

The system administrator ensures that the registry key below is accessible, or inaccessible to users who do not need the plug-in installed.

Standard plug-in:


CU (Current User) plug-in:


Add the following keys here:

DescriptionREG_SZAangetekend Mailen Plugin
FriendlyNameREG_SZAangetekend Mailen
ManifestREG_SZfile:///C:\Program Files\Aangetekend Mailen\Aangetekend Mailen - Outlook plugin\AangetekendMailen_Plugin.vsto|vstolocal

Tip: Preferably create a separate Security Group and add the user to the group.

Extended description

The following steps explain how to implement Group Policy Objects (GPOs) for Active Directory when configuring the Registered Mail Plugin within Microsoft Outlook.

To implement the settings, the group policy object is associated with one or more Active Directory containers, such as a site, a domain or an organisational unit. The settings in the group policy object are then automatically applied to the users and computers whose objects are stored in the Active Directory containers. You can configure the work environment for your employees once and then enforce the associated settings through group policy.

This guide is based on a Windows 2012 R2 environment that is configured with an Active Directory role. These steps will be similar to other configurations.

In this example we will assume the following Active Directory structure:

  • The domain is called Internal.lan
  • The domain controller SVR-001

A member server with the Terminal Server role named TerminalServer1

Step 1: Creating organisational units and assigning computer accounts in them

  1. In the first step, you use the MMC Active Directory - Users and Computers module to create an organisational unit in the domain hierarchy in which the member servers (Terminal Servers) are placed.

    Then move the computer accounts to the relevant new organisational unit.

    Creating organisational units and placing the computer accounts in them

    1. Click Start, click System Administration and then click Active Directory - Users and Computers.
  2. In the navigation pane, right-click Internal.lan, click New, and then click Organization Unit.
  3. Type Servers in the Name box and click OK.
  4. Right-click the newly created Organization Unit Servers, click New, and then click Organization Unit.
  5. Type TerminalServers in the Name box and click OK.
  6. In the navigation pane, click Computers.
  7. In the details pane, right-click TerminalServer1 and then click Move.
  8. In the Move dialog box, click TerminalServers and click OK.

Once you have done this, your screen will look similar to the following image:

Close the Active Directory - Users and Computers module.

Step 2: Create the group policy objects in which the settings are stored

In this step, you create a new Group Policy object. Because it is not yet linked to an organisational unit, the settings you have configured do not yet apply to computers.

Creating the Group Policy objects

  1. Click on Start, click on System Administration, and then click on Group Policy Management.
  2. In the navigation pane Forest: internal.lan, expand Domains and expand: internal.lan.
  3. In the navigation pane, right-click on Group Policy Objects and then click on New.

  1. In the Name box, type the name Aangetekendmailen_User_Policy and click OK.
  2. Select the Group Policy Objects node and your screen will look like the following image:

Step 3: Adding the Group Policy setting for enabling the Registered Mail Plugin on Terminal Servers

  1. Click on SVR-001, in Group Policy Management, click on Group Policy Objects, right-click on Signposting_User_Policy and click on Edit.
  2. In the Group Policy Editor, right-click the top node Policy for Registered Mailing_User_Policy [SVR-001.INTERNAL.LAN] and click Properties.

  1. Select the Disable Computer Configuration Settings check box and click OK.

  1. Click Yes in the Confirm Disable dialogue box and click OK.
  2. In the console tree, under User Configuration, expand the Preferences folder and expand the Windows Settings folder.
  3. Right-click on the Registry node or on a collection folder under the node, point to New and select Collection Item.

  1. In the Name box, type the name AangetekendMail and click OK.
  2. The new collection folder now appears in the console tree.

  1. Right-click on the collection folder, point to New and click on Registry Item to create a registry item in this collection folder.

Now take over the settings as shown in the following illustrations:


- Key Path: Software\Microsoft\Office\Outlook\Addins\AangetekendMailenAddin

Image A:

Image B:

Image C:

Image D:

  1. After all the string values have been created, your screen will look like the following image:

Stap 4: Implementing the initial group policy object with test settings for Registered mail

In this step, you associate the Group Policy object with an organisational unit to apply it to the client computer that is a member of it.

Implementing the Registered Mail settings

  1. On SVR-001, in Group Policy Management, right-click on Terminal Servers in the navigation pane and click on Link an existing Group Policy object.

  1. In the Group Policy Objects list, click on Registered Mailing_User_Policy and click OK.

Configure plugin settings

After deploying the plugin the user will see a one-time startup screen to configure the plugin settings. Entering the server name is essential to be able to use Registered E-mail.

These values are stored in the register, so it is possible to set them in advance.

Go to, or create:


The following values can be entered:

Name (Type = REG_SZ)

























































A detailed explanation per key can be found in the document "Installation manual Registered Email".