Deploying Multiple Signatures

If you need to create more signatures for the same users, e.g. one for new mail, and one short for reply mail, then you can create more versions of the signature templates, and then call the DS Client several times in sequence.

You can either create a new VBScript file or BAT file manually and then call the automatically produced VBScript files, or you can grab the content from those you want to run an add it to your own VB-Script file.

Example of bat file that creates 3 different signatures:

\\srv015\NETLOGON\Dynamicsignature.exe /I:Standard-UK.ini

\\srv015\NETLOGON\Dynamicsignature.exe /I:Standard-UK-Replymail.ini

\\srv015\NETLOGON\Dynamicsignature.exe /I:French.ini

The same just with VBScript.

Set objShell = CreateObject("WScript.Shell")

objShell.Run "\\company.local\NETLOGON\DynamicSignature\DSClient\DynamicSignature.exe /I:Standard-UK.ini" ,,True

objShell.Run "\\company.local\NETLOGON\DynamicSignature\DSClient\DynamicSignature.exe /I:Standard-UK-Replymail.ini" ,,True

objShell.Run "\\company.local\NETLOGON\DynamicSignature\DSClient\DynamicSignature.exe /I:French.ini" ,,True

Before you set this in motion, just remember that only one of them can be default in Outlook. So you need to tweak the;

ForceSignatureNewMail=True

ForceSignatureReplyMail=False

You must be aware that you should have only one of you signatures forcing the settings in Outlook, or they will keep overruling each other. In the simple scenario with 1 signature for new mails and 1 for reply mail, you should have True/False in one configuration and False/True in the other configuration.

Also you could disable the Balloons in the notification area for all but the first, so users don't get several Balloon pop-up’s.

Address Override

You may have users that works from multiple location. So they would like to have different addresses on multiple signatures.

Example:

The user is generally sitting in location A, but on a regular basis has to travel to location B and perform another function there.

When he is performing this function, he wants a signature that uses the address of location B.

Normally the DS-Client will look up the "Office" field to find out what address to use.

With the /A: parameter you can override what the DS-Client will use for address.

...\DynamicSignature.exe /I:Standard-UK.ini /A:NameOfContact

How to implement:

There are various methods for deploying the signatures, so it depends on what your general approach is. But you would most likely need some group control.

Lets say you have a standard signature for all your UK workers deploy by a Group Policy already.

Then you would like to target a group of sales staff that also works out of a Belgian office.

You could then create a group called "British-In-Belgium" and make a login script that checks the group membership

Logic:

If user is member of British-In-Belgium then

run ...\DynamicSignature.exe /I:Standard-UK.ini /A:BelgiumOffice

Then he will get the same UK signature just with the Belgium address. The DS-Client will ignore what is in the "Office" field of his AD account and use the one provided.

You would of course have to have the BelgiumOffice contact created in the DSAddresses OU.

Force Override

New in 6.5.0

Force for new emails /FN:Yes|No

Force for reply emails /FR:Yes|No

If you are making an elaborate script to map out signatures to groups of users then you may need to override the forcing of signatures as default in Outlook.

E.g. you may have a signature that is deployed to a large group and it is set up to be default for them, Then you also wish to deploy this to a small group where it is only supposed to be an option, not default. Now the force setting is made in the template configuration and it applies to all who get that signature. To override this you can use the override parameters: /FN:Yes|No /FR:Yes|No

Example:

To roll out a signature that doesn't become default the syntax would be

...\DynamicSignature.exe /I:Standard-UK.ini /FN:No /FR:No