> I'm baffled. There is nothing in the security settings form that would
> require a password, so I don't know where that dialog is coming from. If it
[quoted text clipped - 53 lines]
> > > > > > users. You should either delete the setting or save it
> > > > > > again, and type the correct password."
The registry setting to adjust the attachment behavior certainly is
supported in an Exchange scenario and is a perfectly legitimate way of
managing that feature. The security settings form is most needed when you
need to manage the behavior of the "object model guard."
Mailbox? What mailbox are we talking about here? The folder needs to be a
public folder, not a mailbox folder.

Signature
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> I've done that too! I used the reg hack to enable certain extensions on a
> per-client basis - this isn't exactly a supported fix from Microsoft in an
> Exchange scenario, though. The only mitigating factor I can think of is that
> the Exchange Alias for the Mailbox is Administrator, while the actual
> username "Administrator" has been changed to something far less obvious.
> Could this have any bearing?
> > I'm baffled. There is nothing in the security settings form that would
> > require a password, so I don't know where that dialog is coming from. If
> it
> > were my installation, I'd probably delete the folder and start over.
> > > Hi Sue,
> > >
[quoted text clipped - 55 lines]
> > > > > > > users. You should either delete the setting or save it
> > > > > > > again, and type the correct password."
BradB - 14 Jan 2004 23:02 GMT
Sorry, I didn't write that very well. The Administrator Mailbox's alias is
Administrator, while the Active Directory username is something completely
different - SID is still the same though.
All of this is being done through the Administrator Mailbox in Outlook, and
yes, the form is published to the Public Folder exactly the way the
Microsoft Documentation describes. The only other factor is that the
Exchange Server we are using is part of Small Business Server 2003 - this
wouldn't be affecting it in any way?
Brad
> The registry setting to adjust the attachment behavior certainly is
> supported in an Exchange scenario and is a perfectly legitimate way of
[quoted text clipped - 82 lines]
> > > > > > > > users. You should either delete the setting or save it
> > > > > > > > again, and type the correct password."
TonyT - 14 Jan 2004 23:24 GMT
Hi Sue & Brad
Even though I posted this in the first place I have not
had a chance to get back and reply although I have been
following the postings. Brad has done everything that I
have pretty well to the letter and I am in the same
situation. Also like Brad I am using SBS 2003. This
problem occurs on 2 of my customer systems again using
SBS 2003
Thanks for the suggestions - I feel this may run for a
while
>-----Original Message-----
>Sorry, I didn't write that very well. The Administrator Mailbox's alias is
[quoted text clipped - 102 lines]
>
>.
Sue Mosher [MVP] - 15 Jan 2004 13:35 GMT
The version of Exchange shouldn't matter. One thing that might be useful to
try would be to give a different user Owner permission on the folder, set up
an Outlook profile for that mailbox, and start Outlook with that profile to
try to set up some security settings items.

Signature
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> Sorry, I didn't write that very well. The Administrator Mailbox's alias is
> Administrator, while the Active Directory username is something completely
[quoted text clipped - 15 lines]
> > Mailbox? What mailbox are we talking about here? The folder needs to be a
> > public folder, not a mailbox folder.
> > > I've done that too! I used the reg hack to enable certain extensions on
> a
[quoted text clipped - 80 lines]
> > > > > > > > > users. You should either delete the setting or save it
> > > > > > > > > again, and type the correct password."