|
Glad that worked for you. Usually, getting
them to generate the status messages will get the backfill going. There are a
few other registry keys you can manipulate to force backfill if the stores are
really stubborn, but it sounds like you didn’t have to go that far. Andy From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacqui Hurst Thanks for your
help. I had looked at this article previously but missed out one vital
step which I hope appears to have resolved my issues. Instead of creating
both registry keys (articles 13629 and 321082) I only created the one for the
content. As I was getting very frustrated with the issue I decided to go
through all the troubleshooting steps again. Being a fresh day I noticed
that it was a requirement for both registry keys. I have followed the
steps on a backup PF server and this appears to have worked. I will now
look at implementing this on the main PF server. Thanks for pointing me
back to this article. It worked a treat. Jacqui From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schan Another KB article that may help you: How to troubleshoot public folder
replication problems in Exchange 2000 Server and in Exchange Server 2003: http://support.microsoft.com/kb/842273/ Andy From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sorry this is off topic but
this group is usually an excellent source of information on Exchange 200x. Can anyone advise how, if
it is possible, to force the replication
of all content from an Exchange
5.5 public folder server to an Exchange 2003 server. Some of my folders
appear to be replicating new data but not older entries. Messaging is
working fine between servers and the issue is not across all public folders
either. Cheers Jacqui |
Title: OT: Exchange Public folder content replication
- RE: [ActiveDir] OT: Exchange Public folder content replicati... Andy Schan
