asked on

Exhange 2003 public folders not replicating to my new server

I setup a new Windows 2003 server running Exchange 2003. I am trying to move everything from my old server (Win2k/Exchange 2k3) to it. I started my setting the public folders to replicate to the new server. However, nothing is going through to the new server. Everything appears to be stuck in the message queue on the old server. Any ideas? Should I reinstall exchange on the new server? I am desperate at this point

Amitspeedstar

Hi u can use the public folder tool kown as pfmigrate.wsf . For more info about this tool see the below technet article

http://support.microsoft.com/kb/822895/en-us

Amit.

rakeshmiglani

stuck in which queue?

quahitis

ASKER

Stuck in the newserver.domain queue on the old server. It acts like it wants to send it but it can't for sone reason

rakeshmiglani

is the mail flow working fine between these two servers. try to send a messge from a user on the old server to a user on the new server and check via message tracking

quahitis

ASKER

I am not getting anything to the new server at all. All I did was install exchange and started trying to migrate folders. I have not allowed smtp traffic to it yet which could be causing the prolbme now that I think of it.

rakeshmiglani

public folder replication takes place via smtp messages.

quahitis

ASKER

Ok, SMTP traffic is now allowed but it is still not replicating. I have a CipherTrust email appliance that all incoming and outgoing mail is routed through. Would this interfere with the replication process?

ASKER CERTIFIED SOLUTION

abhi_ak

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Sembee

Sounds like the classic smart host on the SMTP VS. Remove it and replace it with an SMTP Connector to send email through your appliance.

Antivirus/Antispam can also get in the way. Make sure that any desktop antivirus is set to NOT scan the Exchange directories.

Message tracking - as already mentioned - is the best tool for diagnosing what is happening. Replication messages stick out in the tracking logs and allow you to see what is happening. Make sure that you enable it on both servers - so that you can be sure the messages aren't being dropped when the arrive on the other server.

Simon.