Share via

Start-ClusteredMailboxServer

  • Article

 

Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

This topic explains how to use the Start-ClusteredMailboxServer cmdlet to start a Microsoft Exchange Server 2007 clustered mailbox server after it was shut down with a Stop-ClusteredMailboxServer cmdlet or to restart a failed clustered mailbox server after the problem has been corrected.

Syntax

start-ClusteredMailboxServer -Identity <MailboxServerIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

Detailed Description

An Exchange administrator may occasionally need to start or stop a clustered mailbox server due to issues such as installing an Exchange software update or a facility failure in the datacenter. In this case, the administrator does not want to activate a passive server by using 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 bring Exchange back online. To activate the server after issuing a Stop-ClusteredMailboxServer command, the administrator must issue an explicit Start-ClusteredMailboxServer command.

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

  • A clustered mailbox server must not be running on a node.

  • The cluster must be formed and accessible.

  • The data for the clustered mailbox server must be available and operational.

    Important

    The completion of the Start-ClusteredMailboxServer operation does not mean that all mailbox functionality for the server is online. The administrator must review the information contained in the completion report to determine if the server came online completely or only partially. This task does not complete until a terminal state is reached for the server. That terminal state may or may not be online.

The Start-ClusteredMailboxServer cmdlet can be run remotely from an administrative workstation.

To learn more about the Stop-ClusteredMailboxServer cmdlet, see Stop-ClusteredMailboxServer.

This task requires that 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 Server 2007, see Permission Considerations.

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.

Confirm

Optional

System.Management.Automation.SwitchParameter

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 of the domain controller to locate the CMS include the DomainController parameter on the command.

WhatIf

Optional

System.Management.Automation.SwitchParameter

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 $false.

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 may be because the node is unavailable, or the node is available and the cluster is unavailable, or because the computer being used cannot access a node or computer.

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

The Start-ClusteredMailboxServer command is supported on 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 Admin role.

User does not have Exchange Server Administrator authority on the specified server.

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>. Start-ClusteredMailboxServer was unable to start the specified clustered mailbox server 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>.

Example

The following code example shows how to start the Mailbox server named ClusteredMailboxServer1.

Start-ClusteredMailboxServer -Identity:ClusteredMailboxServer1