/build/static/layout/Breadcrumb_cap_w.png

Outlook default font

Hi all,
i am working on a office 2003 package.
In order to change the default font for outlook messages we have exported some HKCU registries in the package.
After install of the package we checked that registries got installed correctly.
However as soon as we launch outlook the registries are getting deleted and hence font settings changes does not take place.

Any help is appreciated!

0 Comments   [ + ] Show comments

Answers (9)

Posted by: anonymous_9363 11 years ago
Red Belt
0
NB. Use the 'Edit' link to make alterations to your posts, rather than making a new post.. :)
Posted by: karshi 11 years ago
Purple Belt
0
Guys no luck with the above issue. M still stuck up with the same issue
Any ideas on how to standardize font for outlook through office 2003 package??
the registry keys to set the default font value resides in the location
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\MailSettings

But as soon as we launch our outlook shortcut for the first time these reg keys get deleted.
we checked for .PRF file for setiing default values but they have information related to configuratin(exchange server etc).
Posted by: anonymous_9363 11 years ago
Red Belt
0
I think all these things can be controlled via Group Policy, can't they?
Posted by: elgwhoppo 11 years ago
Senior Purple Belt
0
VBScab is right, almost all Office settings (extremely granular) can be controlled through a user group policy, I would look there first. Grab the office resource kit and load up the ADM to confirm.
Posted by: karshi 11 years ago
Purple Belt
0
Thanks for ur replies... i did checked with group policy...
However we need to implement it through our package...

we are unable to predict the root cause of the problem.
we aslso tried creating .PRF file thru profile wizard and loaded into ORK but no use.
Posted by: the_apostate 11 years ago
Senior Yellow Belt
0
Hi All,

Apparently even I seem to be having the same problem. After deploying the office package and on launching outlook.exe the following registry keys gets deleted

HKLM\software\microsoft\office\11.0\common\mailsettings
ComposeFontSimple
ReplyFontSimple
ReplyFontSimple

HKLM\software\microsoft\office\11.0\outlook\setup
ImportPRF

due to which the font settings in outlook reverts back to the default.I tried using the source files to install office and apparently this also seem to be behaving the similar way.

Please help!!
Posted by: MsiCreator 11 years ago
Senior Yellow Belt
0
Hi..Can u tried to create a shortcut pointing to vbs which includes launch of outlook.exe and write deleted registry.
Posted by: karshi 11 years ago
Purple Belt
0
Thanks for ur replies[:)]. Finally we found the solution.
we have seen that after deploying the office package and on launching outlook.exe the registry keys responsible to change the outlook default font were getting deleted and hence the font settings in outlook reverts back to the default.

The app was checking for a few reg keys and if these registry keys exist on build prior to launch of shortcut Microsoft Outlook then outlook does not remove font related registry keys from the build.
So we imported those keys through our transform and hence on launch the font set by us was retained.

Registry keys are:

HKEY_CURRENT_USER\Software\Microsoft\Exchange\Forms Registry\CacheSyncCount
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\LanguageResources\OutlookChangeInstallLanguage
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Setup\First-Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu2\Programs\Order
Posted by: the_apostate 11 years ago
Senior Yellow Belt
0
Thank You!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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