Deployment via Logon Script

In order to deploy signatures and settings via your logon script, simply call sign.exe located on the network share. For example, if the shared folder containing the Symprex Email Signature Manager files is on a server called SERVER in a hidden share called SIGNMGR$, execute the following command from your logon script:

\\SERVER\SIGNMGR$\sign.exe

If the settings database settings.mdb is stored in the same directory as sign.exe, no command-line parameters or settings are required as sign.exe will automatically use the database in the directory it resides in.

If, however, the settings database is not stored in the same directory as sign.exe, or if you are using Microsoft SQL Server, it is necessary to tell sign.exe how to connect to the database, which can be accomplished using one of the following methods:

The result of the deployment to each user is logged to the Email Signature Manager database and is available via the Status Monitor. In the event of any problems that prevent sign.exe from logging results to the database, a log of output and error information can be found in the user’s default TEMP directory on the user’s machine. To open the log, simply open the file %TEMP%\sign.log.

NETLOGON

Using NETLOGON is not recommended, but is possible and works in the same way as using logon script, except that the deployment files are placed in, and called from, the NETLOGON folder.

Note Because the NETLOGON folder is replicated between domain controllers across your organization, you must not put the settings database in the NETLOGON folder; it must be placed in a separate, shared folder that is not replicated and on which the users in your organization have read/write access.

In all other regards, using the NETLOGON folder is the same as using a shared folder. A suitable script is created to execute sign.exe, which is then executed as part of the logon process. You can specify the database connection settings on the command line or via a sign.ini file.