Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 597
  • Last Modified:

Public folder replication from Exchange 2003 to 2007 CCR

I know there are millions of articles on this, and i think I've read them all. I mainly just need human advise on this as I'm kind of confused. I have one PF database on 2003, and one PF database on the 2007 CCR. I have enabled replication between the two and gave it a week to replicate. I have repointed the default public database stores for the mailbox databases to the Exchange 2007 CCR. I dont know what to do for the next step. Can i just delete the 2003 database now?

The part I'm confused about is the replication tab. It says "Replicate content to these public stores". So if I'm on the 2007 server, I would assume I delete the 2003 replica. But if I'm on the 2003 server, now the replication tab says to replicate these folders to the 2007 server. I just want to stop all replication now and delete the 2003 PF.
0
fina27
Asked:
fina27
  • 2
  • 2
1 Solution
 
aslamsurveCommented:
Have you peformed Move All Replicas from the Exchange System Manager?
Need to confirm if all the public folders along with the contents have been replicated to the Public Folder Database on the CCR (Exchange 2007) Server using the Exchange Management Shell to get public folder statistics..Get-PublicFolderStatistics -Server "Name of Clustered Mailbox Server" | Format-List>C:\pfstatistics.txt on the active node of CCR....which give the complete list of the public folders..

Check the Public Folder Instances on the Exchange 2003 Public Folder Store in Exchange System Manger & it should not have public folder stuck over here which means the public folders along with contents have been replicated properly to Exchange 2007 server
.....Let me know the findings.....since then further we have to t-shoot the issue in a direction which can be simplified....

0
 
fina27Author Commented:
No i haven't performed Move All Replicas from the ESM. What does that actually do?

I have confirmed that all PFs have been replicated, and the item count is the same on both servers. It's not very big, only a 300MB PF database.

If i go to Public Folder Instances in the ESM.... all the folders are still there.
0
 
fina27Author Commented:
Ok I just found this helpful article.

http://msmvps.com/blogs/andersonpatricio/archive/2007/10/30/moving-all-replicas-from-an-exchange-server-2003-to-an-exchange-server-2007.aspx

Now just two questions.

1. Should I add the Exchange 2007 server in the replication tab for all the folders in the PF Instances window? Even the OAB versions, Schedule+ free/busy, and Schema-root?

2. Is "move all replicas" the same thing as me going into each folder and removing the 2003 replica from the replication tab?

Thanks for the help
0
 
aslamsurveCommented:
Yes....Right click the public folders in ESM & click View System Folders
Select the Offline Address Book & under it right click the OAB versions by adding the Exchange 2007
public folder database also add the Schedule+ Free busy folders to the Exchange 2007 public folder database.

Is "move all replicas" the same thing as me going into each folder and removing the 2003 replica from the replication tab?
Yes...Just right click each public folder & increase the replication message priority to to Urgent  & public folder interval to Always Run to urgent then peform the Move All Replicas..

To confirm if the users are are connecting to public folders from Exchange 2007 server......dis-mount the public store on the Exchange 2003 server & see if the users are connecting to public folders on Exchange 2007 server.


0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now