Outlook 2002 ignores "Outlook 10 Security Settings" on Exchange 2003 Server

[Bert Köhler]

Hello group,

we are in the process of migrating from Exchange 5.5 to Exchange 2003. While
custom forms with vbscript code accessing the address book worked well in
the old environment (OL2002, forms from the global forms library, settings
in public folder on MSX55), this won't work after the migration (OL2002,
forms from the global forms library, settings in public folder on MSX2003).

Outlook 2002 either ignores the settings or cannot access the public folder
when starting?? (But: you can navigate to the folder and read the objects
after starting). After some trying, I found a workaround that I really don't
want to use: give everybody owner permissions on that public folder! With
this setting, the forms work without the security warning, but that means
everybody can now fiddle with the folder...

We will not migrate to OL2003 in the near future, even if Sue Mosher states
that OL2003 will not show the warning when the form comes from "trusted
sources".

Are there any hints where to look for additional settings?

Any help is appreciated

Bert.

 

[Sue Mosher [MVP]]

There should be no additional settings. What access error are you getting?
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Bert Köhler]

Hi Sue,

unfortunately, there is no error message. OL2002 just falls back to the
standard behaviour and displays the warning message(s) when opening the
forms. I was only guessing the reasons why OL behaves like this when saying
that OL does not get access to the folder or ignores the settings on
purpose...
The only users that do not get the warning message are the owners of the
folder. But giving owner permissions to all users is not appropriate, I
think.
I also tried to use the older folder name: "Outlook Security Settings" with
the corresponding registry setting CheckAdminSettings=1, but the result was
the same.

How (what protocol, what public folder server, MAPI version?) does OL2002
access the public folder on an Exchange 2003 Server when starting? What
should we look for when doing a network trace? Can we increase some
diagnostic level? Can I do an OL startup trace?

Bert.

 

[Bert Köhler]

Hello Sue, hello Group,

this problem seems to be a very special one...

I did not expect to get ready-to-run solution for this problem, but I did
hope for some hints of where to look. So, if anyone had similar problems
(even without solutions), don't hesitate to comment this thread.

I still cannot believe that we are the first to run in to this problem...

Bert.

 

[Michael Bednarek]

Hello Sue, hello Group,

this problem seems to be a very special one...

I did not expect to get ready-to-run solution for this problem, but I did
hope for some hints of where to look. So, if anyone had similar problems
(even without solutions), don't hesitate to comment this thread.

I still cannot believe that we are the first to run in to this problem...

Bert.

You may be the first, but not the only one: same here, except we use
Outlook 9 (2000) on a NT5.2 (2003) server. So the issue seems to be
some lockdown on Server 2003 (NT5.2). (And yes, CheckAdminSettings is
1).

Michael Bednarek, TGM, Brisbane

 

[Rafael]

Bert you're not alone. I was about to post the same question when luckily I
took the time to read through the postings and found this posting.

I don't know what else to try here either as Outlook XP keeps prompting me
to allow the code to run.

I have Exchange 2003 Standard running on Windows Server 2003 Standard with
All my users running Outlook XP.

Thanks,

Rafael

 

[Bert Köhler]

Hello Michael, hello Rafael,

thank you for your comments. I will try to open a support call next week.
There really seems to be a bug in Exchange 2003 with handling public
folders.

 

[Sue Mosher [MVP]]

Does this apply:

* You are running in Cached Exchange mode and

* either the Outlook 10 Security Settings folder is not in Public
Folders\Favorites

* or it is in PF Favorites, but you do not have PF Favorites set to
synchronize automatically

If so, then the article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;833006 applies.

 

[Rafael]

Not the case here Sue. I'm using Outlook XP.

Rafael

 

[Bert Köhler]

Hi Sue,

as Rafael stated, we are also using OLXP (no Cached Mode available) in
conjunction with Exchange 2003.

MS Support suggested to rename the original PF, let this replicate through
the organisation, create a new PF, republish the form and copy the settings
back into the newly created folder. I did this today, but it had no effect.
Just as before, only owners will not experience the warnings...

Bert.

 

[Michael Bednarek]

Does this apply:

* You are running in Cached Exchange mode and

* either the Outlook 10 Security Settings folder is not in Public
Folders\Favorites

* or it is in PF Favorites, but you do not have PF Favorites set to
synchronize automatically

If so, then the article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;833006 applies.

None of the above. It's Exchange 5.5, Outlook 9, Windows NT5.2.

The commonality in the reported problems (Bert, Rafael, myself) seems to
be NT5.2 (Server 2003).

 

[Bert Köhler]

Hello Michael,

Did you mean you installed an Exchange Server 5.5 on a Windows Server 2003?
Or:
Are you migrating from an Exchange Server 5.5 on NT4/5 to an Exchange Server
2003 on Windows Server 2003?

Bert.

 

[Michael Bednarek]

Hello Michael,

Did you mean you installed an Exchange Server 5.5 on a Windows Server 2003?
Or:
Are you migrating from an Exchange Server 5.5 on NT4/5 to an Exchange Server
2003 on Windows Server 2003?

Neither. I joined a 2003 server to a 2000 domain. Our Exchange 5.5 runs
on a 2000 server. (I believe only Exchange 2003 can run on Server 2003.)

The new 2003 server runs Veritas BE 8.5 for backups (I know, it's not
supported). BE needs an Outlook profile to send job notifications. So I
installed Outlook 9 (2000). I have the public folder Outlook Security
Settings properly configured. In fact, BE also runs on a 2000 server in
the same network, and its job notifications are e-mailed without
problem.

The 2003 server does have the registry entry CheckAdminSettings (DWORD)
in HKCU\Software\Policies\Microsoft\Security set to 1, but when BE sends
e-mail, the standard warnings about a program trying to send e-mail
appear. I tried to overcome that with ClickYes
<http://www.express-soft.com/mailmate/clickyes.html>, but BE 8.5 still
doesn't like it and every jobs gets stuck on 99% (there's a document in
Veritas's KB about about it).

I've now given up on MAPI job notifications and reverted to SMTP Event
notification -not nearly as versatile, but the only thing which works.

In my mind, the fault really is with Veritas: why they don't provide
SMTP job notifications completely escapes me. However, why Outlook 9
under Server 2003 doesn't observe the settings of CheckAdminSettings and
the content of Outlook Security Settings is also a problem.

On re-reading your original post, this may well be a different problem
to yours.

 

[Sue Mosher [MVP]]

My recollection is that running Outlook on an Exchange 2003 server is an
unsupported configuration. That could be part of the problem.

And I agree that the fault is with Veritas' application.

 

[Bert Köhler]

Update of MS Support activities:

The MS Outlook support guy said: "On the client side, we tried all we could
try. I will pass this call to the server support group."
The server support guy will now escalate "our" call as an attachment to
another (similar) call to be escalated. Now it's the developers' turn...

Bert.

 

[Sue Mosher [MVP]]

If you don't mind sharing the incident number we can pass that along to some
other folks as well.

 

[Bert Köhler]

Hello Sue,
since we do not have a solution yet, I do not think it useful to publish
such information now. After having fixed our problem, I will publish the
solution. OK?

If you don't mind sharing the incident number we can pass that along to some
other folks as well.

<snip>

 

[Sue Mosher [MVP]]

Up to you. I wanted the incident number to share with contacts at Microsoft
who might be able to give it some extra attention.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Michael Bednarek]

Hello Sue,
since we do not have a solution yet, I do not think it useful to publish
such information now. After having fixed our problem, I will publish the
solution. OK?

I'm eagerly looking forward to it.