Administrative Context

The default deployment option is to use the NETLOGON folder on a domain controller. This offers load balancing and saves bandwidth over WAN connections.

Only administrators have write access to this folder.

And the DS Manager does not give you the opportunity to enter a different set of credentials then those you a running with on the PC or server that you are currently logged into.

So, to deploy a signature you must either be logged in with an account that has permissions to write to the NETLOGON folder, or be running the application in an administrative context.

The DS-Manager will detect if the user is not a member of the "Domain Administrators", and run with a reduced set of possibilities.

It will check direct membership of "Domain Admins". It will not try to traverse nested groups to find out if you are an indirect member of "Domain Admins"

The DS Manager running with reduced feature set looks like this:

Details of the above warning:

We have added support for non-admins so it will be possible to delegate the task of editing templates or campaigns, to staff outside the IT department.

To learn more on the subject of delegating read the chapter in this manual.

Elevation of context

You can elevate the context, by holding shift and right clicking the short-cut, and choosing "Run As..." in the menu. Then you are given opportunity to run it with a different set of credentials. 

On Win8 and Server 2012 you must have the "Require trusted path for credential entry" policy set.

On XP and Win 7 it is possible without further ado.