/build/static/layout/Breadcrumb_cap_w.png

Deploying Microsoft Outlook Email Signatures

I need to setup some Email signature files for every user who logs in

The locaion of those files in outlook are in Tools-->Options-->Mail Format-->Stationery and Fonts-->Email Signature.

We tried Active Setup in previous package but we decided to get rid of it as it is causing lot of issues in our environment.

Is there any other way how i can make it work for all users..Please pitch in any ideas, Your response is highly appreciated.

Thanks,

Raj.


0 Comments   [ + ] Show comments

Answers (10)

Posted by: erik.bradbury 11 years ago
White Belt
0

In our environment we used scripting to call a batch file that put new signature files into %appdata%\micrsoft\signatures.

First I setup Task one to Verify that the directory $(KACE_DEPENDENCY_DIR) exists

 Then On Success Launch $(KACE_DEPENDENCY_DIR)\NewSig.bat with params .

(i had a bit of help from a support tech with the setup of the kscript)

NewSig.bat

this places the signature file into %APPDATA%\Microsoft\Signatures, the .htm file. The other folder that is copied contains a picture,  2 .XML documents and a themedata.thmx file all files releated to the formatting of the signature.

Posted by: aogilmor 14 years ago
9th Degree Black Belt
0
Raj, what ver are you packaging?
I think in 2007 or 10 you can do this with the OCT, just edit the Microsoft Outlook user settings tab
Posted by: jagannadhraj 14 years ago
Orange Belt
0
My package is Signature2009. All i have in that package is just these two email signature files.

Can i do this with a vb script or something?
Posted by: anonymous_9363 14 years ago
Red Belt
0
it is causing lot of issues in our environment. Like what?!? AS is in all probability the most widely-used mechanism for propogating CU settings which aren't/can't be triggered by a Windows Installer entry-point.
Posted by: jagannadhraj 14 years ago
Orange Belt
0
We had a package in our environment with AS. But it had huge problems, So they requested for repackage with out AS.
Any ideas how can we achieve this without AS please?
Posted by: anonymous_9363 14 years ago
Red Belt
0
*ONE* package caused you problems so you want to abandon AS! Priceless. Have you watched IE being configured on a clean machine? How does that work? Can you guess?

If you want to do it without AS, I guess the log-in script is the next most obvious place but that will involve scripting and, to be frank - and please don't take offence - if you're put off AS because of one problem, I wouldn't be very confident about your ability to build bullet-proof scripts.
Posted by: jagannadhraj 14 years ago
Orange Belt
0
Thanks for your help. But just to clarify it wasn't my decision to abandon AS. It was taken by someone else all i can do is follow them not in a position to go against them.
No offense taken...You might have not reached to this position with out starting from somewhere so please stop doubting about other's ability that would be the most dumbest thing to do. Thanks
Posted by: aogilmor 14 years ago
9th Degree Black Belt
0
if you don't have an advertised entry point for your CU settings email sigs (as in making it part of the outlook package) then as Ian (VB) says then you gotta go with AS, logon script or (just a guess) GPO?
Posted by: anonymous_9363 14 years ago
Red Belt
0
it wasn't my decision to abandon ASWell, it's time for Old Faithful to come out again...the Packager's Baseball Bat or, as I now sometimes refer to it as, The Persuader.
Posted by: aogilmor 14 years ago
9th Degree Black Belt
0
surely you're speaking metaphorically vb?
packagers are usually not the baseball bat (or in your case Cricket bat) wielding type
[:D]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ