Manage Email Signatures centrally from your Desktop - For All Users

kalpa

Hi!

Some of my users on Windows 2008 Terminal Server / Outlook 2007 are having problems with their signatures beeing removed but not update when a change has been made to the template.

They receive my "blank" Signature for all but NOT their individual settings.

Another strange thing is that if a users have got a logged error from sign.exe. Her status wont get updated until i delete the user from eMailSignature (via the Status Monitor list)?

// Kalle

Jesper Frier · Posted: Wed Nov 04, 2009 1:09 pm Post subject:

I have moved your post from the OWA forum, as I assume your question is about the Outlook client.

kalpa · Posted: Thu Nov 05, 2009 3:06 pm Post subject:

Hello Jesper anf thanks for your reply.

The problem (as the subject implies) is that these users have an empty log, it's all blank!?

And the "Settings for all" isn't overruled by the individual ones, rather merged as they all receive my two defrault signatures AND the blank one I set as "for all"??

// Kalle

Jesper Frier

This could imply that you run Sign.exe version 7 on an old settings database version 5.

Open Cockpit 7 and verify that your database is OK;
Diagnostics -> Check Settings Database Consistency.

If you are lost, please ZIP your settings.mdb file and forward to me.
_________________
</Jesper> | Manage Email Signatures from your Desktop | Test Email Signature in All In-boxes | Email Signature Showcase

kalpa · Posted: Fri Nov 06, 2009 9:36 am Post subject:

No errors in there, everything is OK (besides the spelling on checking):
Cheking table campaign - OK
Cheking table categories - OK
Cheking table disclaimer - OK
Cheking table general - OK
Cheking table License - OK
Cheking table livemessage - OK
Cheking table lgdaCampaignGroups - OK
Cheking table lgdaDefault - OK
Cheking table lgdaGroups - OK
Cheking table lgdaNoUsers - OK
Cheking table lgdaUsers - OK
Cheking table licenseGroups - OK
Cheking table OWA - OK
Cheking table pictures - OK
Cheking table Preview - OK
Cheking table rootcontext - OK
Cheking table settings - OK
Cheking table stationery - OK
Cheking table lgdaCollect - OK
Cheking table lgdaOWA - OK
Cheking table settingsLegal - OK
Cheking table users - OK
--------------------------------
Database check completed.

I've sent our DB your way...

// Kalle

Jesper Frier · Posted: Mon Nov 09, 2009 8:21 am Post subject:

Repaired the database in Access 2007.

When running Sign.exe (version 7), you will now be able to view log file.

If the Access database often gets corrupted, please try not to virus scan it - or move your database to SQL Server or SQL Express. This SQL script will work on both SQL Server and Express.
_________________
</Jesper> | Manage Email Signatures from your Desktop | Test Email Signature in All In-boxes | Email Signature Showcase

kalpa · Posted: Thu Nov 12, 2009 7:19 am Post subject:

I've repaired the DB but the same users still have problems!?

I have tried to remove the users but their logfiles are still empty after they have been added and logged in a couple of times...

I'll try the SQL Express path, is there a smooth way to import the access data into SQL? Cut'n'paste in 22 tables seem a bit complicated...

// Kalle

Jesper Frier · Posted: Thu Nov 12, 2009 8:20 am Post subject:

Does not look like a database problem to me .
Before moving to SQL database, can you please confirm:

All users with '################' in the log file are in OU=SpecialFalgar?

Are you using Scandinavian characters naming this OU? (SpecialFälger)
_________________
</Jesper> | Manage Email Signatures from your Desktop | Test Email Signature in All In-boxes | Email Signature Showcase

kalpa · Posted: Thu Nov 12, 2009 8:28 am Post subject:

Did you mean the Blank signatures when you wrote "########"

How does the OU affect this? They have all been given individual settings that should overrule any group settings right?

Currently no groups are added to Cockpit, there were some groups before but I removed them while trying to found the source for this error.

Anyway -yes, they all belong to that OU...

// Kalle

Jesper Frier · Posted: Thu Nov 12, 2009 8:38 am Post subject:

Sign.exe is trying to pull user information from this specific OU regardless if you are using individual, group or same signature for all.

What is the exact OU name in your Active Directory? (SpecialFalgar or SpecialFälgar)
_________________
</Jesper> | Manage Email Signatures from your Desktop | Test Email Signature in All In-boxes | Email Signature Showcase

kalpa · Posted: Thu Nov 12, 2009 9:01 am Post subject:

It's internationalized so the correct name is SpecialFalgar...

// Kalle

Bjarne Mess · Posted: Thu Nov 12, 2009 9:38 am Post subject:

Pleae check if your profile name contains illigal characters like ä and ö. The profile name must not contain special characters at all. This is by Microsoft's recommendation.

I have seen similar errors when the profile name was "Outlook innställningar" or similar. Please check this.

Thanks,
Bjarne

kalpa · Posted: Thu Nov 19, 2009 8:48 am Post subject:

Yes i have "Illegal" charcters in the signature names. "Växelnummer" for instance...

BUT, if this was a true error shouldn't all signatures fail then? Not just some?

Regarding the suggestion to use SQL instead, is there an converter script to move all my data to SQL?

// Kalle

Jesper Frier · Posted: Thu Nov 19, 2009 3:15 pm Post subject:

We are not really getting to the bottom of this ... as there are questions unanswered ... Neutral

What is the exact OU name in your Active Directory?
(SpecialFalgar or SpecialFälgar)

Does the profile name (not the signature name) contain illegal characters like ä and ö?

If you believe an SQL database will solve the issue, create the database executing the script. Then have users run Sign.exe.
But if this was a database issue - all users (and all our clients) would be effected ... not only users in one OU ... Wink

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

kalpa · Posted: Thu Nov 19, 2009 4:01 pm Post subject:

Strange, I thought that I had answered that one already...

Anyway, the OU is called SpecialFalgar without an "ä".

Aha, you meant the loginnames... Nope, none of our users have loginnames with special characters.

I'm not sure that this is OU related, since only a few of them has faced this issue, our other OU:s has not migrated to this environment yet that's why they don't show up anywhere...yet...