Relevant Products: Signature Manager Outlook Edition
Setting up ExSync
To deploy signatures from Exclaimer Signature Manager Outlook Edition to each user's computer, an agent named ExSync needs to be running on each client machine. ExSync is designed to update Outlook signatures regularly, using minimal processing / memory resources.
How do I obtain a copy of ExSync?
Having completed the installation process and the setup wizard, the ExSync agent is automatically copied to your specified deployment share, from where it is run. However, to use ExSync, you need to:
- Set the update mode for ExSync.
- Ensure that ExSync runs automatically on all client computers.
Setting the Update Mode for ExSync
Using Exclaimer Signature Manager Outlook Edition settings, you can set the mode in which Outlook policies are applied to user computers via ExSync. To do this, follow the steps below:
1. Within the Exclaimer console, select the signature deployment policies branch of the console tree.
2. From here, select the required deployment policy. A default deployment policy is created automatically when Exclaimer Signature Manager Outlook Edition is installed and a deployment share is specified in the setup wizard, but additional deployment policies can also be added.
3. Select the Settings tab to view settings for the selected deployment policy.
4. Set the frequency with which ExSync should check for new signatures (in minutes) or choose to update once at runtime only. Selecting once at runtime only sets ExSync to update immediately and then to close down, whilst defining a set frequency updates at continuous intervals.
5. Save changes.
Ensuring that ExSync runs automatically
Once ExSync has been deployed to client machines, you need to ensure that it runs automatically. To do this, you can use a logon script or GPO.
Deploying via a logon scriptThis method of deployment is useful if you already have a logon script, or if you wish to deploy Exclaimer Signature Manager Outlook Edition signatures to a select number of users for test purposes. For clarity, this process has been documented in three stages:
- Stage 1: Create new or update existing logon.bat.
- Stage 2: Set login.bat as the login script for required users.
- Stage 3: Ask users to log out and log back in
Stage 1: Create new or update existing logon.batIf you do not already have a logon.bat file, you should create one now. To do this:
1. Open Windows Notepad.
2. Create a file named logon.bat.
3. Enter the full UNC path to ExSync, for example: \\Server\Share\exsync.exe.
4. Save the logon.bat file.
5. Copy the logon.bat file to your shared NETLOGON folder.
Stage 2: Set logon.bat as the logon script for required usersIf required, you can set logon.bat as the login script for each Active Directory user. To do this:
1. Open Microsoft's Active Directory management tool, Active Directory Users and Computers.
2. Locate the required user (in the directory structure).
3. Double-click the user name or right-click and select Properties:
4. Select the appropriate tab, in this case Profile.
5. Enter logon.bat into the logon script attribute and click OK.
Stage 3: Ask users to log out and log back inEnsure that your users log off and log back on at least once to activate the new login script.
Deploying via Group Policy Object (GPO)This method of deployment allows you to deploy the login script using your default Group Policy Object (GPO) or to a GPO that you have created. For clarity, this process has been documented in two stages:
- Stage 1: Create new or update existing logon.bat / logon.vbs.
- Stage 2: Propagate the new GPO.
Stage 1: Create new or update existing logon.bat / logon.vbsIf you do not already have a logon.bat file, or a logon.vbs file you should create one now.
1. Locate the logon scripts folder of the required GPO (in the Group Policy Object management console).
2. Open the logon.bat or logon.vbs file. If neither of these files is present, create one.
3. Add the script shown below into the BAT file:
Add the script shown below into the VBS file:
4. Save the logon.bat or logon.vbs file to the logon scripts folder of the GPO (as found in step