Manage Email Signatures centrally from your Desktop - For All Users

Jesper Frier

Step-by-step setup using default MS Access settings DB

Question

How does eMailSignature work? Continue here ...

Double-click video for full view

Copy the settings.mdb to a net share where your users have min. Read/Write/Update permission.

Default installation directory is C:\Program Files\eMailSignature\
Copy Sign.exe to \NETLOGON (Best Practice) or to the same net share as in #1.
Connect Cockit to your settings database.
Setup 'Signatures for all' and 'For Groups'. Users not having group belonging, will use 'Signatures for all' setting.
The default templates pulls information from your Active Directory.
Execute .CMD script to test deployment:

Code:

"\\[DomainController]\NETLOGON\sign.exe" Provider=Microsoft.Jet.OLEDB.4.0;Data Source="\\[FileServer]\[share]\settings.mdb"

Best Practice: Use UNC path and execute Sign.exe from NETLOGON.

Replace 'DomainController' with the name of your Domain Controller.
Replace 'FileServer\share' with the name of your File Server and share name.
Monitor deployment, fix failed users and check that signatures match your settings. Open Outlook and check signatures.
Back up your standard Access settings DB.
When finished testing, execute your script during users logon.

_________________
</Jesper> | Manage Email Signatures from your Desktop | Test Email Signature in All In-boxes | Email Signature Showcase

Jesper Frier · Posted: Sat May 23, 2009 7:06 am Post subject: VBScript instead of bat-file

Further to item 5
If you prefer VBScript:

Jesper Frier

Further to item 5.

Deploying via a Group Policy Object (GPO) logon script:

Locate the Logon scripts folder of the GPO you want to use.
User configuration -> Windows settings -> Script (Logon/Logoff), Logon.

If there is no 'logon.bat' file, create eMailSignature.bat with the following content: