Deploying signatures for remote users

You can configure your system to deploy signatures to users who work remotely, or use computers that are not joined to the Active Directory domain. To achieve this, you need to:

• Deploy signatures for remote users to a given directory

• Configure an Internet facing Virtual Directory in IIS

• Install a copy of the Exclaimer Outlook Settings Update Client on the remote computer

Define a deployment directory for remote users

There are two options for setting a deployment directory for remote users:

• Option 1 - configure each remote user separately

• Option 2 - have all users retrieve their signature from the same place

The deployment directory can be:

• A UNC path.  For example \\DC1\Outlook Signatures

• A local folder.  For example C:\Outlook Signatures

Network drives (for example Z:\Outlook Signatures) cannot be used.  This is because the service that deploys signatures runs under the LocalSystem account by default.  This account does not have access to the network drives of the logged-on user.

Procedures for both options are detailed below.

Option 1 - configure each remote user separately

For each user requiring deployment of a remote signature, you must edit the configuration file for the network-based ExSync agent.

1. Locate and open the required ExSync.cfg file. This file can be found in the relevant network share, as specified on the settings tab for the selected signature deployment policy - for example:

    

   The number of signature deployment policies found will vary from one organization to another. Many organizations will only ever need the one signature deployment policy that is automatically created when Exclaimer Signature Manager Outlook Edition is installed.

2. Open the ExSync.cfg file in Notepad (or a similar text editing program). The content of this file should be similar to the example shown below:

3. Add the following lines to the configuration file:

[RemoteUsers]

{DefaultSMTPAddress}={RemoteSignatureLocation}

Where {DefaultSMTPAddress} is the SMTP Address of a remote user and {RemoteSignatureLocation} is the location to which you will point the virtual directory.

For example:

[RemoteUsers]

[email protected]=C:\Signature Deployment

The final configuration file should look similar to the example below:

These changes will not take effect until the next time signatures are generated. This can be triggered by saving the configuration in the console. Remember that if multiple signature deployment policies are defined, you may need to update multiple ExSync.cfg files (each signature deployment policy is associated with its own ExSync.cfg file).

Option 2 - configure the product to deploy all user signatures to the same location

1. Open the relevant ExSync.cfg file in Notepad (or a similar text editing program). The content of this file should be similar to the example shown below:

3. Beneath the [Global] section, add the following line:

RemoteSource={RemoteSignatureLocation}

Where{RemoteSignatureLocation} is the location for the virtual directory.

For example:

RemoteSource=C:\Signature Deployment

The final configuration file should look similar to the example below:

Remember that if multiple signature deployment policies are defined, you may need to update multiple ExSync.cfg files (each signature deployment policy is associated with its own ExSync.cfg file).

These changes will allow files to be generated in the specified folder, similar to the following image:

Configuring an Internet facing virtual directory in IIS

The configuration process for both IIS 6 and IIS 7 is detailed in the following sections.

Configuring a virtual directory using IIS 6

1. Open Internet Information Services Manager (inetmgr.exe):

2. Expand nodes and locate the Default Web Site entry:

3. Create a new Virtual Directory (Action > New > Virtual Directory...):

4. Click next to launch the Virtual Directory Creation Wizard:

5. Click next and enter an alias (with which users will connect to this virtual directory):

6. Click next and then Browse to navigate to the Remote Deployment Location (as described previously):

7. Click next to set permissions. Here you can accept default permissions however, only Read permissions are required:

8. Click next to confirm settings and then finish to exit from the wizard:

Now when you check the content of the virtual directory, you will see that deployed signatures are present:

Configuring a virtual directory using IIS 7

1. Open Internet Information Services Manager (inetmgr.exe):

2. Expand nodes and locate the Default Web Site entry:

3. Right-click on the Default Web Site node and select Add Virtual Directory..:

4. Enter an alias and a Deployment Folder Location:

Now when you check the content of the virtual directory, you will see that deployed signatures are present:

Installing the Exclaimer Outlook Settings Update Client on remote computers

The Exclaimer Outlook Settings Update Client must be installed on each remote computer and or computers that are not joined to the Active Directory domain. To achieve this, the following preparation is required:

• Each end user should download the Exclaimer Outlook Settings Update Client (an MSI file) to their computer. This file is added to your Exclaimer Signature Manager Outlook Edition installation directory when the product is first installed. It can be copied from here and distributed to remote users, as required.

• You will need to know the URL of the remote signature location and the SMTP Address for each user's account (your network administrator should be able to provide this information).

The client installation process

1. Double-click the MSI file to launch the Exclaimer Outlook Settings Update Client Setup wizard:

2. Click next to view and accept the License Agreement:

3. Click next to define an installation location. By default, this is set to Program Files:

4. Click next to define user settings for the application. Here, the SMTP Address should be defined as the user's default email address and the Remote Signature Location should be defined as the external Web address of the deployment location for signatures. In our example this will be: 

5. SMTP Address: '[email protected]'

6. Remote Signature Location: 'http://www.mycompany.co.uk/Signatures'

5. Click next to confirm settings:

6. Click install to perform the installation. Upon completion you have the option to immediately start the Remote Client, or it will be started the next time the user logs on to their computer:

7. You can check that ExSync is running by viewing processes in Windows Task Manager:

8. Signatures are now deployed to this computer and can be seen in Microsoft Outlook. If any errors are encountered updating signatures, they will be shown in the Application Event Log of this computer.