Manage Email Signatures Centrally - For All Users

primehealthgroup · Not too shy to talk Joined: 27 Mar 2008 Posts: 6

Hello again,

More problems Sad

When I create three groups for three seperate email signatures and than setup the groups to each have access to an email signature I find it doesnt work and it loads a defualt signature of eMailSignature Demo. The groups are valid in AD. ie Domain users being one of the groups. Than I have two new groups setup for the other signatures which have priority over the domain account in cockpit.

First how do I make the groups work as I have to manual do it at the moment for each user and that is not going to be feesable for 300 odd users.

Second. Where do I set the defualt signature?

I am running sign 5.0 and cockpit 5.0 and I have verified this from the logfile.

Log file:

--------------- eMailSignature LOG file -------------------
- Started at 23/05/2008 8:37:05 AM
- sign.exe version 5.0.0 has been run for this user.
------------------------------------------------------------

Connection string to settings database:
Provider=sqloledb;Data Source=primesql-srv2\sql2005;Initial Catalog=emailsignaturedb;User Id=<taken out>;Password=<taken out>;
23/05/2008 8:37:06 AM Begin finding user DN
User path: LDAP://DC=prime
23/05/2008 8:37:07 AM End Finddistinguishedname
User: testemail (CN=Test Email,OU=Head Office,OU=Prime Sites,DC=prime)
23/05/2008 8:37:07 AM License Key valid for version. 5
Distinguished name set to CN=Test Email,OU=Head Office,OU=Prime Sites,DC=prime
No property found for group membership (-2147463155)

------------------- Signatures to deploy: -------------------
Default signature: eMailSignature Demo
Reply/forward signature: eMailSignature Demo
Signatures to deploy: eMailSignature Demo
Origin ID (Internal): 1

-------------------------------------------------------------
Office version 2007 detected.
1 signature to deploy.

No signature eMailSignature Demo found in the database.
-------------- eMailSignature END LOG file -----------------
- Finalised at 23/05/2008 8:37:08 AM
------------------------------------------------------------
Status: No signature eMailSignature Demo found
-------------- eMailSignature END LOG file -----------------
- Finalised at 23/05/2008 8:37:08 AM
------------------------------------------------------------
Status: No signature eMailSignature Demo found

Thanks for your help Smile

Jesper Frier · Posted: Fri May 23, 2008 5:47 am Post subject: Group Settings

Deploying to groups you need to be aware of the difference between using Security Groups and Distribution Groups (see link below) and which groups are set as your priority.

Please reply to these questions:

Is everything working OK with 'For all' setting active?
When OK, remove selection; 'These settings always have priority over group settings'.
Are you deploying to Security or Distribution Groups?
Are group belonning found in LDAP://DC=prime as you have this error?

Code:

No property found for group membership (-2147463155)

If you manually have to enter LDAP connection string, please go to Advanced Technical Settings in Edit menu.
Please verify policy settings for specific users running GPResult.exe command line tool.

Please let me know where it went wrong, and we might be able to improve application or documentation.
_________________
</Jesper> | Test Email Signature | Showcase |

primehealthgroup · Not too shy to talk Joined: 27 Mar 2008 Posts: 6

Hi Jesper,

Thanks for your help. To answer your questions:

1. Where is this for all setting? These settings always have priority is ticked from the begining for each group a member is of.

2. These are being deployed as security groups but dont have nested groups inside them.

3. I ran the defult entry in the ldap query and those groups are indeed part of AD as it is Domain Users

4. What policy settings are you after as the signature program is not being run by group Policy.

5. It went wrong when I deployed it from a login script.

Jesper Frier · Posted: Fri May 23, 2008 8:55 am Post subject:

Re. 1) Actions -> Deploy Signatures -> For All .
Please try this before troubleshooting group settings. If this does not work, then groups won't either.

Re. 2) Not using nested Security Groups. OK.

Re. 3) OK.

Re. 4) OK.

Re. 5) Please run Sign.exe from Cockpit. File -> Run Sign.exe. If this works, the problem is your logon script.

New question ... Smile

6) Did you use this script to create your SQL settings DB?. I just spend hours of support yesterday with someone who claimed 'Yes', but didn't ... so please create new DB using the script ad check again.
_________________
</Jesper> | Test Email Signature | Showcase |

primehealthgroup · Not too shy to talk Joined: 27 Mar 2008 Posts: 6

Jesper your a champion Smile

Setting the deploy signatures to all first and than doing the groups worked.

Thank you so much for your help Smile