I am trying to set up a development environment which allows me to test the
effects of changing the outlook security template in public folders. I have
an exchange 2003 sp2 server on Windows 2003 sp1. My clients are XP pro sp2
and outlook 2003 sp2. I installed the outlook security template in
accordance with
http://office.microsoft.com/en-us/or...402931033.aspx and left it as
default. I have a application which generates the "outlook is trying to
access your address book" warning in the production environment. I can't
replicate this warning (mail goes straight through with no warnings). This
happened even before I had any outlook security configured which seemed
strange as outlook should generate a warning by default. I don't know much
about exchange. Can anyone point me in the right direction.

No, Outlook 2003 won't necessarily generate a warning by default. It depends on the context of the application and the code. In particular, VBA and add-in code are trusted by default.

Did you apply the CheckAdminSettings registry value to your local machine?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Rod" wrote in message ...
I am trying to set up a development environment which allows me to test the
effects of changing the outlook security template in public folders. I have
an exchange 2003 sp2 server on Windows 2003 sp1. My clients are XP pro sp2
and outlook 2003 sp2. I installed the outlook security template in
accordance with
http://office.microsoft.com/en-us/or...402931033.aspx and left it as
default. I have a application which generates the "outlook is trying to
access your address book" warning in the production environment. I can't
replicate this warning (mail goes straight through with no warnings). This
happened even before I had any outlook security configured which seemed
strange as outlook should generate a warning by default. I don't know much
about exchange. Can anyone point me in the right direction.

Thanks for the reply.

Yes, the registry value is correct.

The application kicks off a warning in the production environment in 2
situations. One is the application calling the mapi dll to send a
message. The other is using outlook forms to send an email (one off
form I think). In the security template both these events are set to
prompt user however this doesn't occur.

ON the Help | About Microsoft Outlook dialog, you can see whether Outlook thinks the user or the public folder is controlling the security settings. What do you see there?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

wrote in message ups.com...
Thanks for the reply.

Yes, the registry value is correct.

The application kicks off a warning in the production environment in 2
situations. One is the application calling the mapi dll to send a
message. The other is using outlook forms to send an email (one off
form I think). In the security template both these events are set to
prompt user however this doesn't occur.

"Administrator controlled". If I log on as a user who is not in the OU
controlled by the GPO I see "default" and the warning messages still do not
trigger. I guess I will investigate why, for some reason, the application is
trusted on the dev network but not on the prod network. Thanks for your
help.

"Administrator-controlled" tells you that OUtlook has recognized the registry value and is handing off control to the public folder. The next step, then, would be to confirm that the user is represented by an item in the folder and that the item contains the correct settings.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Rod" wrote in message ...
"Administrator controlled". If I log on as a user who is not in the OU
controlled by the GPO I see "default" and the warning messages still do not
trigger. I guess I will investigate why, for some reason, the application is
trusted on the dev network but not on the prod network. Thanks for your
help.

I have two computers that both have the registry setting set exactly the
same, but one shows administrative and the other default. Same domain, user
level, etc on Small Business Server.

Does whether the account is in cached mode matter?

Does whether the forms cache is cleared matter?

Thanks for any assistance or insight.

"Sue Mosher [MVP-Outlook]" wrote:

"Administrator-controlled" tells you that OUtlook has recognized the registry value and is handing off control to the public folder. The next step, then, would be to confirm that the user is represented by an item in the folder and that the item contains the correct settings.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Rod" wrote in message ...
"Administrator controlled". If I log on as a user who is not in the OU
controlled by the GPO I see "default" and the warning messages still do not
trigger. I guess I will investigate why, for some reason, the application is
trusted on the dev network but not on the prod network. Thanks for your
help.

I have heard some odd reports on variations with cached mode, but have never tracked down the exact problem. The forms cache state should not matter at all.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"E. Palmer" wrote in message ...
I have two computers that both have the registry setting set exactly the
same, but one shows administrative and the other default. Same domain, user
level, etc on Small Business Server.

Does whether the account is in cached mode matter?

Does whether the forms cache is cleared matter?

Thanks for any assistance or insight.

"Sue Mosher [MVP-Outlook]" wrote:

"Administrator-controlled" tells you that OUtlook has recognized the registry value and is handing off control to the public folder. The next step, then, would be to confirm that the user is represented by an item in the folder and that the item contains the correct settings.

"Rod" wrote in message ...
"Administrator controlled". If I log on as a user who is not in the OU
controlled by the GPO I see "default" and the warning messages still do not
trigger. I guess I will investigate why, for some reason, the application is
trusted on the dev network but not on the prod network. Thanks for your
help.

Hi,

Oops, this was entirely my fault, I missed the last folder in ther reg key.
Thanks though.

"Sue Mosher [MVP-Outlook]" wrote:

I have heard some odd reports on variations with cached mode, but have never tracked down the exact problem. The forms cache state should not matter at all.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"E. Palmer" wrote in message ...
I have two computers that both have the registry setting set exactly the
same, but one shows administrative and the other default. Same domain, user
level, etc on Small Business Server.

Does whether the account is in cached mode matter?

Does whether the forms cache is cleared matter?

Thanks for any assistance or insight.

"Sue Mosher [MVP-Outlook]" wrote:

"Administrator-controlled" tells you that OUtlook has recognized the registry value and is handing off control to the public folder. The next step, then, would be to confirm that the user is represented by an item in the folder and that the item contains the correct settings.

"Rod" wrote in message ...
"Administrator controlled". If I log on as a user who is not in the OU
controlled by the GPO I see "default" and the warning messages still do not
trigger. I guess I will investigate why, for some reason, the application is
trusted on the dev network but not on the prod network. Thanks for your
help.