Applies to: Exchange Server 2007
Topic Last Modified: 2007-08-29

This topic explains how the use the Stop-ClusteredMailboxServer cmdlet to stop a Microsoft Exchange Server 2007 clustered mailbox server without activating it on a passive node in the cluster.

Syntax

stop-ClusteredMailboxServer -Identity <MailboxServerIdParameter> -StopReason <String> [-DomainController <Fqdn>]

Parameters

Parameter Required Type Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.MailboxServerIdParameter

The Identity parameter specifies the name or GUID of the clustered mailbox server to be started. This parameter can be omitted when it is run on the computer with the Mailbox server to be started.

StopReason

Required

System.String

The StopReason parameter must be specified to identify the reason that the stop command is being issued.

Confirm

Optional

Boolean

The Confirm parameter causes the command to pause processing and requires the administrator to acknowledge what the command will do before processing continues. The default value is $true.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

To specify the fully qualified domain name (FQDN) of the domain controller to locate the clustered mailbox server, include the DomainController parameter in the command.

WhatIf

Optional

Boolean

The WhatIf parameter instructs the command to simulate the actions that it would take on the object. By using the WhatIf parameter, the administrator can view what changes would occur without having to apply any of those changes. The default value is $true.

Detailed Description

An Exchange administrator may occasionally need to start or stop a clustered mailbox server due to issues such as a facility failure in the datacenter or another serious issue. In this case, the administrator does not want to activate a passive server (such as with the Move-ClusteredMailboxServer cmdlet) but rather shut down all clustered mailbox server operations. The Stop-ClusteredMailboxServer cmdlet allows the Exchange administrator to shut down the server in a clean state and leave it shut down. Unlike the Move-ClusteredMailboxServer cmdlet or an automatic failover, after issuing a Stop-ClusteredMailboxServer command, a restart of the operating system will not result in bringing Exchange back online. To activate the server after issuing a Stop-ClusteredMailboxServer command, the administrator must issue an explicit Start-ClusteredMailboxServer command.

Note:
The administrator must provide a reason with the stop task to record why the server was taken offline. This reason is placed in the event log.

To successfully initiate a Stop-ClusteredMailboxServer operation, the following conditions must be met:

  • A clustered mailbox server must be running (online or partially online).

  • The cluster must be operational and accessible.

  • The specified clustered mailbox server must exist.

  • The specified clustered mailbox server must not be in transition between nodes at the time the operation is initiated.

This cmdlet can be run from an administrative workstation.

To run the Stop-ClusteredMailboxServer cmdlet, the account you use must be 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 Microsoft Exchange Server 2007, see Permission Considerations.

To learn more about the Start-ClusteredMailboxServer cmdlet, see Start-ClusteredMailboxServer (RTM).

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.

Stop-ClusteredMailboxServer is unable to stop the specified clustered mailbox server because this task is only supported on servers running Exchange 2007 Server. <ServerName> is not running Exchange 2007 Server.

Unable to perform the requested action on the specified clustered mailbox server because this task is only supported on servers running Exchange 2007. <ServerName> is not running Exchange 2007.

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 Admin role.

The 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 specified server is a stand-alone Mailbox server.

The operation could not be performed because '<CMSName>' could not be found on <DCFullName>. Stop-ClusteredMailboxServer was unable to stop the specified clustered mailbox server status because the specified server does not exist.

Unable to perform the requested operation on the specified clustered mailbox server because the 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.

Unable to perform the requested operation on the specified clustered mailbox server because the specified server is not a clustered mailbox server. Specified server: <ServerName>.

The specified clustered mailbox server failed to stop or only partially stopped.

The clustered mailbox server <ServerName> failed to stop. <ServerName> is only partially stopped.

Example

The following code example shows how to stop the Mailbox server named MailboxServer1 because of a datacenter power outage.

Copy Code 
Stop-ClusteredMailboxServer -Identity:MailboxServer1 -StopReason:"DataCenter Power Outage"