Relevant Products: Signature Manager Exchange Edition | Signature Manager Outlook Edition | Auto Responder
Scenario
You are using the Template Editor alongside one of our server clients in a multi-server environment. But, 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.
Reason
When a change is made in the Template Editor and published to the server, it executes this change using the rights of the user operating the template editor.
The published change triggers 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.
Resolution
To resolve this issue:
- For the Template Editor, set up the User Computer Object and User Account with Full Control permissions in the Template Library shared folder, stored on the Signature Manager Server.
These permissions need to be set on the Security and Share tabs. - For Remote Deployment with the Template Editor, set up the Network Service and the Server Computer Object with Full Control permissions on the Deployment Share.
Note: For more information on configuring Remote Deployment, including setting permissions on the share, see Remote Deployment - Configuration Synchronisation.