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
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md
+35-36Lines changed: 35 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ ms.reviewer:
12
12
# New-PublicFolderMoveRequest
13
13
14
14
## SYNOPSIS
15
-
This cmdlet is available only in on-premises Exchange.
15
+
The `New-PublicFolderMoveRequest` cmdlet is available only in on-premises Exchange.
16
16
17
-
Use the New-PublicFolderMoveRequest cmdlet to begin the process of moving public folder contents between public folder mailboxes. Moving public folders only moves the physical contents of the public folder; it doesn't change the logical hierarchy. When the move request is completed, you must run the Remove-PublicFolderMoveRequest cmdlet to remove the request or wait until the time specified in the CompletedRequestAgeLimit parameter has passed. The request must be removed before you can run another move request.
17
+
Use the `New-PublicFolderMoveRequest` cmdlet to begin the process of moving public folder contents between public folder mailboxes. Moving public folders only moves the physical contents of the public folder; it doesn't change the logical hierarchy. When the move request is completed, you must run the `Remove-PublicFolderMoveRequest` cmdlet to remove the request or wait until the time specified in the **CompletedRequestAgeLimit** parameter has passed. The request must be removed before you can run another move request.
18
18
19
-
Be aware that the target public folder mailbox will be locked while the move request is active. See the Detailed Description section below for more details.
19
+
Be aware that the target public folder mailbox will be locked while the move request is active. For more information, see the Detailed Description section below.
20
20
21
21
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should make sure no users are accessing public folder data in that target public folder mailbox.
46
+
The `New-PublicFolderMoveRequest` cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox.
47
47
48
-
To move the public folder mailbox to another mailbox database, use the New-MoveRequest cmdlet. To ensure that this folder is already in the target public folder mailbox, run the Update-PublicFolderMailbox cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script.
48
+
To move the public folder mailbox to another mailbox database, use the `New-MoveRequest` cmdlet. To ensure that this folder is already in the target public folder mailbox, run the `Update-PublicFolderMailbox` cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script.
49
49
50
50
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://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
51
51
@@ -69,16 +69,15 @@ You can also move a branch of public folders by using the Move-PublicFolderBranc
This example moves all public folders from public folder mailbox Pub1 to public folder mailbox Pub2.
77
76
78
77
## PARAMETERS
79
78
80
79
### -Folders
81
-
The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, child public folders won't be moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability.
80
+
The **Folders** parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders won't be moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability.
The TargetMailbox parameter specifies the target public folder mailbox that you want to move the public folders to. You can use any value that uniquely identifies the mailbox. For example:
96
+
The **TargetMailbox** parameter specifies the target public folder mailbox that you want to move the public folders to. You can use any value that uniquely identifies the mailbox. For example:
The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
123
+
The **AcceptLargeDataLoss** switch specifies that the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
125
124
126
-
You need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail.
125
+
You need to use this switch if you set the **LargeItemLimit** parameter to a value of **51** or higher. Otherwise, the command will fail.
The AllowLargeItems switch specifies that you can move large items only when large items are encountered. You don't need to specify a value with this switch.
141
+
The **AllowLargeItems** switch specifies that you can move large items only when they're encountered. You don't need to specify a value with this switch.
143
142
144
143
Large items are email messages with a maximum of 1,023 attachments.
The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
159
+
The **BadItemLimit** parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to be completed.
161
160
162
-
Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again.
161
+
Valid input for this parameter is an integer or the value **unlimited**. The default value is **0**, which means that the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend **10** or lower) so that the request can proceed. If too many bad items are detected, consider using the `New-MailboxRepairRequest` cmdlet to attempt to fix corrupted items in the source mailbox, and then try the request again.
The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
177
+
The **CompletedRequestAgeLimit** parameter specifies how long the request will be kept after it has been completed before being automatically removed. The default value for this parameter is **30 days**.
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
193
+
The **Confirm** switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding.
195
194
196
-
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
197
-
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
195
+
- Destructive cmdlets (for example, `Remove-\*` cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
196
+
- Most other cmdlets (for example, `New-\*` and `Set-\*` cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
212
+
The **DomainController** parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
260
+
The **Priority** parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
285
+
The **RequestExpiryInterval** parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
287
286
288
-
- The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value.
289
-
- If the request fails, you need to manually remove it by using the corresponding Remove-\*Request cmdlet.
287
+
- The completed request is automatically removed based on the **CompletedRequestAgeLimit** parameter value.
288
+
- If the request fails, you need to manually remove it by using the corresponding `Remove-\*Request` cmdlet.
290
289
291
290
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
292
291
293
-
When you use the value Unlimited, the completed request isn't automatically removed.
292
+
When you use the value **Unlimited**, the completed request isn't automatically removed.
The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
308
+
The **Suspend** switch specifies whether or not to suspend the request. You don't need to specify a value with this switch.
310
309
311
-
If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
310
+
If you use this switch, the request is queued, but the request won't reach the status of **InProgress** until you resume the request with the relevant resume cmdlet.
The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
326
+
The **SuspendComment** parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the **Suspend** parameter.
The SuspendWhenReadyToComplete switch specifies whether to suspend the request before it reaches the status of CompletionInProgress. You don't need to specify a value with this switch.
342
+
The **SuspendWhenReadyToComplete** switch specifies whether or not to suspend the request before it reaches the status of **CompletionInProgress**. You don't need to specify a value with this switch.
344
343
345
-
After the move is suspended, it has a status of AutoSuspended. You can then manually complete the move by using the Resume-PublicFolderMoveRequest command.
344
+
After the move is suspended, it has a status of **AutoSuspended**. You can then manually complete the move by using the `Resume-PublicFolderMoveRequest` command.
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
360
+
The **WhatIf** switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
392
+
The `CommonParameters` cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
394
393
395
394
## INPUTS
396
395
397
396
### Input types
398
-
To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.
397
+
To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the **Input Type** field for a cmdlet is blank, the cmdlet doesn't accept input data.
399
398
400
399
## OUTPUTS
401
400
402
401
### Output types
403
-
To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.
402
+
To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the **Output Type** field is blank, the cmdlet doesn't return data.
0 commit comments