Member Avatar for helen

When trying to migrate public folders from a 2000 exchange server to a 2003 exchange server folder will not move. The public folders are in the same tree. It says that you can just copy and past but it will not let me paste. If I try to go through the properties will not allow me to set the root directory. Any suggestions on what to do?

  • 3 Contributors
  • 3 Replies
  • 123 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by feigned

Dani AI

Generated

When Exchange 2000 -> 2003 public-folder moves fail, permissions are one possible cause (as and pointed out) but the more reliable, supported path is replica-based migration rather than trying to drag/drop or change the store root directly. Create a replica on the Exchange 2003 server, let replication finish, then remove the replica from the 2000 server. For large hierarchies use a tool that can operate on a tree rather than individual folders.

Checklist and quick checks

  • Confirm the Exchange 2003 server has a mounted Public Folder store and that the Microsoft Exchange System Attendant and Information Store services are running.
  • Verify both servers are in the same Exchange organization and that AD replication is healthy.
  • Ensure RPC/network connectivity and firewall rules allow Exchange-to-Exchange replication (dynamic RPC ports and endpoint mapper).
  • Look in the Application event log on both servers for public-folder or Information Store replication errors; those messages pinpoint problems faster than guessing.

Practical steps to move folders

  • In Exchange System Manager: expand Servers -> target server -> First Storage Group -> Public Folder Store -> Public Folders. On the folder to move use All Tasks -> Add Replica and select the Exchange 2003 server. Wait for replication to complete and verify content and ACLs on the replica, then remove the old replica.
  • For bulk moves or to monitor replication progress, use PFDAVAdmin (Exchange 2000/2003 utility) to add replicas for many folders, watch status, and export if needed.
  • If replication stalls, test with a small test folder, review event logs, and restart the Exchange services in a maintenance window rather than removing replicas prematurely.

Cautions

  • Do not delete the original store or remove all replicas until the target has a complete, verified replica.
  • Double-check public-folder ACLs and membership of the account used to perform the migration (Exchange/Organization Admin rights).
  • If logs show replication errors you cannot resolve, collect the event log text and the exact error codes before contacting Microsoft support or searching the Microsoft Knowledge Base for the specific message.

Recommended Answers

All 3 Replies

Member Avatar for Zachery

there are probally permissions settings effecting you some where down the trees

Member Avatar for helen

We have tried all ways, we have looked at the permissions. We are having difficulty with the replication of folders also.

Member Avatar for feigned

We have tried all ways, we have looked at the permissions. We are having difficulty with the replication of folders also.

It's all in the permissions.

Can't export/import the stores?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.