I try to use below EMS command to replicate \somePFfolder to Ex201-PFDatabase: Set-PublicFolder -identify '\somePFfolder' -replicas @{Add=Ex2010-PFDatabase1} And I got this error: Cannot process argument transformation on parameter 'Replicas'. Cannot convert the "System.Collections.Hashtable" value of type "System.Collections.Hashtable" to type "Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter[]". + CategoryInfo : InvalidData: (:) [Set-PublicFolder], ParameterBindin...mationException + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-PublicFolder Can somebody help me to correct the parameter type conversion error? thanks

Hi, I find it easier to use the PF Scrips that are available in the Scripts folder. To add a server as replica you could use this syntax: .\AddReplicaToPFRecursive.ps1 -TopPublicFolder \somePFfolder -ServerToAdd SERVER2 ...cause when using Set-PublicFolder it would be to easy to replace the server/public folder database, instead of just adding a replica. So if you want to add PFDatabase1 to a folder that already have PFDatabase2 set, the command would be: Set-PublicFolder \somePFfolder -Replicas "PFDatabase1","PFDatabase2" Scripts for Managing Public Folders in the Exchange Management Shell http://technet.microsoft.com/en-us/library/aa998596.aspxMartina Miskovic

Hi Andy, Is there any update?Fiona Liao TechNet Community Support

If we don't need to coexist with Exchange 2003 users, can we simply use below? The Exchange 2010 PF database already pre-populated with AddReplicaToPFRecursive.ps1 during the migration. 1. .\moveallreplicas.ps -server "ex2003_PF1" -Newserver "ex2010_PF1" --OR-- 1. Open Exchange System Manager form ex2003_PF1 Go to the public folder database, then right-click and select "Move All Replicas" and select the Exchange public folder database @ ex2010_PF1 2. Wait til the replicate completed 3. dismount/remove the Exchange 2003 PF database thanks

If we don't need to coexist with Exchange 2003 users, can we simply use below which I asume has the same effet of mvoeallreplicas.ps1? The Exchange 2010 PF database already pre-populated with AddReplicaToPFRecursive.ps1 during the migration. 1. Open Exchange System Manager 2. Go to the public folder database, then right-click and select "Move All Replicas" and select the Exchange public folder database 3. Wait til the replicate completed 4. dismount/remove the Exchange 2003 PF database thanks Not a good idea if you still have users on Exchange 2003, cause that would delete system folders that are needed for the users to be able to log on to Exchange 2003.Martina Miskovic

Hi Martina, thanks for the quick reply. We do not have any more Exchange 2003 left and like to decomission the Exchange 2003 servers. Does the plan make sense now? I don't think Exchange 2003 will let you delete the PF database if there are still system folder exist, right? thanks

I don't think Exchange 2003 will let you delete the PF database if there are still system folder exist, right? Yes, that is correct. Personally I never use the script MoveAllReplicas.ps1 cause it will move system public folders, like OWAScratch*, StoreEvents*, schema-root that Exchange 2010 will never need or use. I think using RemoveReplicaFromPFRecursive.ps1 is better and then handle the system folders manually (deleting the above system folders and remove the replica for OAB and free/busy) Example: ./RemoveReplicaFromPFRecursive.ps1 TopPublicFolder \ -servertoRemove Exchange2003 Martina Miskovic

I prefer the safer approach, keep the legacy system folders. We still have lots of Outlook 2003 users, they need the free/busy folders at the very least. Can you tell me the difference between MoveAllReplicas.ps1 and ReplaceReplicaOnRPFRecursive.ps1? They almost looks identical except ReplaceReplicasOnPFRecursive mentions nothing about system folders. thanks