Merge pull request MicrosoftDocs#1721 from MicrosoftDocs/chrisda

Chrisda to Master

Author: chrisda

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md

@@ -24,14 +24,23 @@ Get-AdvancedThreatProtectionDocumentDetail [-Action <MultiValuedProperty>] [-Dom
 For the reporting period and organization you specify, the cmdlet returns the following information:
 
 - Action
+
 - Document Id
+
 - Domain
+
 - Event Type
+
 - File Hash
+
 - File Name
+
 - File Path
+
 - Size
+
 - Timestamp
+
 - Workload
 
 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).

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md

@@ -25,11 +25,17 @@ Get-AdvancedThreatProtectionDocumentReport [-Action <MultiValuedProperty>] [-Agg
 ## DESCRIPTION
 For the reporting period and organization you specify, the cmdlet returns the following information:
 
+
 - Action
+
 - Count
+
 - Date
+
 - Domain
+
 - Event Type
+
 - Workload
 
 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).

exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md

@@ -187,7 +187,7 @@ The EnableMailboxIntelligence parameter specifies whether to enable or disable m
 - $true: Use mailbox intelligence in domain and user impersonation protection.
 
 - $false: Don't use mailbox intelligence in domain and user impersonation protection. This is the default value.
-- 
+
 ```yaml
 Type: $true | $false
 Parameter Sets: (All)

exchange/exchange-ps/exchange/antispam-antimalware/Enable-AntispamUpdates.md

@@ -9,7 +9,7 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016"
 # Enable-AntispamUpdates
 
 ## SYNOPSIS
-The Enable-AntispamUpdates cmdlet has been deprecated in Microsoft Exchange Server 2010 Service Pack 1.
+The Enable-AntispamUpdates cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and is no longer used.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
 
@@ -21,7 +21,7 @@ Enable-AntispamUpdates [[-Identity] <ServerIdParameter>] [-Confirm]
 ```
 
 ## DESCRIPTION
-This cmdlet has been deprecated in Exchange Server 2010 Service Pack 1.
+This cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and is no longer used.
 
 ## EXAMPLES
 
@@ -30,7 +30,7 @@ This cmdlet has been deprecated in Exchange Server 2010 Service Pack 1.
 Enable-AntispamUpdates
 ```
 
-This cmdlet has been deprecated in Exchange Server 2010 Service Pack 1.
+This cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and is no longer used.
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/antispam-antimalware/Release-QuarantineMessage.md

@@ -218,7 +218,7 @@ Accept wildcard characters: False
 ```
 
 ### -Delete
-**This parameter has been deprecated and is no longer used.**
+This parameter has been deprecated and is no longer used.
 
 To delete quarantined messages, use the Delete-QuarantineMessage cmdlet.
 

exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md

@@ -332,9 +332,7 @@ Accept wildcard characters: False
 ```
 
 ### -EndUserSpamNotificationCustomFromAddress
-The EndUserSpamNotificationCustomFromAddress parameter specifies a custom From address for end-user spam notification messages. Valid input for this parameter is an SMTP email address.
-
-This parameter is visible but not active, and may be deprecated in a future version of Exchange Online Protection.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: SmtpAddress
@@ -349,9 +347,7 @@ Accept wildcard characters: False
 ```
 
 ### -EndUserSpamNotificationCustomFromName
-The EndUserSpamNotificationCustomFromName parameter specifies a custom display name in the From field for end-user spam notification messages. If the value includes spaces, enclose the value in quotation marks (").
-
-This parameter is visible but not active, and may be deprecated in a future version of Exchange Online Protection.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: String

exchange/exchange-ps/exchange/antispam-antimalware/Update-SafeList.md

@@ -44,7 +44,7 @@ This example updates Safe Senders List data for the single user [email protected].
 Set-AdServerSettings -ViewEntireForest $true; Get-Mailbox -ResultSize Unlimited -RecipientTypeDetails UserMailbox | Update-Safelist
 ```
 
-This example updates safelist data for all user mailboxes in your Exchange organization. By default, the Exchange Management Shell is configured to retrieve or modify objects that reside in the domain in which the Exchange server resides. Therefore, to retrieve all the mailboxes in your Exchange organization, you must first set the scope of the Shell to the entire forest using the Set-AdServerSettings cmdlet. For more information, see Set-AdServerSettings.
+This example updates safelist data for all user mailboxes in your Exchange organization. By default, the Exchange Management Shell is configured to retrieve or modify objects that reside in the domain in which the Exchange server resides. Therefore, to retrieve all the mailboxes in your Exchange organization, you must first set the scope of the Exchange Manaagement Shell to the entire forest using the Set-AdServerSettings cmdlet.
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/client-access-servers/Enable-OutlookAnywhere.md

@@ -72,17 +72,15 @@ This example enables the Exchange Client Access server for Outlook Anywhere. The
 ## PARAMETERS
 
 ### -ClientAuthenticationMethod
-The ClientAuthenticationMethod parameter specifies the authentication method that the Autodiscover service provides to the Outlook Anywhere clients to authenticate to the Client Access server. This parameter accepts the following values:
+The ClientAuthenticationMethod parameter specifies the authentication method that the Autodiscover service provides to the Outlook Anywhere clients to authenticate to the Client Access server. Valid values are:
 
 - Basic
 
 - Ntlm
 
-- MaxValidValue Also known as Negotiate Ex authentication (NegoEx). This authentication type is reserved for future Microsoft use and shouldn't be used. Use of this setting will cause authentication to fail.
-
 This parameter must be specified if you don't use the DefaultAuthenticationMethod parameter. When you use this parameter without specifying the IISAuthenticationMethods parameter, IISAuthenticationMethods parameter is set to both NTLM and Basic.
 
-Although this parameter only allows setting one authentication method, the Shell doesn't return an error if you include multiple values.
+Although this parameter only allows setting one authentication method, the command won't return an error if you include multiple values.
 
 ```yaml
 Type: Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | MaxValidValue | Misconfigured
@@ -99,14 +97,12 @@ Accept wildcard characters: False
 ### -DefaultAuthenticationMethod
 The DefaultAuthenticationMethod parameter specifies whether to set both the ClientAuthenticationMethod and IISAuthenticationMethods parameters to the same authentication value.
 
-When you set an authentication value by using the DefaultAuthenticationMethod parameter, you force the specified authentication method to be used on the /rpc virtual directory in Internet Information Services (IIS). This parameter accepts the following values:
+When you set an authentication value by using the DefaultAuthenticationMethod parameter, you force the specified authentication method to be used on the /rpc virtual directory in Internet Information Services (IIS). Valid values are:
 
 - Basic
 
 - Ntlm
 
-- MaxValidValue Also known as Negotiate Ex authentication (NegoEx). This authentication type is reserved for future Microsoft use and shouldn't be used. Use of this setting will cause authentication to fail.
-
 If the DefaultAuthenticationMethod parameter is specified, neither the ClientAuthenticationMethod nor the IISAuthenticationMethods parameter can be used.
 
 ```yaml

exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessArray.md

@@ -99,7 +99,7 @@ The Site parameter filters the results by Active Directory site. You can use any
 - Distinguished name (DN)
 
 - GUID
-- 
+
 - To see a list of available sites, use the Get-ADSite cmdlet.
 
 ```yaml

exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessServer.md

@@ -13,6 +13,8 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Get-ClientAccessServer cmdlet to view settings that are associated with the Client Access server role.
 
+Note: In Exchange 2013 or later, use the Get-ClientAccessService cmdlet instead. If you have scripts that use Get-ClientAccessServer, update them to use Get-ClientAccessService.
+
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
 
 ## SYNTAX
@@ -24,8 +26,6 @@ Get-ClientAccessServer [[-Identity] <ClientAccessServerIdParameter>] [-DomainCon
 ```
 
 ## DESCRIPTION
-The Get-ClientAccessServer cmdlet will be removed in a future version of Exchange. You should use the Get-ClientAccessService cmdlet instead.
-
 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

exchange/exchange-ps/exchange/client-access-servers/Set-ClientAccessServer.md

@@ -11,7 +11,9 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016"
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Set-ClientAccessServer cmdlet to modify the client access configuration settings on Mailbox servers.
+Use the Set-ClientAccessServer cmdlet to modify settings that are associated with the Client Access server role.
+
+Note: In Exchange 2013 or later, use the Set-ClientAccessService cmdlet instead. If you have scripts that use Set-ClientAccessServer, update them to use Set-ClientAccessService.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
 
@@ -37,8 +39,6 @@ Set-ClientAccessServer [-Identity] <ClientAccessServerIdParameter> [-AutoDiscove
 ```
 
 ## DESCRIPTION
-The Set-ClientAccessServer cmdlet will be removed in a future version of Exchange. You should use the Set-ClientAccessService cmdlet instead.
-
 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

exchange/exchange-ps/exchange/client-access-servers/Set-OutlookAnywhere.md

@@ -101,15 +101,13 @@ Accept wildcard characters: False
 ### -ClientAuthenticationMethod
 This parameter is available or functional only in Exchange Server 2010.
 
-The ClientAuthenticationMethod parameter specifies the authentication method that the Autodiscover service provides to the Outlook Anywhere clients to authenticate to the Client Access server. This parameter accepts the following values:
+The ClientAuthenticationMethod parameter specifies the authentication method that the Autodiscover service provides to the Outlook Anywhere clients to authenticate to the Client Access server. Valid values are:
 
 - Basic
 
 - Ntlm
 
-- MaxValidValue Also known as Negotiate Ex authentication (NegoEx). This authentication type is reserved for future Microsoft use and shouldn't be used. Use of this setting will cause authentication to fail.
-
-Although you can use this parameter to set only one authentication method, the Shell doesn't return an error if you include multiple values.
+Although you can use this parameter to set only one authentication method, the command won't return an error if you include multiple values.
 
 ```yaml
 Type: Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | MaxValidValue | Misconfigured

exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md

@@ -2494,7 +2494,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are:
 
 - $true: All supported attachment types are avaialble for WebReady Document Viewing. This is the default value.
-- 
+
 - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are avaialble for WebReady Document Viewing (you can remove values from the lists).
 
 ```yaml

exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md

@@ -1109,7 +1109,7 @@ This parameter is available only in the cloud-based service.
 The LinkedInEnabled parameter specifies whether users can synchronize their LinkedIn contacts to their Contacts folder. Valid values are:
 
 - $true: LinkedIn integration is enabled. This is the default value.
-- 
+
 - $false: LinkedIn integration is disabled.
 
 ```yaml
@@ -2095,7 +2095,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are:
 
 - $true: All supported attachment types are avaialble for WebReady Document Viewing. This is the default value.
-- 
+
 - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are avaialble for WebReady Document Viewing (you can remove values from the lists).
 
 ```yaml

exchange/exchange-ps/exchange/client-access/Test-CalendarConnectivity.md

@@ -49,6 +49,8 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example:
 
+Test-CalendarConnectivity -ClientAccessServer MBX01 | ConvertTo-Html \> "C:\\My Documents\\Calendar Test.html"
+
 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

exchange/exchange-ps/exchange/client-access/Test-EcpConnectivity.md

@@ -49,6 +49,8 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example:
 
+Test-EcpConnectivity -ClientAccessServer MBX01 | ConvertTo-Html \> "C:\\My Documents\\EAC Test.html"
+
 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

exchange/exchange-ps/exchange/client-access/Test-ImapConnectivity.md

@@ -48,6 +48,8 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example:
 
+Test-IMAPConnectivity -ClientAccessServer MBX01 | ConvertTo-Html \> "C:\\My Documents\\IMAP Test.html"
+
 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).
 
 **Important Note**: In Exchange 2013 or later, when you run this command to test a single mailbox on an Exchange server that isn't hosting the active maildbox database copy for the mailbox, you might see the following error message:

exchange/exchange-ps/exchange/client-access/Test-PopConnectivity.md

@@ -48,6 +48,8 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example:
 
+Test-PopConnectivity -ClientAccessServer MBX01 | ConvertTo-Html \> "C:\\My Documents\\POP Test.html"
+
 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

exchange/exchange-ps/exchange/client-access/Test-PowerShellConnectivity.md

@@ -57,6 +57,8 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example:
 
+Test-PowerShellConnectivity -ClientAccessServer MBX01 | ConvertTo-Html \> "C:\\My Documents\\PowerShell Test.html"
+
 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

exchange/exchange-ps/exchange/client-access/Test-WebServicesConnectivity.md

@@ -66,6 +66,8 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding \> \<filename\> to the command. For example:
 
+Test-WebServicesConnectivity -ClientAccessServer MBX01 | ConvertTo-Html \> "C:\\My Documents\\EWS Test.html"
+
 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

exchange/exchange-ps/exchange/database-availability-groups/Get-MailboxDatabaseCopyStatus.md

@@ -90,7 +90,7 @@ Accept wildcard characters: False
 ```
 
 ### -ConnectionStatus
-The ConnectionStatus switch is obsolete and in the process of being deprecated. Use of this switch will be ignored by the task. The information previously provided by this switch is now provided through an internal caching mechanism and, as such, the switch is no longer needed.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: SwitchParameter

exchange/exchange-ps/exchange/devices/Clear-ActiveSyncDevice.md

@@ -13,7 +13,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service.
 
 Use the Clear-ActiveSyncDevice cmdlet to delete all data from a mobile device.
 
-The Clear-ActiveSyncDevice cmdlet will be removed in a future version of Exchange. Use the Clear-MobileDevice cmdlet instead. If you have any scripts that use the Clear-ActiveSyncDevice cmdlet, update them to use the Clear-MobileDevice cmdlet.
+Note: In Exchange 2013 or later, use the Clear-MobileDevice cmdlet instead. If you have scripts that use Clear-ActiveSyncDevice, update them to use Clear-MobileDevice.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).