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
This example is related to the previous example where more than 100 records were available (the value of the LastPage property from that command was False). We're using the same date range, but this time we're using the value of the Watermark property from the previous command for the PageCookie parameter in this command to get the remaining results.
67
+
This example is related to the previous example where more than 100 records were available (the value of the LastPage property from that command was False). We're using the same date range, but this time we're using the value of the Watermark property from the previous command for the PageCookie parameter in this command to get the remaining results in a loop. ResultData from each iteration can be used as needed.
The PageCookie parameter specifies whether to get more data when the value of the LastPage property in the command output is False. If you don't use the PageSize parameter, a maximum of 100 records are returned. If you use the PageSize parameter, a maximum of 5000 records can be returned. To get more records than what as returned in the current command, use the value of the Watermark property from the output of the current command as the value for the PageCookie parameter in a new command with the same date range and filters.
243
+
The PageCookie parameter specifies whether to get more data when the value of the LastPage property in the command output is False. If you don't use the PageSize parameter, a maximum of 100 records are returned. If you use the PageSize parameter, a maximum of 5000 records can be returned. To get more records than what as returned in the current command, use the value of the Watermark property from the output of the current command as the value for the PageCookie parameter in a new command with the same date range and filters. The PageCookie value is valid for 120 seconds to fetch the next set of records for same query.
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 100.
259
+
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 100. Consider using a smaller PageSize value to avoid PageCookie expiry when exporting large datasets.
The HoldCleanup switch instructs the Managed Folder Assistant to clean up duplicate versions of items in the Recoverable Items folder that may have been created when a mailbox is on In-Place Hold, Litigation Hold, or has Single Item Recovery enabled. You don't need to specify a value with this switch.
171
-
172
-
Removing duplicate items from the Recoverable Items folder reduces the folder size and may help prevent reaching Recoverable Items quota limits. For more details about Recoverable Items quota limits, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder).
173
-
174
-
```yaml
175
-
Type: SwitchParameter
176
-
Parameter Sets: HoldCleanup
177
-
Aliases:
178
-
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
179
-
180
-
Required: True
181
-
Position: Named
182
-
Default value: None
183
-
Accept pipeline input: False
184
-
Accept wildcard characters: False
185
-
```
186
-
187
-
```yaml
188
-
Type: SwitchParameter
189
-
Parameter Sets: Default
190
-
Aliases:
191
-
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
192
-
193
-
Required: False
194
-
Position: Named
195
-
Default value: None
196
-
Accept pipeline input: False
197
-
Accept wildcard characters: False
198
-
```
199
-
200
-
### -StopHoldCleanup
201
-
This parameter is available only in the cloud-based service.
202
-
203
-
The StopHoldCleanup switch stops a previous hold clean-up command that was issued on the mailbox. You don't need to specify a value with this switch.
204
-
205
-
A hold clean-up command will run until it completely scans the Recoverable Items folder for duplicate versions of items (it even continues after an interruption). In some cases, the hold clean-up command gets stuck, which can block other regular MRM tasks on the mailbox (for example, expiring items). The StopHoldCleanup switch tells MRM to abandon the stuck hold clean-up task so that regular tasks can continue.
206
-
207
-
```yaml
208
-
Type: SwitchParameter
209
-
Parameter Sets: StopHoldCleanup
210
-
Aliases:
211
-
Applicable: Exchange Online
212
-
213
-
Required: True
214
-
Position: Named
215
-
Default value: None
216
-
Accept pipeline input: False
217
-
Accept wildcard characters: False
218
-
```
219
-
220
168
### -AdaptiveScope
221
169
This parameter is available only in the cloud-based service.
The HoldCleanup switch instructs the Managed Folder Assistant to clean up duplicate versions of items in the Recoverable Items folder that may have been created when a mailbox is on In-Place Hold, Litigation Hold, or has Single Item Recovery enabled. You don't need to specify a value with this switch.
331
+
332
+
Removing duplicate items from the Recoverable Items folder reduces the folder size and may help prevent reaching Recoverable Items quota limits. For more details about Recoverable Items quota limits, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder).
333
+
334
+
```yaml
335
+
Type: SwitchParameter
336
+
Parameter Sets: Identity, HoldCleanupParameterSet
337
+
Aliases:
338
+
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
339
+
340
+
Required: False
341
+
Position: Named
342
+
Default value: None
343
+
Accept pipeline input: False
344
+
Accept wildcard characters: False
345
+
```
346
+
381
347
### -InactiveMailbox
382
348
This parameter is available only in the cloud-based service.
383
349
@@ -389,7 +355,27 @@ When you use this switch, items aren't moved from the inactive mailbox to the ar
This parameter is available only in the cloud-based service.
371
+
372
+
The StopHoldCleanup switch stops a previous hold clean-up command that was issued on the mailbox. You don't need to specify a value with this switch.
373
+
374
+
A hold clean-up command will run until it completely scans the Recoverable Items folder for duplicate versions of items (it even continues after an interruption). In some cases, the hold clean-up command gets stuck, which can block other regular MRM tasks on the mailbox (for example, expiring items). The StopHoldCleanup switch tells MRM to abandon the stuck hold clean-up task so that regular tasks can continue.
0 commit comments