Export (0) Print
Expand All
Related Help Topics
Loading
No resources found.
Related Blog Articles
Loading
No resources found.
Expand Minimize
This topic has not yet been rated - Rate this topic

Test-CalendarConnectivity

Exchange 2010
 

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2012-11-15

Use the Test-CalendarConnectivity cmdlet to verify that anonymous calendar sharing is enabled and working properly. The Calendar virtual directory is a subdirectory of the Microsoft Office Outlook Web App virtual directory. When you run this command without any parameters, the command tests against all Outlook Web App calendar virtual directories.


Test-CalendarConnectivity [-ClientAccessServer <ServerIdParameter>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-LightMode <SwitchParameter>] [-MailboxServer <ServerIdParameter>] [-MonitoringContext <SwitchParameter>] [-ResetTestAccountCredentials <SwitchParameter>] [-TestType <Internal | External>] [-Timeout <UInt32>] [-TrustAnySSLCertificate <SwitchParameter>] [-VirtualDirectoryName <String>] [-WhatIf [<SwitchParameter>]]

To test virtual directories on a Client Access server, there must be a test Active Directory account. There must also be a test mailbox in each Active Directory site that hosts mailboxes that can be accessed through the virtual directories being tested. You can create the test account by running the New-TestCasConnectivityUser.ps1 script. The default location for this file is: \\Program Files\Microsoft\Exchange Server\V14\Scripts.

If the test environment wasn't created during the Mailbox server setup, you're prompted to run the script that creates the test mailboxes and test users when you run this command.

If the server hosting the test mailbox isn't available, the command returns an error that might not clearly identify the problem. To avoid this, use the Test-MAPIConnectivity cmdlet to verify that the server that hosts the test mailbox is running and that the mailbox is available before you run this command.

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 "Outlook Web App virtual directories" entry in the Client Access Permissions topic.

 

Parameter Required Type Description

ClientAccessServer

Optional

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

The ClientAccessServer parameter specifies the name of the Client Access server to test. If this parameter is included, all Outlook Web App calendar virtual directories on the Client Access server are tested against all Exchange Mailbox servers in the local Active Directory site.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.

LightMode

Optional

System.Management.Automation.SwitchParameter

The LightMode parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of the command.

noteNote:
This parameter is implemented for other Exchange diagnostic commands where it's used to run a less intensive version of a command.

MailboxServer

Optional

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

The MailboxServer parameter specifies the name of the Mailbox server to test. If not specified, all Mailbox servers in the local Active Directory site are tested.

MonitoringContext

Optional

System.Management.Automation.SwitchParameter

The MonitoringContext parameter shows you what information is returned to Microsoft System Center Operations Manager 2007. When System Center Operations Manager 2007 executes the Test-CalendarConnectivity cmdlet, it requires additional information to be returned. By setting this parameter to $true, you can see exactly what would be returned to Operations Manager 2007. This parameter is informational only and has no effect on Operations Manager 2007.

ResetTestAccountCredentials

Optional

System.Management.Automation.SwitchParameter

The ResetTestAccountCredentials parameter specifies whether to reset the password for the test account used to run this command. The password for the test account is usually reset every 7 days. Use this parameter to force a password reset any time a password reset is required for security reasons.

TestType

Optional

Microsoft.Exchange.Monitoring.OwaConnectivityTestType

The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. If you don't specify this parameter, the default is TestType:Internal.

Timeout

Optional

System.UInt32

The TimeOut parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of the command.

noteNote:
This parameter is implemented for other Exchange diagnostic commands where it's used to run a less intensive version of a command.

TrustAnySSLCertificate

Optional

System.Management.Automation.SwitchParameter

The TrustAnySSLCertificate parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of the command.

noteNote:
This parameter is implemented for other Exchange diagnostic commands where it's used to run a less intensive version of a command.

VirtualDirectoryName

Optional

System.String

The VirtualDirectoryName parameter specifies the name of the virtual directory to test on a particular Client Access server. If this parameter isn't included, all Outlook Web App calendar virtual directories that support calendar sharing are tested.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

This example tests the connectivity for the Client Access server CAS01.

Test-CalendarConnectivity -ClientAccessServer CAS01
 © 2010 Microsoft Corporation. All rights reserved.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.