do I need to run *Update-PublicFolderHierarchy* after I run AddReplicaToPFRecursive? I have a PF on each MB server besides the Exchange 2003 server.
On Fri, Jun 28, 2013 at 5:50 PM, Michael B. Smith <[email protected]>wrote: > Please please PLEASE stop using MoveAllReplicas.**** > > ** ** > > If I could get MSFT to change their docs, I would. I’ve tried several > times.**** > > ** ** > > Use AddReplicaToPFRecursive, let replication happen, then > REmoveReplicaFromPFRecursive.**** > > ** ** > > My way – you can’t lose data.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *S Powell > *Sent:* Friday, June 28, 2013 5:30 PM > *To:* [email protected] > *Subject:* Re: [Exchange] Preferred method to move Exchange 2003 PF to > 2010**** > > ** ** > > having just FAILED EPICLY at moving my 2007 PFs from one server to > another, I'd first export them all as .pst then use move all replicas. If > anything goes wrong you have the pst to fall back on quickly... nothing is > worse then seeing 2700 contacts go *poof* ... trust me.**** > > ** ** > > move all replicas on 2010 powershell**** > > > **** > > > > ----------------**** > > Robert '); drop table Students;-- **** > > ** ** > > On Fri, Jun 28, 2013 at 1:42 PM, Todd Lemmiksoo <[email protected]> > wrote:**** > > I am planning on moving our Exchange 2003 PF replicas to 2010 next week. I > have seen a couple of ways to do this. **** > > 1. Use 2003 ESM to "Move all Replicas".**** > > OR**** > > 2. Use 2010 powershell move all replicas.**** > > Is there a consensus as to which method works best. > **** > > > -- > T. Todd Lemmiksoo **** > > ** ** > -- T. Todd Lemmiksoo
