Upgrading from v4.x and Earlier

There are a number of key changes between v4.x and earlier, and v10.x, as follows:

•The Deployment Tool (sign.exe) has been replaced by a new Email Signature Manager Agent that runs on users’ computers seamlessly updating Outlook signatures at configured intervals. The new Agent gets signature settings from the Client Access Service or, in the case of remote users, from the user's mailbox using Exchange Web Services.

•The Access database (settings.mdb) has been replaced by a new Built-in Database that can scale to any number of users and which does not require sharing on a network share.

•A new Email Signature Manager Service is now responsible for generating Outlook signatures and deploying OWA signatures to users’ mailboxes using EWS. In addition it also generates signatures for use by the new Email Signature Manager Transport Agent to inject into emails sent from mobile devices when using On-Premises Exchange Server.

You should upgrade from v4.x and earlier using following these steps:

1.Determine the type of database you are presently using (open the Settings Database dialog) and complete the appropriate step:
 

è If you are using an Access database (typically, settings.mdb), move it from its current location (i.e. the shared folder) to a secure location and take a backup copy.

è If you are using SQL Server, take a full backup.

2.Determine how the old Deployment Tool (sign.exe) is currently executed by the users in your organization and complete the appropriate step:
 
è If you are running it from a logon script, remove the call to it from that logon script and delete sign.exe from your shared folder.
è If you are using GPO to deploy it using the MSI package, delete the GPO that installs it (this will ensure that it is uninstalled when your users logon to their machines).
 

3.Uninstall the current version using Windows Control Panel. When prompted, you should remove the current database (make sure to backup the database first) and settings.
 

4.Create a service account for use with the new Email Signature Manager Service.
 

5.One server (and one server only) in your organization will need to have a Full Installation of the product.

6.Complete the upgrade process.