You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -39,7 +39,7 @@ The Remove-PublicFolderMailboxMigrationRequest cmdlet is intended for troublesho
39
39
40
40
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).
41
41
42
-
## EXAMPLES
42
+
## EXAMPLES and SCENARIOS
43
43
44
44
### -------------------------- Example 1 --------------------------
### -------Scenario 2: Remove duplicate public folder mailbox migration tasks-----------
76
+
77
+
If you observe two or more public folder mailbox migration requests created for the same target mailbox, this means the public folder mailbox migration request is duplicated.
78
+
79
+
You can find duplicates by running the `Get-PublicFolderMailboxMigrationRequest` cmdlet. If a mailbox name is mentioned as a target mailbox more than once, then it means you have duplicate requests.
80
+
81
+
You can also use the following cmdlet to find duplicate requests:
82
+
83
+
`Get-PublicFolderMailboxMigrationRequest | group TargetMailbox |?{$_.Count -gt 1}`
84
+
85
+
If you do not get any output from the above command, then you do not have any duplicate mailbox migration requests.
86
+
87
+
[A sample script is provided here](https://gallery.technet.microsoft.com/scriptcenter/Remove-Duplicate-public-055f0e5e) to detect duplicate or orphaned public folder mailbox migration requests and also remove them.
0 commit comments