Move Public Folders from Exchange 2003 to 2007

[AFOINT]

I am decommisioning my Exchange 2003 clustered mailbox server this weekend.
I have already ran the "Move all Replicas" command from my Exchange 2003
server to my Exchange 2007 server. Public folder Instances on the 2003
server still contains 5 folders and 1 system folder (Schedule+ Free Busy
Information). I see 0x20 Outgoing message events from Exchange 2003 server.
On Exchange 2007 server, I am getting event ID 3085 replication errors "Error
1129 occurred while generating an outgoing replication message." for the
folders mentioned above still located in Public folder Instances on 2003.
How do I force these folders to finish replicating, I kicked off replication
4 days ago?
If they don't finish, can I remove the old PF in adsiedit with no harm so I
can remove the old Exchange 2003 infrastructure this weekend?
All users are moved to Exchange 2007 and are pointing to the new PF properly
on the database properties client settings.

[Mark Arnold [MVP]]

Keep everything up and running, make sure all users are replicated
accross and progressively remove the replicas from the PF as you see
them in sync. Then uninstall the Exchange server.

[AFOINT]

Not sure that your response makes sense. All users are moved to Exchange
2007, not replicated. I've attempted to remove the replicas from the PF
using the "Move all Replicas" option, but they aren't all moving over. What
do you mean by "Progressively remove the replicas from the PF as you see them
in sync.?"

[dok...@sub.nu]

Hello,

I've done just the same as you. "Move all replicas" from the Exchange
2003 ESM. I get some errors in the application log on the 2007 server,
like this:

Error 1129 occurred while generating an outgoing replication message.

Type: 0x80000004
Folder: (7-165A3D) IPM_SUBTREE\Infobox\Cabinet\Suppliers\Companyname

Database "Second Storage Group\Public Folder Database".

And in "Replication status" I see mixed status of "Both modified" and
"Local modified".

Don't know what to do.

[Andy David {MVP}]

Wait till Sp1?

[AFOINT]

Funny, SP1 for Exchange 2007 will certainly add features that many customers
are looking for, but it's not going to fix a problem with Exchange 2003 SP2,
and for that matter, Public folders period. I am amazed that there is no way
to force a removal of an old Public Folder Instance so you can remove a
Public Folder Database from an old server. I am planning on removing our
Exchange 2003 Mailbox Cluster tomorrow, Exchange is scheduled down for the
entire weekend for over 5,000 users so I can complete the move over to 2007,
I hope PF's don't get in the way.
If I have to, I will backup our PF's to a pst and just remove all PF's for
the entire domain and rebuild from the pst backup.

[artu...@gmail.com]

On Aug 3, 7:30 pm, AFOINT <AFO...@discussions.microsoft.com> wrote:
> Funny, SP1 for Exchange 2007 will certainly add features that many customers
> are looking for, but it's not going to fix a problem with Exchange 2003 SP2,
> and for that matter, Public folders period. I am amazed that there is no way
> to force a removal of an old Public Folder Instance so you can remove a
> Public Folder Database from an old server. I am planning on removing our
> Exchange 2003 Mailbox Cluster tomorrow, Exchange is scheduled down for the
> entire weekend for over 5,000 users so I can complete the move over to 2007,
> I hope PF's don't get in the way.
> If I have to, I will backup our PF's to a pst and just remove all PF's for
> the entire domain and rebuild from the pst backup.
>
> "Andy David {MVP}" wrote:
>

> > On Fri, 03 Aug 2007 16:56:42 -0700, dokt...@sub.nu wrote:
>
> > >Hello,
>
> > >I've done just the same as you. "Move all replicas" from the Exchange
> > >2003 ESM. I get some errors in the application log on the 2007 server,
> > >like this:
>
> > >Error 1129 occurred while generating an outgoing replication message.
>
> > > Type: 0x80000004
> > > Folder: (7-165A3D) IPM_SUBTREE\Infobox\Cabinet\Suppliers\Companyname
>
> > > Database "Second Storage Group\Public Folder Database".
>
> > >And in "Replication status" I see mixed status of "Both modified" and
> > >"Local modified".
>
> > >Don't know what to do.
>
> > Wait till Sp1?

Have you found the answer?

[a.re...@qdoscc.com]

> Have you found the answer?- Hide quoted text -
>
> - Show quoted text -

Has anyone found the answer to this yet as I am experiencing exactly
the same issue. The public folders on my 2003 exchange and the ones on
the 2007 exchange appear to be replicated but I cannot find a way to
seperate them and delete the old PF's. Any assistance greatly
appreciated...

[AFOINT]

Let's face the facts, there is no fix. Here is what you do as I have
succesfully removed Exchange 2003 from my environment:

Move all replicas from Exchange 2003 PF to Exchange 2007 PF
If some public folder instances won't move, backup your PF to a pst file
just in case and manually remove your old PF's via ADSIEDIT. This worked
well for me.
Make sure your new storage groups and mailbox databases are pointing at your
new public folder store. AFter that, just follow the steps to remove
Exchange 2003 as documented all over the web such as deleting routing group
connectors, old routing groups, setting up your new smtp send connector,
moving the public folder store to the Exchange 2007 Administrative Group,
removing/moving RUS.