Symprex Email Signature Manager, v5.1.0

Deployment

This chapter explains how to set up the deployment of signatures and settings created with Symprex Email Signature Manager.

 

The most common deployment model is to use a small command line utility, sign.exe, which runs locally on each user's computer (typically during logon) and connects to the central Email Signature Manager database in order to perform the following deployment actions:

 

Deploy the user's signatures, stationery and client settings locally to Outlook.
Deploy the user's signature to OWA on Exchange Server.
Deploy the user's signature to Office 365.
Deploy the user's signature to the Blackberry Enterprise Server database.
Generate the user's signature for the Email Signature Manager Transport Agent to apply to emails sent from mobile devices.

 

There are two ways to set up the usage of sign.exe for the users in your organization:

 

Using Logon Script (the logon script executes sign.exe when the user logs on).
Using Group Policy (a small MSI package installs sign.exe to be executed when the user logs on).

 

Using the Logon Script method is simplest and therefore also recommended for evaluation of Email Signature Manager.

 

There are two ways to configure the central database:

 

Using the Email Signature Manager database.
Using a Microsoft SQL Server database.

 

Using the Email Signature Manager database is simplest and therefore also recommended for evaluation of Email Signature Manager.

 

To get started, please follow these steps:

 

1.Create the central shared folder.
 
2.Configure Email Signature Manager to connect to your database.
 
3.Configure the deployment via logon script or group policy.

 

Service Deployment

 

The Email Signature Manager Deployment Service is used to perform the majority of deployment actions otherwise undertaken by sign.exe. Instead of running on each user's computer, the service is installed on a server (i.e. a central location within your organization's domain), and performs signature deployment and generation at configurable intervals. The primary benefit of using the service is that it can deploy signatures to users who do not log on to the domain and hence are unable to run sign.exe. The service can perform all of the deployment actions detailed above except deployment to Outlook, which must still be accomplished using sign.exe. Indeed, sign.exe will only deploy to Outlook when the service is enabled; all other deployment actions are handled by the service.

 

Mobile Devices

 

Signatures are applied to emails sent from mobile devices (excluding Blackberry devices) using the Email Signature Manager Transport Agent, which processes emails centrally on each Exchange Server within your organization. The Transport Agent needs to be installed and configured if you want to apply signatures to emails sent from your users' Android, iPhone, iPad and Windows Mobile devices.

 

Additional Information

 

For information about setting up the Deployment Service, please see the topic about deployment via the Email Signature Manager Service.

 

For information about setting up the Transport Agent, please see the topic about deployment via the Email Signature Manager Transport Agent.

 

For information about setting up a Email Signature Manager database on Microsoft SQL Server, please see the topic about using Microsoft SQL Server.

 


Copyright © 2013 Symprex Limited. All Rights Reserved.