Relevant Products: Signature Manager Exchange Edition | Signature Manager Outlook Edition | Auto Responder
Scenario
You are using Template Editor alongside one of our server clients in a multi-server environment.
When you deploy a change from the Template Editor console to a signature on the server, it does not replicate to all servers in your environment via the Remote Deployment service.
Cause
When a change is made in Template Editor and published to the server, it carries this change out using the rights of the user operating template editor.
This published change will then trigger the Configuration Service for the server product to save the configuration and initiate the Remote Deployment service to deploy these changes to the other servers. This service and the remote deployment process here is carried out under the Local System account of the server.
Resolution
Due to the use of the Local System account for Remote Deployment, you will need to provide the server containing the Template Library share full control (or modify) rights to the Remote Deployment share.
For more details on configuring Remote Deployment including setting permissions on the share, see here