Errors with Distribution Group Wizard and link to Public Folder Ar

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I'm having a problem with setting up a Distribution Group with the Public
Folder. My objective is to create a number of Distribution Groups that will
archive the e-mail to them to a public folder. The DG and PF are both being
created, but the link between the two is not. My objective is to use the PF
as the store where a team will go to view general e-mail addresses that are
being sent (webmaster@xxxxxxxxxxxxx, for example).

I am using the Add Distribution Group Wizard (ADGW, Server
Management\Standard Management\Distribution Groups\Add a Distribution Group)
to add the DG. I am having no problems with setting up the DG Information,
Group Membership, or Group Manager pages. When I come to the Group Options
page, I am leaving both 'Create a public folder to archive e-mail messages
sent to this group' and 'Enable this group to receive e-mail messages from
users outside of your network' check. I get the confirmation screen and
everything looks right. When the wizard goes into creation, the progress bar
runs all the way to the end rapidly and then, after a loooong wait, I get the
message:

'The wizard could not successfully configure this group. The following
could not be completed: - The Exchange public folder could not be created.
Do you want to keep this group?'

If I answer yes, the both the DG >>and the Public Folder<< (despite the
error message) get created, and the DG works fine (i.e. User members receive
e-mails posted to that DG), but the PF does not receive a copy of the
message. It appears that the creation of the link between the two is what
fails.

We are running SBS 2003 with Exchange 2003 running in Native mode. I know
that the above function worked on setup, as the default Distribution group
based on the <companyname> that is created during install exists and posts
successfully to the associated Public Folder. When I look at the properties
for this DG, the PF reference is listed as a member, but when I go to add my
other PFs to their associated DG, I do not get a Microsoft Exchange System
Objects component listed under the AD (which what is listed for my
<companyname> DG member.

I believe that the problems boils down to the following: the MS Exchange
System Objects are either not listed with the AD, or I don't know where to
find them. I have both browsed and searched the AD trying to locate this
entry with no success. Is there anyone that has faced and resolved this
issue that can point me in the right direction?

Thanks,

Andre


.



Relevant Pages

  • Re: Message Restrictions not Working - Why Not??
    ... If you want to restrict who can send to the distribution group, ... In the properties of the distribution list - Exchange General tab - ... perhaps as a member of a group that is a member of the ... mailbox as a security group, ...
    (microsoft.public.exchange.admin)
  • New Distribution Groups with Public Folder Archive - Error
    ... I'm having a problem with setting up a Distribution Group with the Public ... archive the e-mail to them to a public folder. ... We are running SBS 2003 with Exchange 2003 running in Native mode. ... DG member. ...
    (microsoft.public.exchange.setup)
  • Re: Msg to distribution group stuck in E2k3
    ... I tried to setup a distribution group in Exchange 2003. ... I added other groups as member each containing ... In Outlook I can check the recipient I entered to the "To" field. ...
    (microsoft.public.exchange.admin)
  • Reply as a distribution group
    ... my environment is Outlook 2003 and Exchange 2000 server. ... and a distribution group: group@xxxxxxxxxx ... user is a member of the group ...
    (microsoft.public.outlook.installation)
  • Re: Public Folder not receiving external emails from Distribution Grou
    ... I have an single Exchange 2k3 SP2 server. ... I have a Distribution Group. ... The Public Folder was added under ... Can anyone off guidance on why this is happening? ...
    (microsoft.public.exchange.admin)