Jesper Frier Certified Professional


Joined: 09 Sep 2006 Posts: 1923 Location: Stoevring, Denmark
|
| Posted: Mon Apr 14, 2008 8:03 am Post subject: Best Practice deployment Guide |
|
|
How does eMailSignature work? Learn more ..
Scenario
This is our recommended Best Practice deployment - First the 'Silent' deployment and then the 'Live' deployment.
The 'Silent' deployment will allow you to monitor, test and fix client deployment issues before going 'Live' - without clients knowing you are testing.
Best Practice step-by-step deployment Guide
- Install eMailSignature on two Windows PCs:
- One console is installed in IT for the initial technical setup.
- One console is installed in Marketing/Communication.
- Connect the console to your Settings Database.
Learn how to setup your default Access settings DB here | Learn how to setup your SQL settings DB here
- Test that you can preview your email signatures without errors.
Only create TXT format for reply signatures. RTF is no longer used, so I would not spend time on this format.
- Setup 'Signatures for All' and OUs/Groups. Users not having group belonging, will use 'Signatures for All' setting.
- Now make the Silent deployment setting.
Use the 'Signature Report' to check your settings.
- Run your logon script, monitor deployment, fix failed users and check that signatures match your Active Directory group settings.
You might consider collecting user created signatures to document your corporate email branding level.
- Remove Silent deployment setting. Now users default and reply/forward signatures are changed according to your settings when they run your logon script.
Using default Access settings database? Backup your settings database in Diagnostics, Tools -> Compact and Repair Settings Database.
_________________ </Jesper> | Manage Email Signatures from your Desktop | Test Email Signature in All In-boxes | Email Signature Showcase |
|