MS Outlook Signatures

[bbbrian09]

Good Afternoon!

I'm sure there are many threads out there about creating MS Outlook Signatures using VBscript, but that is not the exact nature of my post here. I have gone through and setup a script that creates 4 different signature variants in for our users - 1 Full, 1 Reply, 1 Individual and 1 Departmental. Where I am a little stuck at is determining how to use vbscript and IF statements to set the proper default signature based on variables.

Currently I have a registry entry applied to all users that set to New e-mail signature in Outlook to %username%, and sets the reply signature to %username%-reply. These files are listed in %appdata%\Microaodt\Signatures as %username%.rtf and %username%-reply.rtf. Also in that same folder is %username%-individual.rtf and %username%-departmental.rtf. Each of these signatures is created when a login script runs for the user upon login.

What i'm looking to do is find some way to set the appropriate default signature based on a variable, either a YES or NO from an entry in a CSV file, or a YES or NO from an active directory attribute. Either one would work. I've been trying to rack my brain on this one but can't quite figure anything out. Any help from scripting geniuses would be greatly appreciated!

**side note - I would like to keep the registry entry in tact, meaning that the NEW e-mail signature entry is always going to be dependent on the file %username%.rtf being in the %appdata%\Microsoft\Signatures folder.

 

[sxschech]

Could you do it the lazy way and based on which signature type to use copy it to the standard name?
If Full then copy Full.Sig to Standard.Sig
If Indiv then copy Indiv.Sig to Standard.Sig

Or is that already what you are doing and I'm misreading your post.

 

[bbbrian09]

I thought about doing it that way, but I actually got this figured out today. I decided to use group policy item level targeting when adding the registry entry for the NewSignature option. Basically there will be a YES or a NO value stored as an attribute in Active Directory and the item level targeting will apply one of three registry values based on the results of an LDAP query.

Marking this one as solved!