Automating Outlook 2013/2016 Signatures

So now that you have your signatures created in your output directory, we will set up a simple method to deploy these signatures globally through your organization. 


In this example, I will show you have to use our tool to set up a scheduled task to run on logon for each user who's connect to a domain. 

I will use John Smith as an example.

John Smith's domain credentials are as follows: CONTOSO\JSmith

John Smith's Email is:


John's signature file after it has been created would be labeled: jsmith.htm


Before we continue any further, we will need to create a scheduled task on the users machine that will run the Deployment tool from a network location that John Smith will have access too. 

You will create a Basic task, with the following parameters for Triggers and Actions.


Once you've done this, when the user logs out and logs back in, the Outlook Deploy Tool will run and automatically adjust the signature settings in Outlook to use the new signature that was created for the user. 

There are several ways you can deploy the signatures within your organization, such as using Group Policy or even having the users manually execute the application from the network share in your environment. 

Currently the system relies on the Domain User naming convention being first initial and last name. Generally the login name should match the users email address.

If your organization does not conform to this structure, please contact our support team so we can work with you on customizing this tool to meet your needs.

*Keep in mind there are development rates that will apply*


This tool currently supports Outlook 2013 and 2016.







Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk