Merge pull request MicrosoftDocs#3143 from MicrosoftDocs/chrisda

Chrisda to Master

Author: chrisda

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

@@ -91,7 +91,6 @@ The Test-OutlookConnectivity cmdlet runs the same process as the monitoring prob
 
 This example lists the probes running in the backend services on a Mailbox server: `Get-MonitoringItemIdentity -Server MailboxServer1 -Identity outlook.protocol | ?{$_.Name -like '*probe'}`.
 
-
 This example lists the probes running in the client access services on a Mailbox server: `Get-MonitoringItemIdentity -Server MailboxServer1 -Identity outlook | ?{$_.Name -like '*probe'}`.
 
 For more information on probes and the monitoring framework, see Managed Availability (https://go.microsoft.com/fwlink/p/?LinkId=510838), Managed Availability and Server Health (https://go.microsoft.com/fwlink/p/?LinkId=510839), and Customizing Managed Availability (https://go.microsoft.com/fwlink/p/?LinkId=510840)
@@ -110,54 +109,39 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ### -------------------------- Example 1 --------------------------
 ```
-Test-OutlookConnectivity -Protocol:HTTP -GetDefaultsFromAutoDiscover:$true
+Test-OutlookConnectivity -ProbeIdentity OutlookMapiHttp.Protocol\OutlookMapiHttpSelfTestProbe
 ```
 
-In Exchange 2010, this example tests the most common end-to-end Outlook connectivity scenario for Outlook Anywhere. This includes testing for connectivity through the Autodiscover service, creating a user profile, and logging on to the user mailbox. All of the required values are retrieved from the Autodiscover service. Because the Identity parameter isn't specified, the command uses the temporary test user that you've created using the New-TestCasConnectivityUser.ps1 script. This example command can be run to test TCP/IP connectivity by setting the Protocol parameter to RPC.
+In Exchange 2013 or later, this example runs an MAPI over HTTP OutlookRpcSelfTestProbe on the Mailbox server that you're currently connected to.
 
 ### -------------------------- Example 2 --------------------------
 ```
-Test-OutlookConnectivity -ProbeIdentity "OutlookRpcSelfTestProbe"
+Test-OutlookConnectivity "Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 1234512345" -RunFromServerId PrimaryMailbox -MailboxId [email protected]
 ```
 
-In Exchange 2013 or later, this example runs an OutlookRpcSelfTestProbe on the mailbox server that you're currently connected to.
+In Exchange 2013 or later, this example runs the OutlookRpcDeepTestProbe from the "PrimaryMailbox" server for the mailbox "[email protected]" mounted on "Mailbox Database 1234512345". Because the Credential parameter is not specified, the probe will use the default testing credentials.
 
 ### -------------------------- Example 3 --------------------------
 ```
-Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server
+Test-OutlookConnectivity -Protocol HTTP -GetDefaultsFromAutoDiscover $true
 ```
 
-In Exchange 2010, this example tests for Outlook Anywhere connectivity using the local server as the RpcProxy endpoint as well as the RPC endpoint. Because the Identity parameter isn't specified, the command uses the temporary test user that you've created using the New-TestCasConnectivityUser.ps1 script. Modify this example to use the public external URL by setting the RpcProxyTestType parameter to External. Additionally, the example command can use the Client Access server array as the RPC endpoint by setting the RpcTestType parameter to Array. To only validate TCP/IP connectivity, omit the RpcProxyTestType parameter.
+In Exchange 2010, this example tests the most common end-to-end Outlook connectivity scenario for Outlook Anywhere. This includes testing for connectivity through the Autodiscover service, creating a user profile, and logging on to the user mailbox. All of the required values are retrieved from the Autodiscover service. Because the Identity parameter isn't specified, the command uses the temporary test user that you've created using the New-TestCasConnectivityUser.ps1 script. This example command can be run to test TCP/IP connectivity by setting the Protocol parameter to RPC.
 
 ### -------------------------- Example 4 --------------------------
 ```
-Test-OutlookConnectivity "OutlookRpcDeepTestProbe\Mailbox Database 1234512345" -RunFromServerId PrimaryMailbox -MailboxId [email protected]
+Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server
 ```
 
-In Exchange 2013 or later, this example runs the OutlookRpcDeepTestProbe from the "PrimaryMailbox" server for the mailbox "[email protected]" mounted on "Mailbox Database 1234512345". Because the Credential parameter is not specified, the probe will use the default testing credentials.
+In Exchange 2010, this example tests for Outlook Anywhere connectivity using the local server as the RpcProxy endpoint as well as the RPC endpoint. Because the Identity parameter isn't specified, the command uses the temporary test user that you've created using the New-TestCasConnectivityUser.ps1 script. Modify this example to use the public external URL by setting the RpcProxyTestType parameter to External. Additionally, the example command can use the Client Access server array as the RPC endpoint by setting the RpcTestType parameter to Array. To only validate TCP/IP connectivity, omit the RpcProxyTestType parameter.
 
 ### -------------------------- Example 5 --------------------------
 ```
-Test-OutlookConnectivity -RpcProxyServer:RpcProxySrv01 -RpcProxyAuthenticationType:Basic -RpcClientAccessServer:CAS01 -RpcAuthenticationType:NTLM
+Test-OutlookConnectivity -RpcProxyServer RpcProxySrv01 -RpcProxyAuthenticationType Basic -RpcClientAccessServer CAS01 -RpcAuthenticationType NTLM
 ```
 
 In Exchange 2010, this example validates Outlook connectivity through RpcProxy on one server to a different server running the Client Access server role with Basic for the outer authentication layer and NTLM for the inner authentication layer. Using these parameters should allow you to validate most types of Outlook connectivity configurations. This command can also be used with the GetDefaultsFromAutoDiscover parameter set to $true if you only need to override one or two parameters. This following command is similar to running a connectivity test using the RPC Ping utility but provides stronger validation.
 
-### -------------------------- Example 6 --------------------------
-```
-$TestCredentials = Get-Credential; 
-Test-OutlookConnectivity -ProbeIdentity OutlookRpcCtpProbe -MailboxId [email protected] -Credential $TestCredentials
-```
-
-In Exchange 2013 or later, this example runs the OutlookRpcCtpProbe and verifies the log-on credentials for the "[email protected]" mailbox.
-
-### -------------------------- Example 7 --------------------------
-```
-Test-OutlookConnectivity -ProbeIdentity "OutlookRpcCTPProbe" -MailboxID [email protected]
-```
-
-In Exchange 2013 or later, this example runs a logon test from the client access services on a Mailbox server for the mailbox [email protected].
-
 ## PARAMETERS
 
 ### -Identity
@@ -214,7 +198,11 @@ Accept wildcard characters: False
 ### -RpcTestType
 This parameter is available or functional only in Exchange Server 2010.
 
-The RpcTestType parameter specifies which type of RPC endpoint the command should test. Valid values are Server or Array. If Server is specified, the command uses the local server as the RPC endpoint. If Array is specified, the command looks for a ClientAccessArray object in the same Active Directory site where the command is being run.
+The RpcTestType parameter specifies which type of RPC endpoint the command should test. Valid values are:
+
+- Server: The command uses the local server as the RPC endpoint.
+
+- Array: The command looks for a ClientAccessArray object in the local Active Directory site.
 
 ```yaml
 Type: Array | Server
@@ -233,14 +221,12 @@ This parameter is available or functional only in Exchange Server 2010.
 
 The WSTestType parameter specifies type of servers that you want to include in your Outlook connectivity test. You can use the following values:
 
-- Unknown
+- Unknown (This is the default value.)
 
 - Internal
 
 - External
 
-- The default value is Unknown.
-
 ```yaml
 Type: Unknown | Internal | External
 Parameter Sets: WSTestType
@@ -256,7 +242,11 @@ Accept wildcard characters: False
 ### -Archive
 This parameter is available or functional only in Exchange Server 2010.
 
-The Archive parameter specifies whether tests should be performed to connect to the user's on-premises archive mailbox. You don't need to specify a value for this parameter.
+The Archive parameter specifies whether tests should be performed to connect to the user's on-premises archive mailbox. Valid values are:
+
+$true: Connect to the user's on-premises archive mailbox.
+
+$false: Don't connect to the user's on-premises mailbox. This is the default value.
 
 ```yaml
 Type: $true | $false
@@ -292,7 +282,9 @@ Accept wildcard characters: False
 ```
 
 ### -Credential
-The Credential parameter specifies the credential used by the probe. The system's test credentials are used by default. This parameter requires you to create a credentials object by using the Get-Credential cmdlet. For more information, see Get-Credential (https://go.microsoft.com/fwlink/p/?linkId=142122).
+The Credential parameter specifies the credential used by the probe. The system's test credentials are used by default
+
+This parameter requires you to create a credentials object by using the Get-Credential cmdlet. For more information, see Get-Credential (https://go.microsoft.com/fwlink/p/?linkId=142122).
 
 ```yaml
 Type: PSCredential
@@ -326,6 +318,8 @@ This parameter is available or functional only in Exchange Server 2010.
 
 The MailboxCredential parameter specifies certain credentials to allow logon access to a user's mailbox. Use the parameter along with the Identity parameter to access a user's mailbox when you don't have access permissions.
 
+This parameter requires you to create a credentials object by using the Get-Credential cmdlet. For more information, see Get-Credential (https://go.microsoft.com/fwlink/p/?linkId=142122).
+
 ```yaml
 Type: PSCredential
 Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType
@@ -356,7 +350,7 @@ Accept wildcard characters: False
 ### -MonitoringContext
 This parameter is available or functional only in Exchange Server 2010.
 
-The MonitoringContext parameter specifies whether the command returns additional information that can be used with Microsoft System Center Operations Manager 2007. The default value is $false.
+The MonitoringContext switch specifies whether the command returns additional information that can be used with Microsoft System Center Operations Manager. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
@@ -371,11 +365,23 @@ Accept wildcard characters: False
 ```
 
 ### -ProbeIdentity
-The ProbeIdentity parameter specifies the probe to use.
+The ProbeIdentity parameter specifies the probe to use. Valid values are:
 
-- RPC over HTTP (Outlook Anywhere) probes
+Outlook Anywhere (RPC over HTTP) probes:
 
-- MAPI over HTTP probes
+- Outlook.Protocol\OutlookRpcSelfTestProbe: Validates that the RPC/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity.
+
+- Outlook.Protocol\OutlookRpcDeepTestProbe: Validates that the RPC/HTTP endpoint is working on the Mailbox server. It will attempt to connect to and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet.
+
+- Outlook.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>: Validates that the RPC/HTTP endpoint is working on the Mailbox Server. It will attempt to connect to and log in to the mailbox in the specified mailbox database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, "Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530").
+
+MAPI over HTTP probes:
+
+- OutlookMapiHttp.Protocol\OutlookMapiHttpSelfTestProbe: Validates that the MAPI/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity.
+
+- OutlookMapiHttp.Protocol\OutlookMapiHttpDeepTestProbe: Validates that the MAPI/HTTP endpoint is working on the Mailbox server. It will attempt to connect and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet.
+
+- OutlookMapiHttp.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>: Validates that the MAPI/HTTP endpoint is working on the Mailbox Server. It will attempt to connect and log in to the mailbox in the specified database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, "Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530").
 
 ```yaml
 Type: String
@@ -468,7 +474,11 @@ Accept wildcard characters: False
 ### -RpcProxyTestType
 This parameter is available or functional only in Exchange Server 2010.
 
-The RpcProxyTestType parameter specifies which HTTP endpoint the command should connect to. The value can be Internal or External. The Internal value refers to the local computer name (http://\<localcomputername\>, for example, http://CAS01). The External value refers to a public namespace (the external HTTP URL on the /rpc virtual directory, for example, http://mail.contoso.com).
+The RpcProxyTestType parameter specifies which HTTP endpoint the command should connect to. Valid values are:
+
+- Internal: Refers to the local computer name (https://\<localcomputername\>, for example, httpS://CAS01). 
+
+- External: Refers to a public namespace (the external HTTP URL on the /rpc virtual directory, for example, https://mail.contoso.com).
 
 ```yaml
 Type: External | Internal
@@ -532,7 +542,7 @@ Accept wildcard characters: False
 ### -TrustAnySslCert
 This parameter is available or functional only in Exchange Server 2010.
 
-The TrustAnySslCert parameter can be set to $true to ignore any Secure Sockets Layer (SSL) certificate warnings. The default value is $false.
+The TrustAnySslCert switch specifies whether to ignore any Secure Sockets Layer (SSL) certificate warnings. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter

exchange/exchange-ps/exchange/mailboxes/Remove-Mailbox.md

@@ -99,6 +99,13 @@ $Temp = Get-Mailbox | Where {$_.DisplayName -eq 'John Rodman'}; Remove-Mailbox -
 
 This example removes John Rodman's mailbox from the mailbox database after the mailbox has been disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter.
 
+### -------------------------- Example 4 --------------------------
+```
+Get-Mailbox -Identity Laura -SoftDeleted | Remove-Mailbox -PermanentlyDelete.
+```
+
+In Exchange Online, this example removes the specified soft-deleted mailbox mailbox.
+
 ## PARAMETERS
 
 ### -Identity
@@ -385,12 +392,10 @@ The PermanentlyDelete switch specifies whether to immediately and permanently de
 
 Notes:
 
-- This switch works only on mailboxes that have already been deleted, but are still recoverable (known as soft-deleted mailboxes).
+- This switch works only on mailboxes that have already been deleted, but are still recoverable (known as soft-deleted mailboxes). Use the Get-Mailbox cmdlet to identify the soft-deleted mailbox, and then pipe the results to the Remove-Mailbox cmdlet as shown in Example 3 in this topic.
 
 - This switch doesn't work on soft-deleted mailboxes that are on In-Place Hold or Litigation Hold (known as inactive mailboxes).
 
-Use the Get-Mailbox cmdlet to identify the soft-deleted mailbox, and then pipe the results to the Remove-Mailbox cmdlet with this switch. For example, Get-Mailbox -Identity Laura -SoftDeleted | Remove-Mailbox -PermanentlyDelete.
-
 ```yaml
 Type: SwitchParameter
 Parameter Sets: Default