Comments on: pfmigrate of public folders from Exch5.5 to E2K3 fails http://itknowledgeexchange.techtarget.com/itanswers/pfmigrate-of-public-folders-from-exch55-to-e2k3-fails/ Fri, 24 May 2013 12:30:07 +0000 hourly 1 By: mfppub http://itknowledgeexchange.techtarget.com/itanswers/pfmigrate-of-public-folders-from-exch55-to-e2k3-fails/#comment-37350 mfppub Wed, 06 Apr 2005 11:30:50 +0000 #comment-37350 We did not use the ADC as we migrated from 5.5 to a brand new Exchange 2K Organization. To migrate our public folders we used Microsoft’s interorg utility (Q238573) and it worked very well for us – we only used it to migrate the actual folders without migrating the data, and then we used Netiq to migrate the data.

]]> By: zerocool http://itknowledgeexchange.techtarget.com/itanswers/pfmigrate-of-public-folders-from-exch55-to-e2k3-fails/#comment-37351 zerocool Wed, 06 Apr 2005 04:13:50 +0000 #comment-37351 The ADC is definatley the way to go… All public folders will easily be migrated. I use the same method for mailboxes.

Regards

]]> By: poomba1 http://itknowledgeexchange.techtarget.com/itanswers/pfmigrate-of-public-folders-from-exch55-to-e2k3-fails/#comment-37352 poomba1 Wed, 06 Apr 2005 03:11:20 +0000 #comment-37352 Had a buddy with the same issue. He broke the ADC on on the 5.5 user Outlook and Service account, exported to PST then had to reapply permissions from users accounts in the new AD. A pain, yes, but quicker than trying to work around the migrate tool issues. Also make sure you don’t have any AV software running on the 5.5 (the ol’ NAV for Ex 2.1x has been known to cause export issies in VSAPI/MAPI mode and background scanning).

]]>