Thank you. No, I meant clarification for myself. Public Folders are not my expertise.
________________________________ From: Michael B. Smith <mich...@smithcons.com> To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> Sent: Mon, February 15, 2010 1:16:02 PM Subject: RE: Exchange 2003 to 2007 Public Folder migration No clarification required. I believe Simon and I both understood that. We were describing a process that we find WORKS BETTER IN THE REAL WORLD the MoveAllReplicas. That process is: Add the new server to the replica list (PS script). Use message tracking to see the success/failure of messages moving across (PS script or EMC). With get-publicfolderstatistics, determine when replication is complete (PS script). Remove the old server from the replica list (PS script). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From:Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 2:39 PM To: MS-Exchange Admin Issues Subject: Re: Exchange 2003 to 2007 Public Folder migration One clairification: I am trying to move all data from our 2003 servers to 2007. There are no users that are using the server but I need to move all data off to retire the server. Can I use a PS script to move data from a 2003 to 2007? Thanks again, Rick ________________________________ From:Simon Butler <si...@sembee.co.uk> To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> Sent: Mon, February 15, 2010 9:46:26 AM Subject: RE: Exchange 2003 to 2007 Public Folder migration Have to say that I recommend the same thing as well. MoveAllReplicas moves the content, so if you have users on the old system the content availability for them will be mixed – most likely unable to get anything, which includes things like free/busy information and the offline address book. PF replication is a pain, it has a mind of its own. Message tracking is the tool to use here initially. That will show you if the content is going across, as it sticks out somewhat – SERVER-IS @ example.local Check it is being delivered. Primary reason for replication failure is a smart host on the SMTP virtual server of the originating server. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://certificatesforexchange.com/ for certificates from just $23.99. Need a domain for your certificate? http://domainsforexchange.net/ Exchange Resources: http://exbpa.com/ From:Michael B. Smith [mailto:mich...@smithcons.com] Sent: 15 February 2010 17:26 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2007 Public Folder migration I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 –TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that’s just me. After that, using get-publicfolder –recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From:Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
