TechNet topic updates

chrisda · chrisda · commit e1cb98a5ee7a · 2018-03-02T16:35:47.000-08:00
Updates done in the TechNet versions (bugs) that needed to be synced to GitHub.
diff --git a/exchange/exchange-ps/exchange/Get-ClientAccessRule.md b/exchange/exchange-ps/exchange/Get-ClientAccessRule.md
@@ -6,6 +6,8 @@ schema: 2.0.0
 # Get-ClientAccessRule
 
 ## SYNOPSIS
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+
 Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
@@ -18,20 +20,20 @@ Get-ClientAccessRule [[-Identity] <ClientAccessRuleIdParameter>] [-Confirm] [-Do
 ```
 
 ## DESCRIPTION
-Client access rules are like transport rules for client connections to your organization. You use conditions and exceptions to identify the connections based on the user or properties of the client or the connection, and actions that define what to do with those connections.
+Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
 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).
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Online)
+### Example 1
 ```
 Get-ClientAccessRule
 ```
 
 This example shows a summary list of all client access rules.
 
-### Example 2 -------------------------- (Exchange Online)
+### Example 2
 ```
 Get-ClientAccessRule "Block Client Connections from 192.168.1.0/24" | Format-List
 ```
@@ -61,7 +63,9 @@ Accept wildcard characters: False
 ```
 
 ### -DomainController
-This parameter is reserved for internal Microsoft use.
+This parameter is available only in on-premises Exchange.
+
+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.
 
 ```yaml
 Type: Fqdn
diff --git a/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md
@@ -67,11 +67,12 @@ This example returns all dynamic distribution groups whose names contain the str
 
 ### Example 4
 ```
-$FTE = Get-DynamicDistributionGroup "Full Time Employees"; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter
+$FTE = Get-DynamicDistributionGroup "Full Time Employees"; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer
 ```
 
 This example returns the members for the dynamic distribution group named Full Time Employees. The first command stores the dynamic distribution group object in the variable $FTE. The second command uses the Get-Recipient cmdlet to list the recipients that match the criteria defined for the dynamic distribution group.
 
+
 ## PARAMETERS
 
 ### -Anr
diff --git a/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md
@@ -261,10 +261,10 @@ The Status parameter filters the results based on status. You can use the follow
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 - Synced
diff --git a/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md
@@ -262,10 +262,10 @@ The Status parameter filters the results based on status. You can use the follow
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 - Synced
diff --git a/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md
@@ -238,10 +238,10 @@ The Status parameter filters the results based on status. You can use the follow
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 - Synced
diff --git a/exchange/exchange-ps/exchange/Get-MoveRequest.md b/exchange/exchange-ps/exchange/Get-MoveRequest.md
@@ -219,10 +219,10 @@ The MoveStatus parameter returns move requests in the specified status. You can
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 You can't use this parameter with the Identity parameter.
diff --git a/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md
@@ -221,10 +221,10 @@ The Status parameter filters the results based on status. You can use the follow
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 - Synced
diff --git a/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md
@@ -211,10 +211,10 @@ The Status parameter filters the results based on status. You can use the follow
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 - Synced
diff --git a/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md
@@ -208,10 +208,10 @@ The Status parameter filters the results based on status. You can use the follow
 
 - InProgress
 
-- None
-
 - Queued
 
+- Retrying
+
 - Suspended
 
 - Synced
diff --git a/exchange/exchange-ps/exchange/New-ClientAccessRule.md b/exchange/exchange-ps/exchange/New-ClientAccessRule.md
@@ -6,6 +6,8 @@ schema: 2.0.0
 # New-ClientAccessRule
 
 ## SYNOPSIS
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+
 Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
@@ -24,7 +26,7 @@ New-ClientAccessRule [-Name] <String> -Action <AllowAccess | DenyAccess>
 ```
 
 ## DESCRIPTION
-Client access rules are like transport rules for client connections to your organization. You use conditions and exceptions to identify the connections based on the user or properties of the client or the connection, and actions that define what to do with those connections.
+Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
 Note: Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list:
 
@@ -40,14 +42,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Online)
+### Example 1
 ```
 New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1
 ```
 
 This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you'll lose the ability to fix the rules yourself (you'll need to call Microsoft Customer Service and Support).
 
-### Example 2 -------------------------- (Exchange Online)
+### Example 2
 ```
 New-ClientAccessRule -Name "Block ActiveSync" -Action DenyAccess -AnyOfProtocols ExchangeActiveSync -ExceptAnyOfClientIPAddressesOrRanges 192.168.10.1/24
 ```
@@ -221,7 +223,9 @@ Accept wildcard characters: False
 ```
 
 ### -DomainController
-This parameter is reserved for internal Microsoft use.
+This parameter is available only in on-premises Exchange.
+
+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.
 
 ```yaml
 Type: Fqdn
diff --git a/exchange/exchange-ps/exchange/Release-QuarantineMessage.md b/exchange/exchange-ps/exchange/Release-QuarantineMessage.md
@@ -60,15 +60,15 @@ This example releases the quarantined message with the specified Identity value
 
 ### Example 3
 ```
-Get-QuarantineMessage | Release-QuarantineMessage -ReleaseToAll -Delete
+Get-QuarantineMessage | Release-QuarantineMessage -ReleaseToAll
 ```
 
-This example releases all messages to all original recipients and deletes all released messages from quarantine.
+This example releases all messages to all original recipients.
 
 ## PARAMETERS
 
 ### -Identities
-The Identities parameter identifies quarantined messages for bulk operations. You identify the messages by using the syntax: value1,value2.... The value is a unique quarantined message identifier in the format GUID1\\GUID2 (for example c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7.
+The Identities parameter identifies quarantined messages for bulk operations. You identify the messages by using the syntax: value1,value2,...valueN. The value is a unique quarantined message identifier in the format GUID1\\GUID2 (for example c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7).
 
 You can find the identity value for a quarantined message by using the Get-QuarantineMessage cmdlet.
 
@@ -210,9 +210,9 @@ Accept wildcard characters: False
 ```
 
 ### -Delete
-The Delete switch specifies whether to delete a message from quarantine after it's been released to all original recipients. You don't need to specify a value with this switch.
+**This parameter has been deprecated and is no longer used.**
 
-You can only use this switch with the ReleaseToAll parameter.
+To delete quarantined messages, use the Delete-QuarantineMessage cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md b/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md
@@ -6,6 +6,8 @@ schema: 2.0.0
 # Remove-ClientAccessRule
 
 ## SYNOPSIS
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+
 Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
@@ -18,13 +20,13 @@ Remove-ClientAccessRule [-Identity] <ClientAccessRuleIdParameter> [-Confirm] [-D
 ```
 
 ## DESCRIPTION
-Client access rules are like transport rules for client connections to your organization. You use conditions and exceptions to identify the connections based on the user or properties of the client or the connection, and actions that define what to do with those connections.
+Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
 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).
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Online)
+### Example 1
 ```
 Remove-ClientAccessRule "Block Client Connections from 192.168.1.0/24"
 ```
@@ -92,7 +94,9 @@ Accept wildcard characters: False
 ```
 
 ### -DomainController
-This parameter is reserved for internal Microsoft use.
+This parameter is available only in on-premises Exchange.
+
+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.
 
 ```yaml
 Type: Fqdn
diff --git a/exchange/exchange-ps/exchange/Set-ClientAccessRule.md b/exchange/exchange-ps/exchange/Set-ClientAccessRule.md
@@ -6,6 +6,8 @@ schema: 2.0.0
 # Set-ClientAccessRule
 
 ## SYNOPSIS
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+
 Use the Set-ClientAccessRule cmdlet to modify existing client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
@@ -24,7 +26,7 @@ Set-ClientAccessRule [-Identity] <ClientAccessRuleIdParameter> [-Action <AllowAc
 ```
 
 ## DESCRIPTION
-Client access rules are like transport rules for client connections to your organization. You use conditions and exceptions to identify the connections based on the user or properties of the client or the connection, and actions that define what to do with those connections.
+Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
 Note: Not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list:
 
@@ -40,7 +42,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Online)
+### Example 1
 ```
 Set-ClientAccessRule "Allow IMAP4" -AnyOfClientIPAddressesOrRanges @{Add="172.17.17.27/16"}
 ```
@@ -226,7 +228,9 @@ Accept wildcard characters: False
 ```
 
 ### -DomainController
-This parameter is reserved for internal Microsoft use.
+This parameter is available only in on-premises Exchange.
+
+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.
 
 ```yaml
 Type: Fqdn
diff --git a/exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
@@ -1587,13 +1587,9 @@ Accept wildcard characters: False
 ### -BoxAttachmentsEnabled
 This parameter is available only in the cloud-based service.
 
-The BoxAttachmentsEnabled parameter specifies whether to allow Box attachments in Outlook on the web when the value of the ThirdPartyAttachmentsEnabled parameter is $true. Valid values are:
+This parameter has been deprecated and is no longer used.
 
-- $true: Box attachments are enabled. This is the default value.
-
-- $false: Box attachments are disabled.
-
-This parameter has no effect if the value of the ThirdPartyAttachmentsEnabled parameter is $false.
+To enable or disable Box attachments in Outlook on the web, use the ThirdPartyAttachmentsEnabled parameter.
 
 ```yaml
 Type: $true | $false
@@ -1631,13 +1627,9 @@ Accept wildcard characters: False
 ### -DropboxAttachmentsEnabled
 This parameter is available only in the cloud-based service.
 
-The DropboxAttachmentsEnabled parameter specifies whether to allow Dropbox attachments in Outlook on the web when the value of the ThirdPartyAttachmentsEnabled parameter is $true. Valid values are:
-
-- $true: Dropbox attachments are enabled. This is the default value.
+This parameter has been deprecated and is no longer used.
 
-- $false: Dropbox attachments are disabled.
-
-This parameter has no effect if the value of the ThirdPartyAttachmentsEnabled parameter is $false.
+To enable or disable Dropbox attachments in Outlook on the web, use the ThirdPartyAttachmentsEnabled parameter.
 
 ```yaml
 Type: $true | $false
@@ -1695,13 +1687,9 @@ Accept wildcard characters: False
 ### -GoogleDriveAttachmentsEnabled
 This parameter is available only in the cloud-based service.
 
-The GoogleDriveAttachmentsEnabled parameter specifies whether to allow Google Drive attachments in Outlook on the web when the value of the ThirdPartyAttachmentsEnabled parameter is $true. Valid values are:
-
-- $true: Google Drive attachments are enabled. This is the default value.
-
-- $false: Google Drive attachments are disabled.
+This parameter has been deprecated and is no longer used.
 
-This parameter has no effect if the value of the ThirdPartyAttachmentsEnabled parameter is $false.
+To enable or disable Google Drive attachments in Outlook on the web, use the ThirdPartyAttachmentsEnabled parameter.
 
 ```yaml
 Type: $true | $false
@@ -1883,7 +1871,7 @@ Accept wildcard characters: False
 ### -ThirdPartyAttachmentsEnabled
 This parameter is available only in the cloud-based service.
 
-The ThirdPartyAttachmentsEnabled parameter specifies whether to allow third-party attachments in Outlook on the web. Valid values are:
+The ThirdPartyAttachmentsEnabled parameter specifies whether to allow third-party (for example, Box, Dropbox, and Google Drive) attachments in Outlook on the web. Valid values are:
 
 - $true: Third-party attachments are enabled. Users can connect their third-party file sharing accounts and share files over email. This is the default value.
 
diff --git a/exchange/exchange-ps/exchange/Test-ClientAccessRule.md b/exchange/exchange-ps/exchange/Test-ClientAccessRule.md
@@ -6,6 +6,8 @@ schema: 2.0.0
 # Test-ClientAccessRule
 
 ## SYNOPSIS
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+
 Use the Test-ClientAccessRule cmdlet to test how client access rules affect access to your cloud-based organization. If any of the client properties you specify for this cmdlet match any client access rules, the rules are returned in the results.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
@@ -15,13 +17,12 @@ For information about the parameter sets in the Syntax section below, see Exchan
 ```
 Test-ClientAccessRule
  -AuthenticationType <BasicAuthentication | NonBasicAuthentication | AdfsAuthentication | CertificateBasedAuthentication | OAuthAuthentication>
- -Protocol <ExchangeWebServices | RemotePowerShell | OutlookAnywhere | POP3 | IMAP4 | OutlookWebApp | ExchangeAdminCenter | ExchangeActiveSync | OfflineAddressBook | PowerShellWebServices | REST>
- -RemoteAddress <IPAddress> -RemotePort <Int32> -User <MailboxIdParameter> [-Confirm]
+ -Protocol <ExchangeWebServices | RemotePowerShell | OutlookAnywhere | POP3 | IMAP4 | OutlookWebApp | ExchangeAdminCenter | ExchangeActiveSync | OfflineAddressBook | PowerShellWebServices | REST> -RemoteAddress <IPAddress> -RemotePort <Int32> -User <MailboxIdParameter> [-Confirm]
  [-OAuthClaims <Hashtable>] [-WhatIf] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-Client access rules are like transport rules for client connections to your organization. You use conditions and exceptions to identify the connections based on the user or properties of the client or the connection, and actions that define what to do with those connections.
+Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
 Note: Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list:
 
@@ -37,7 +38,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Online)
+### Example 1
 ```
 Test-ClientAccessRule -AuthenticationType BasicAuthentication -Protocol OutlookWebApp -RemoteAddress 172.17.17.26 -RemotePort 443 -User julia@contoso.com
 ```
