Role out to clients via Group Policy

1. Create a Group Policy in the root of your domain (or somewhere else in your AD structure, as you see fit.)

2. Unlink this new policy before you start editing it, to make sure it will not affect your users before you are finished testing. When you later have finished testing you can then easily link it to all the appropriate OU’s in your domain. 

3. You now need to assign the VBScript file that DS Manager has created, as logon script.

When you have finished testing the template, then enable the Group policy link again.

Now every time a user logs on to your network the DS Client Application will run on the client an update his signature and settings.

You may already be thinking that it is superfluous to have the signature refreshed every time a logon occurs, especially considering that only rarely does the data in Ad change. But it is not really.

You will need the client to run in any case the check if there is any changes to his/her Account information in AD. And the client can generate a fresh signature in just under 1 second. So there is really no need to try to decide if his account has changed since last time. It is equally fast just to generate always.

Multiple signature

If you consider deploying more than one signature for each user, e.g. a normal one for New mail, and a short version for Reply's, then read this section