Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1
Topic Last Modified: 2007-08-21

Use the Get-ClusteredMailboxServerStatus cmdlet to view the status of a specified Microsoft Exchange Server 2007 clustered mailbox server and to get basic operational status about the computers that can host it.

Syntax

Get-ClusteredMailboxServerStatus [-Identity <ServerIdParameter>] [-DomainController <Fqdn>]

Parameters

Parameter Required Type Description

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

To specify the FQDN of the domain controller that writes this configuration change to the Active Directory directory service, include the DomainController parameter in the command.

Identity

Optional

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

The Identity parameter takes one of the following values:

  • GUID

  • Domain name

  • Name of storage group

Detailed Description

Microsoft Exchange Server 2007 Service Pack 1 (SP1) adds new functionality to the Get-ClusteredMailboxServerStatus cmdlet. In a cluster continuous replication (CCR) environment, after a dedicated network has been created for log shipping, the Get-ClusteredMailboxServerStatus cmdlet displays information about cluster networks that have been enabled for continuous replication activity. The new output details include:

  • OperationalReplicationHostNames:{Host1,Host2,Host3}

  • FailedReplicationHostNames:{Host4}

  • InUseReplicationHostNames:{Host1,Host2}

Continuous replication is enabled by using the Enable-ContinuousReplicationHostName cmdlet. For more information about this cmdlet, see Enable-ContinuousReplicationHostName.

The following preconditions must be met to successfully run the Get-ClusteredMailboxServerStatus cmdlet:

  • The account you use to initiate the task is delegated the Exchange  Server Administrator role and local Administrators group for the target server. For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

  • The clustered mailbox server must exist.

  • The cluster must be formed, and the Cluster service must be running.

  • Communication to the cluster must be available.

An Exchange administrator can retrieve the following information by running the Get-ClusteredMailboxServerStatus cmdlet:

  • Host of the clustered mailbox server (a fully qualified domain name or FQDN).

  • Current status of the clustered mailbox server, as follows:

    • Online   The server is completely online.

    • Partially Online   One or more resources of the server are not online.

    • Online Pending   One or more resources of the server are still coming online.

    • Offline   The server is completely offline.

    • Offline Pending   One or more resources of the server are still going offline.

    • Failed   The server has failed.

  • List of the operational computers in the cluster. An array of FQDNs.

  • List of each offline resource associated with the clustered mailbox server and its state.

For databases, the resource name is either the database GUID or the StorageGroupName\DatabaseName. All other resources use their cluster resource name. The state of the clustered mailbox server will be reported as one of the following:

  • Partially Online   One or more resources of the server are not online.

  • Online Pending   One or more resources of the server are still coming online.

  • Offline   The server is completely offline.

  • Offline Pending   One or more resources of the server are still going offline.

  • Failed   One or more resources have failed.

For information about troubleshooting failed resources, see Troubleshooting High Availability Deployments.

The Get-ClusteredMailboxServerStatus cmdlet is supported remotely using the following methods:

  • All nodes in the cluster hosting the clustered mailbox server.

  • An administrative workstation.

  • Another Exchange server in the organization.

Errors

Error Description

Server <CMSName> is not available. The cluster may be unavailable or a communication problem may exist. This task cannot complete without communicating with the cluster.

The task was unable to connect to the cluster due to a communication issue, or the cluster is not available.

This error may occur because the node is unavailable, or the node is available and the cluster is unavailable, or due to a general communication failure.

Get-ClusteredMailboxServerStatus is unable to get clustered mailbox server status because this task is only supported on servers running Exchange 2007 Server. <ServerName> is not running Exchange 2007 Server.

This task supports Exchange 2007 only and <ServerName> is not an Exchange 2007 server.

Access denied. The account used to run this task does not have sufficient privileges to get clustered mailbox server status from <ServerName>. Please use an account that has been assigned the Exchange Server Administrator role.

User does not have Exchange Server Administrator authority.

The operation could not be performed because <CMSName> could not be found on <DCFullName>. <CMSName> is a standalone mailbox server. This task will only work when executed against a clustered mailbox server.

The server is a stand-alone Mailbox server.

The operation could not be performed because <CMSName> could not be found on <DCFullName>. Get-ClusteredMailboxServerStatus was unable to get clustered mailbox server status because the specified server does not exist.

Unable to get clustered mailbox server status because the specified server does not exist. Specified server: <ServerName>.

Server <CMSName> is not a clustered mailbox server. This task will only work when executed against a clustered mailbox server.

The specified server was not a clustered mailbox server.

No default Clustered Mailbox Server could be determined for <NodeName>. This task requires a Clustered Mailbox Server identity to be specified.

Identity was omitted, and a clustered mailbox server could not be implied.

The Identity parameter was omitted (defaulted) and no single clustered mailbox server can be selected. Use the Identity parameter to specify the Clustered Mailbox Server.

Identity was omitted, and a clustered mailbox server could not be implied because there is no started clustered mailbox server and there are multiple stopped clustered mailbox servers present on this node.

The Mailbox role is not configured on node <Node>.

The Mailbox server role is not installed on this node.

Example

In the following example, the Get-ClusteredMailboxServerStatus cmdlet is used to view the status of a clustered mailbox server named CMS1.

Copy Code 
Get-ClusteredMailboxServerStatus -Identity:CMS1

The following displays the output obtained from running the Get-ClusteredMailboxServerStatus cmdlet as shown in the previous code sample:

Get-ClusteredMailboxServerStatus -Identity:CMS1

Identity: CMS1,66ece5af-1c91-421e-a460-a0c864d38968

ClusteredMailboxServerName : CMS1.contoso.com

State: Partially Online

OperationalMachines: {CMS-Node1 <Active>, CMS-Node2}

FailedResources: {<Second Storage Group>/<Public Folder Database> -- Offline}

IsValid: True

ObjectState : Unchanged