Outlook Security Settings issue

[mooch911]

Hello,

I am trying to implement a default outlook security settings template
for Office 2003 to allow .url and .lnk files through. I have tested
my template in our test environment and it works perfectly, but it
doesn't work in our production environment. The only difference
between our test and production environments is that our test
environment doesn't have group policies in place to handle the Office
2000 installs in our production environment. Does anyone know if
office 2000 adm settings can affect the security settings for office
2003?

Thanks.

John Luong

 

[Sue Mosher [MVP-Outlook]]

I don't know of any overlap between Outlook 2000 and 2003 settings, but you'd have to compare the .adm files to know for sure.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[mooch911]

Is there anything else that you can think of that could possibly cause
Outlook 2003 to not even look at the Outlook Security settings? Our
users that have Outlook 2000 in production are still getting the
Outlook Security settings.


Thanks.

 

[Sue Mosher [MVP-Outlook]]

This is very obscure, but another user provided it as a solution when they had a similar problem:

In Outlook 2003 SP2 there was a change, that Outlook always, if it
tries to access a public folder first contacts its home server (stored
in the Outlook profile). The home server gives back an EcWrongServer
and the referral to the server where the Public Folder is located.
In Exchange SP2 there was a change that if Exchange had to send an
EcWrongServer more than 5 times in 10 seconds it will respond with a
EcServerPaused what will end up in a MAPI error MAPI_E_FAILONPROVIDER.
This error message causes, that the Outlook client is not able to find
the Outlook security form and as a result it will show the security
warning.

The issue only occurs, if the home server of the mailbox/user used is
not the one, that also holds the Outlook security settings public
folder, what is true in my environment.

To work around this issue, there is a possibility to force Outlook not
to contact the home server first when searching for a public
folder.What we need to do is, we need to remove or rename the registry
key, where the home server is stored in the Outlook profile.
Please try to rename the following registry key on the profile of the
user you use to send the emails:

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging
Subsystem\Profiles\<profile>\13dbb0c8aa05101a9bb000aa002fc45a]

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers