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/Test-WebServicesConnectivity.md
+3-198Lines changed: 3 additions & 198 deletions
Original file line number
Diff line number
Diff line change
@@ -6,20 +6,6 @@ schema: 2.0.0
6
6
# Test-WebServicesConnectivity
7
7
8
8
## SYNOPSIS
9
-
!!! Exchange Server 2010
10
-
11
-
Use the Test-WebServicesConnectivity cmdlet to perform basic operations to verify the functionality of Exchange Web Services on a server running Microsoft Exchange Server 2010 that has the Client Access server role installed.
12
-
13
-
!!! Exchange Server 2013
14
-
15
-
This cmdlet is available only in on-premises Exchange.
16
-
17
-
Use the Test-WebServicesConnectivity cmdlet to perform basic operations to verify the functionality of Exchange Web Services on a server running Microsoft Exchange Server 2013.
18
-
19
-
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
20
-
21
-
!!! Exchange Server 2016
22
-
23
9
This cmdlet is available only in on-premises Exchange.
24
10
25
11
Use the Test-WebServicesConnectivity cmdlet to test client connectivity to Exchange Web Services virtual directories.
The Test-WebServicesConnectivity cmdlet tests the functionality of Exchange Web Services. The Test-WebServicesConnectivity cmdlet performs basic operations to verify the functionality of Outlook Anywhere. The operations tested by default are GetFolder, CreateItem, DeleteItem, and SyncFolderItems. The results of each test are returned by the Exchange Management Shell.
63
-
64
-
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Test Exchange Web Services" entry in the Client Access Permissions topic.
65
-
66
-
!!! Exchange Server 2013
67
-
68
-
To use most of the features of this cmdlet, you need to create a test user by running the following command: & $env:ExchangeInstallPath\\Scripts\\New-TestCasConnectivityUser.ps1
69
-
70
-
The Test-WebServicesConnectivity results are displayed on-screen. The cmdlet returns the following information.
71
-
72
-
- Source Source server.
73
-
74
-
- ServiceEndpoint Destination server.
75
-
76
-
- Scenario The operations that are tested. Values are Autodiscover: SOAP Provider and EWS: GetFolder or EWS: ConvertID.
77
-
78
-
- Result The values returned are typically Success or \*FAILURE\*.
79
-
80
-
- Latency (MS) The time required to complete the test in milliseconds
81
-
82
-
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 CAS01 | ConvertTo-Html \> "C:\\My Documents\\EWS Test.html"
83
-
84
-
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Test Exchange Web Services" entry in the Clients and mobile devices permissions topic.
85
-
86
-
!!! Exchange Server 2016
87
-
88
46
The Test-WebServicesConnectivity cmdlet tests Exchange Web Services connectivity by connecting to a specified Exchange Web Services virtual directory, to any Exchange Web Services virtual directories on a specified Exchange server, or to any Exchange Web Services virtual directories that are available in the local Active Directory site.
89
47
90
48
The first time you use this cmdlet, you might be required to create a test user. To create a test user, run the following command.
@@ -107,25 +65,17 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
107
65
108
66
## EXAMPLES
109
67
110
-
### Example 1 -------------------------- (Exchange Server 2010)
68
+
### Example 1
111
69
```
112
70
Test-WebServicesConnectivity -AllowUnsecureAccess
113
71
```
114
72
115
-
This example tests Exchange Web Services on the local Client Access server and allows the test to use an unsecured connection that doesn't require SSL. A default test account is used.
116
-
117
-
### Example 1 -------------------------- (Exchange Server 2013)
This example tests the connection to Exchange Web Services on the Client Access server named CAS01. The test account that was created by running the New-TestCasConnectivityUser.ps1 script is used.
73
+
In Exchange 2010, this example tests Exchange Web Services on the local Client Access server and allows the test to use an unsecured connection that doesn't require SSL. A default test account is used.
123
74
124
-
### Example 1 -------------------------- (Exchange Server 2016)
The ClientAccessServer parameter specifies the Client Access server to use when the command is run.
153
-
154
-
155
-
156
-
!!! Exchange Server 2013
157
-
158
-
The ClientAccessServer parameter specifies the Client Access server to use when the command is run.
159
-
160
-
You can use any value that uniquely identifies the server. For example:
161
-
162
-
- Name (for example, Exchange01)
163
-
164
-
- Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com)
165
-
166
-
- Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01)
167
-
168
-
- GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942)
169
-
170
-
171
-
172
-
!!! Exchange Server 2016
173
-
174
100
The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections.
175
101
176
102
You can use any value that uniquely identifies the server. For example:
@@ -185,8 +111,6 @@ You can use any value that uniquely identifies the server. For example:
185
111
186
112
You can't use this parameter with the AutoDiscoverServer parameter.
The LightMode parameter instructs the command to perform only a subset of the connectivity tests. When you use this parameter, only the GetFolder operation is tested.
256
-
257
-
258
-
259
-
!!! Exchange Server 2013
260
-
261
-
The LightMode switch instructs the command to perform only a subset of the connectivity tests. When you use this parameter, the EWS: ConvertId operation is tested instead of the EWS: GetFolder operation.
262
-
263
-
264
-
265
-
!!! Exchange Server 2016
266
-
267
177
The LightMode switch tells the command to perform only a subset of the tests. You don't need to specify a value with this switch.
268
178
269
179
When you use this switch, the EWS: ConvertId test is run instead of the EWS: GetFolder test.
The MailboxCredential parameter specifies the mailbox to use when the command is run.
290
-
291
-
292
-
293
-
!!! Exchange Server 2013
294
-
295
-
The MailboxCredential parameter specifies the mailbox credentials to use when the command is run. This parameter is required when you use the Identity parameter.
296
-
297
-
This parameter requires the creation and passing of a credential object. This credential object is created by using the Get-Credential cmdlet. For more information, see Get-Credential (https://go.microsoft.com/fwlink/p/?linkId=142122).
298
-
299
-
300
-
301
-
!!! Exchange Server 2016
302
-
303
195
The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test.
304
196
305
197
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).
306
198
307
199
This parameter is required when you use the Identity parameter.
The MonitoringContext parameter specifies whether the test result is passed to Microsoft System Center Operations Manager 2007. If this parameter is set to $true, the test result is passed to Operations Manager 2007. If this parameter is set to $false, the test result appears only on the command line.
344
-
345
-
346
-
347
-
!!! Exchange Server 2013
348
-
349
-
The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager 2007 or System Center 2012 - Operations Manager.
350
-
351
-
352
-
353
-
!!! Exchange Server 2016
354
-
355
231
The MonitoringContext switch includes the associated monitoring events and performance counters in the results. Typically, you include the monitoring events and performance counters in the results when the output is passed to MicrosoftSystem Center Operations Manager (SCOM). You don't need to specify a value with this switch.
The TrustAnySSLCertificate parameter allows the test to use any SSL certificate available.
421
-
422
-
423
-
424
-
!!! Exchange Server 2013
425
-
426
-
The TrustAnySSLCertificate switch allows the test to use any SSL certificate that's available.
427
-
428
-
429
-
430
-
!!! Exchange Server 2016
431
-
432
292
The TrustAnySSLCertificate switch specifies whether to ignore Secure Sockets Layer (SSL) certificate validation failures. You don't need to specify a value with this switch.
433
293
434
294
This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL.
The AutoDiscoverServer parameter specifies the Client Access server to use to test Autodiscover connectivity.
487
-
488
-
You can use any value that uniquely identifies the server. For example:
489
-
490
-
- Name (for example, Exchange01)
491
-
492
-
- Distinguished name (DN) (for example, CN=Exchange01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com)
493
-
494
-
- Exchange Legacy DN (for example, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange01)
495
-
496
-
- GUID (for example, bc014a0d-1509-4ecc-b569-f077eec54942)
497
-
498
-
499
-
500
-
!!! Exchange Server 2016
501
-
502
342
The AutoDiscoverServer parameter specifies the server with the Client Access server role installed that's used for Autodiscover.
503
343
504
344
You can use any value that uniquely identifies the server. For example:
@@ -513,8 +353,6 @@ You can use any value that uniquely identifies the server. For example:
513
353
514
354
You can't use this parameter with the ClientAccessServer parameter.
0 commit comments