Exchange 2010 Public Folder move to new Exchange 2010 server.
Hello Experts!
I have around 4500 Public Folders I need to move from physical Exchange 2010 servers to virtual Exchange 2010 servers and I would appreciate an assist with the best means to accomplish this. Here are my specific questions, but I welcome any other tips:
1. There are several pre-canned scripts related to moving/migrating PFs and replicas in the $exscripts folder, which one would be the most appropriate for this situation? It's been several years since I've had to mess with 2010 PFs since they've thankfully been transitioned to PF mailboxes in 2013/2016, and I'm fuzzy on the details. Do I have to target the upstream server to replicate from or will any server containing the PF data suffice?
2. Bandwidth is a concern for this project due to the shear number of items we're moving. Once I pull the trigger on whatever script I go with, will replication begin immediately or will it adhere to the replication schedule? I would like to limit replication to only occur during non-production hours.
3. I would really rather not start with the '\' PF and recurse down. What options exist to move the PFs in stages possibly based on an input .csv file similar to a Staged migration with Exchange Online. I'm just referring to the use of a .csv file to specify which items to move.
Thanks in advance.
I have around 4500 Public Folders I need to move from physical Exchange 2010 servers to virtual Exchange 2010 servers and I would appreciate an assist with the best means to accomplish this. Here are my specific questions, but I welcome any other tips:
1. There are several pre-canned scripts related to moving/migrating PFs and replicas in the $exscripts folder, which one would be the most appropriate for this situation? It's been several years since I've had to mess with 2010 PFs since they've thankfully been transitioned to PF mailboxes in 2013/2016, and I'm fuzzy on the details. Do I have to target the upstream server to replicate from or will any server containing the PF data suffice?
2. Bandwidth is a concern for this project due to the shear number of items we're moving. Once I pull the trigger on whatever script I go with, will replication begin immediately or will it adhere to the replication schedule? I would like to limit replication to only occur during non-production hours.
3. I would really rather not start with the '\' PF and recurse down. What options exist to move the PFs in stages possibly based on an input .csv file similar to a Staged migration with Exchange Online. I'm just referring to the use of a .csv file to specify which items to move.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.