Public folder replication between Exchange 2007 and Exchange 2010

[Peter Lawton]

I've just set up a new Exchange 2010 server to work with our existing

Exchange 2007 servers and I'm having trouble getting public folders to

replicate, although emails are flowing from 2010 to 2007 in both

directions OK

I've added the new 2010 exchange server to the replica list of all the

public folders on the 2007 servers but they never show up on the 2010 server

Similarly I've created a new public folder on the Exchange 2010 server

and added the 2007 servers to the replica list but the folder never

replicates

The database replication timing is set to "Always" on all servers

Anyone any idea if there's some step I've missed to get public folders

replicating?

Many thanks

Peter Lawton

 

[Ed Crowley [MVP]]

How long have you waited?

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Peter Lawton" <Dummy@FakeDomain> wrote in message

news:eZ6hVV3YKHA.4148@TK2MSFTNGP04.phx.gbl...
> I've just set up a new Exchange 2010 server to work with our existing
> Exchange 2007 servers and I'm having trouble getting public folders to
> replicate, although emails are flowing from 2010 to 2007 in both
> directions OK

> I've added the new 2010 exchange server to the replica list of all the
> public folders on the 2007 servers but they never show up on the 2010
> server

> Similarly I've created a new public folder on the Exchange 2010 server and
> added the 2007 servers to the replica list but the folder never replicates

> The database replication timing is set to "Always" on all servers

> Anyone any idea if there's some step I've missed to get public folders
> replicating?

> Many thanks

> Peter Lawton

 

[Peter Lawton]

Re: Public folder replication between Exchange 2007 and Exchange2010

Ed Crowley [MVP] wrote:
> How long have you waited?

4 days

 

[Ed Crowley [MVP]]

Well, that's too long. The general diagnostic process for public folder

replication includes the following.

1. Verifying that your server has the public folder hierarchy by using the

Get-PublicFolderStatistics cmdlet.

2. Verifying that you have created replicas on the new server.

3. Verifying that you have messaging connectivity between the two servers.

4. Watching the SMTP queues to see if public folder content messages are

flowing between the two servers.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Peter Lawton" <Dummy@FakeDomain> wrote in message

news:ez$BLWpZKHA.2188@TK2MSFTNGP04.phx.gbl...
> Ed Crowley [MVP] wrote:
> > How long have you waited?

> 4 days

 

[Peter Lawton]

Re: Public folder replication between Exchange 2007 and Exchange2010

Ed Crowley [MVP] wrote:
> Well, that's too long. The general diagnostic process for public folder
> replication includes the following.

> 1. Verifying that your server has the public folder hierarchy by using
> the Get-PublicFolderStatistics cmdlet.
> 2. Verifying that you have created replicas on the new server.
> 3. Verifying that you have messaging connectivity between the two servers.
> 4. Watching the SMTP queues to see if public folder content messages
> are flowing between the two servers.

1. doing get-publicfolderstatistics on the Exchange 2010 server just

returns the single public folder created on that server, non of the ones

on the Exchange 2007 server that should be replicating.

Similarly running it on the Exchange 2007 server only shows the public

folders there, not the one on the 2010 server

2. I've set several public folders to have replicas on both servers,

similarly the single folder on the Exchange 2010 server. What do you

mean by "created replicas", I don't have to manually create the folders

that are on the 2007 server on the 2010 server do I?

3. email is flowing OK between mailboxes on both servers, just seems to

be public folders that aren't replicating

4. No messages queued at all on either server

It's very strange they don't seem to be aware of each other's public

folders

Peter Lawton

 

[Peter Lawton]

Re: Public folder replication between Exchange 2007 and Exchange2010

Peter Lawton wrote:
> Ed Crowley [MVP] wrote:
> > Well, that's too long. The general diagnostic process for public
> > folder replication includes the following.
>

>> 1. Verifying that your server has the public folder hierarchy by
> > using the Get-PublicFolderStatistics cmdlet.
> > 2. Verifying that you have created replicas on the new server.
> > 3. Verifying that you have messaging connectivity between the two
> > servers.
> > 4. Watching the SMTP queues to see if public folder content messages
> > are flowing between the two servers.

> 1. doing get-publicfolderstatistics on the Exchange 2010 server just
> returns the single public folder created on that server, non of the ones
> on the Exchange 2007 server that should be replicating.
> Similarly running it on the Exchange 2007 server only shows the public
> folders there, not the one on the 2010 server

> 2. I've set several public folders to have replicas on both servers,
> similarly the single folder on the Exchange 2010 server. What do you
> mean by "created replicas", I don't have to manually create the folders
> that are on the 2007 server on the 2010 server do I?

> 3. email is flowing OK between mailboxes on both servers, just seems to
> be public folders that aren't replicating

> 4. No messages queued at all on either server

> It's very strange they don't seem to be aware of each other's public
> folders

> Peter Lawton

A bit more information now. Users with mailboxes on both Exchange 2010

and Exchange 2007 servers can send email to mail enabled public folders

on Exchange 2007, but no users either on Exchange 2007 or Exchange 2010

can send email to mail enabled public folders on Exchange 2010.

There's no problem sending email both directions between mailboxes on

Exchange 2010 and Exchange 2007 servers though

This may well explain the issue but I can't see why it's happening

Peter Lawton

 

[Ed Crowley [MVP]]

1. Sorry, I meant Get-PublicFolder -Recurse. If you see the hierarchy

then it's replicating. If you don't see the hierarchy, stop now. Run this

on the Exchange 2007 server first to see what I mean by seeing a hierarchy.

If you don't see the hierarchy, you'll have to diagnose why that is.

2. Replicas won't magically appear in the Exchange 2010 public store except

for those system folders that automatically get created. You will need to

go through your public folders and add the 2010 server's public store as a

replica. Exchange 2007 provides you with a script to help with that. Open

the EMS, change your working directory to C:\Program

Files\Microsoft\Exchange Server\Scripts (or wherever you installed Exchange)

and enter this command:

> .\AddReplicaToPFRecursive TopPublicFolder ServerToAdd

Exchange_2020_Server_Name

Exercise discretion before doing this because, depending on how large your

public folder store is, it may kick off a large number of messages.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Peter Lawton" <Dummy@FakeDomain> wrote in message

news:%23EQ1ZO2ZKHA.2184@TK2MSFTNGP04.phx.gbl...
> Ed Crowley [MVP] wrote:
> > Well, that's too long. The general diagnostic process for public folder
> > replication includes the following.
>

>> 1. Verifying that your server has the public folder hierarchy by using
> > the Get-PublicFolderStatistics cmdlet.
> > 2. Verifying that you have created replicas on the new server.
> > 3. Verifying that you have messaging connectivity between the two
> > servers.
> > 4. Watching the SMTP queues to see if public folder content messages are
> > flowing between the two servers.

> 1. doing get-publicfolderstatistics on the Exchange 2010 server just
> returns the single public folder created on that server, non of the ones
> on the Exchange 2007 server that should be replicating.
> Similarly running it on the Exchange 2007 server only shows the public
> folders there, not the one on the 2010 server

> 2. I've set several public folders to have replicas on both servers,
> similarly the single folder on the Exchange 2010 server. What do you mean
> by "created replicas", I don't have to manually create the folders that
> are on the 2007 server on the 2010 server do I?

> 3. email is flowing OK between mailboxes on both servers, just seems to be
> public folders that aren't replicating

> 4. No messages queued at all on either server

> It's very strange they don't seem to be aware of each other's public
> folders

> Peter Lawton

 

[Peter Lawton]

Re: Public folder replication between Exchange 2007 and Exchange2010

Ed Crowley [MVP] wrote:
> 1. Sorry, I meant Get-PublicFolder -Recurse. If you see the
> hierarchy then it's replicating. If you don't see the hierarchy, stop
> now. Run this on the Exchange 2007 server first to see what I mean by
> seeing a hierarchy. If you don't see the hierarchy, you'll have to
> diagnose why that is.

> 2. Replicas won't magically appear in the Exchange 2010 public store
> except for those system folders that automatically get created. You
> will need to go through your public folders and add the 2010 server's
> public store as a replica. Exchange 2007 provides you with a script to
> help with that. Open the EMS, change your working directory to
> C:\Program Files\Microsoft\Exchange Server\Scripts (or wherever you
> installed Exchange) and enter this command:

> ..\AddReplicaToPFRecursive TopPublicFolder ServerToAdd
> Exchange_2020_Server_Name

> Exercise discretion before doing this because, depending on how large
> your public folder store is, it may kick off a large number of messages.

Right, I'm with you now

When I run Get-PublicFolder -Recurse on an Exchange 2007 server I see

all of the dozens of my public folders, when I run it on one of the two

new Exchange 2010 servers I just see the following:-

Name Parent Path

---- ---------
IPM_SUBTREE

Test-Folder

On the second of the two Exchange 2010 servers I see:-

Name Parent Path

---- ---------
IPM_SUBTREE

Nothing except the IPM_SUBTREE and the single test folder I created on

one server and the other one doesn't even show the test folder

Looks like the 2010 servers are each looking at their own private public

folder tree somehow ?

Peter Lawton

 

[Ed Crowley [MVP]]

They don't have a replica of the hierarchy. That tells you replication is

broken.

Open the queue viewer to show the queues on all your hub transport servers

in the same AD sites as your Exchange servers, and then try issuing:

Update-PublicFolderHierarchy -Server Exch_2007_PF_Server

See if anything is held up in the queues or if the replication occurs.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Peter Lawton" <Dummy@FakeDomain> wrote in message

news:eg3OjTCaKHA.2164@TK2MSFTNGP02.phx.gbl...
> Ed Crowley [MVP] wrote:
> > 1. Sorry, I meant Get-PublicFolder -Recurse. If you see the hierarchy
> > then it's replicating. If you don't see the hierarchy, stop now. Run
> > this on the Exchange 2007 server first to see what I mean by seeing a
> > hierarchy. If you don't see the hierarchy, you'll have to diagnose why
> > that is.
>

>> 2. Replicas won't magically appear in the Exchange 2010 public store
> > except for those system folders that automatically get created. You will
> > need to go through your public folders and add the 2010 server's public
> > store as a replica. Exchange 2007 provides you with a script to help
> > with that. Open the EMS, change your working directory to C:\Program
> > Files\Microsoft\Exchange Server\Scripts (or wherever you installed
> > Exchange) and enter this command:
>

>> ..\AddReplicaToPFRecursive TopPublicFolder ServerToAdd
> > Exchange_2020_Server_Name
>

>> Exercise discretion before doing this because, depending on how large
> > your public folder store is, it may kick off a large number of messages.

> Right, I'm with you now

> When I run Get-PublicFolder -Recurse on an Exchange 2007 server I see
> all of the dozens of my public folders, when I run it on one of the two
> new Exchange 2010 servers I just see the following:-

> Name Parent Path
> ---- ---------> IPM_SUBTREE
> Test-Folder

> On the second of the two Exchange 2010 servers I see:-

> Name Parent Path
> ---- ---------> IPM_SUBTREE

> Nothing except the IPM_SUBTREE and the single test folder I created on one
> server and the other one doesn't even show the test folder

> Looks like the 2010 servers are each looking at their own private public
> folder tree somehow ?

> Peter Lawton

 

[Peter Lawton]

Re: Public folder replication between Exchange 2007 and Exchange2010

Ed Crowley [MVP] wrote:
> They don't have a replica of the hierarchy. That tells you replication
> is broken.

> Open the queue viewer to show the queues on all your hub transport
> servers in the same AD sites as your Exchange servers, and then try
> issuing:

> Update-PublicFolderHierarchy -Server Exch_2007_PF_Server

> See if anything is held up in the queues or if the replication occurs.

Hi, great - that seems to have got it all working

I issued that command on all my PF servers and it seems to have un-stuck

everything

Many thanks for all your help !

Peter Lawton

 

[Ed Crowley [MVP]]

Happy to have helped!

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Peter Lawton" <Dummy@FakeDomain> wrote in message

news:uqBqa6QaKHA.4924@TK2MSFTNGP05.phx.gbl...
> Ed Crowley [MVP] wrote:
> > They don't have a replica of the hierarchy. That tells you replication
> > is broken.
>

>> Open the queue viewer to show the queues on all your hub transport
> > servers in the same AD sites as your Exchange servers, and then try
> > issuing:
>

>> Update-PublicFolderHierarchy -Server Exch_2007_PF_Server
>

>> See if anything is held up in the queues or if the replication occurs.

> Hi, great - that seems to have got it all working

> I issued that command on all my PF servers and it seems to have un-stuck
> everything

> Many thanks for all your help !

> Peter Lawton

 

[ZackSilver]

We had a similar issue, but didn't have to jump through all the hoops indicated above. You just need to go into the Public Folder Management Console in the EMC on your Exchange 2007 box and change the replication schedule to something other than "always run". I changed ours to "Run every hour" and the next day when I came in, all of our Public folders were visible on the 2010 box. You may have to uncheck "Use public folder database replication schedule" to be able to make this change. Good luck!