Exchange 2003 is not replicating public folders
We have an existing Exchange Server 2003 (EXCHANGE2K3) running on Windows 2003, fully patched OS and Exchange. We've set up a new exchange server (EXCHANGE01) and will be migrating all mailboxes and public folders to the new server.
The first thing we're doing - as its the least problematic in theory - is replicating public folders. They simply refuse to replicate at all to the new server even after 24 hours.
I've never had a migration / replication fail, so I'm a little stumped at where to start diagnosing the problems. I've turned on these logs, but they're not returning anything (possibly because no one's adding to the public folders currently?):
Replication AD Updates
Maximum
Replication Incoming Messages - Maximum
Replication Outgoing Messages - Maximum
Non-Delivery Reports - Maximum
Replication Backfill - Maximum
Replication General - Maximum
Replication Errors - Maximum
Any idea which way to head to diagnose this one?
The first thing we're doing - as its the least problematic in theory - is replicating public folders. They simply refuse to replicate at all to the new server even after 24 hours.
I've never had a migration / replication fail, so I'm a little stumped at where to start diagnosing the problems. I've turned on these logs, but they're not returning anything (possibly because no one's adding to the public folders currently?):
Replication AD Updates
Maximum
Replication Incoming Messages - Maximum
Replication Outgoing Messages - Maximum
Non-Delivery Reports - Maximum
Replication Backfill - Maximum
Replication General - Maximum
Replication Errors - Maximum
Any idea which way to head to diagnose this one?
ASKER
After I've run the pfmigration utility (using the command line PFMIGRATE.WSF /S:EXCHANGE2K3 /T:EXCHANGE01 /WMI:EXCHANGE2K3 /N:100 /A) , the log file says thus:
No folders were affected by the requested change.
Now, there's only fifteen folders according to the report I ran from the same utility, so it's not the folder 'limit' of 100 folders maximum.
Thanks in advance!
No folders were affected by the requested change.
Now, there's only fifteen folders according to the report I ran from the same utility, so it's not the folder 'limit' of 100 folders maximum.
Thanks in advance!
ASKER
Okay, after manually removing the replicas I crated by hand, now it claims that it configured all fifteen public folders for replication - and they still don't show up on server EXCHANGE01.
Hmmmmmmmmmmmm.............
Hmmmmmmmmmmmm.............
Are you getting any errors in evet viewer?
Also run a dcdiag and netdiag on the domain controller(s) reports back any errors
Also run a dcdiag and netdiag on the domain controller(s) reports back any errors
ASKER
dcdiang and netdiag are returning with no errors.
I do show replication information in the event logs on the source server, but this seems to never reach the destination server as there are no replication event logged there.
I do show replication information in the event logs on the source server, but this seems to never reach the destination server as there are no replication event logged there.
http://www.amset.info/exchange/migration.asp
Go down to the section that says populating the server with new data.
It gives a quick overview on mograting.
You should basically go into ESM then admin group and public folders.
right click and then go to connetc to and connect to your original server.
Now for the folders right lcick on and then go to the replication tab.
It should list your old server and new server.
You need to make sure the new server is in there and then you can remove the old server and it will only replicate to the new server.
Go down to the section that says populating the server with new data.
It gives a quick overview on mograting.
You should basically go into ESM then admin group and public folders.
right click and then go to connetc to and connect to your original server.
Now for the folders right lcick on and then go to the replication tab.
It should list your old server and new server.
You need to make sure the new server is in there and then you can remove the old server and it will only replicate to the new server.
ASKER
Well, the SMTP virtual server has a smart-host set upon it, in contravention to how it was supposed to be set up. After removing that, replication still isn't functioning.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
After bouncing the smart host on the previously-mentioned server, the replication is beginning to take place. Before, I couldn't see any of the public folders on EXCHANGE01, and now they're showing up and (slowly) starting to populate.
Tonight in the off-hours I'll force the replication and see if it actually completes them all.
Tonight in the off-hours I'll force the replication and see if it actually completes them all.
ASKER
A dead-on solution with links to how the rest of it should work. Thanks!
http://support.microsoft.com/kb/822895