The Connect-ExchangeServer function does not change the target Exchange server in Exchange Server 2010

View products that this article applies to.

Symptoms

In a Microsoft Exchange Server 2010 environment, the Exchange Management Shell (EMS) still connects to the initial Exchange server. This issue occurs after you changed the target Exchange server in the EMS by using the Connect-ExchangeServer function.

Note You can trace network traffic to determine whether the EMS still connects to the initial Exchange server.

↑ Back to the top

Cause

This issue occurs because you cannot ensure commands to run in the new EMS session even if the Connect-ExchangeServer function creates a new EMS session to the target Exchange server. Therefore, some commands still run in the initial EMS session.

↑ Back to the top

Resolution

To resolve this issue, install the following update rollup:

2579150 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 1

Note This update introduces an -AllowClobber switch to the Connect-ExchangeServer function. The EMS connects to the new target Exchange server successfully by using this switch.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Workaround

To work around the issue, open the EMS by running a full command-line every time. The following is an example of a full command-line.

Open a command prompt, and type the following command:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command ". 'C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1'; Connect-ExchangeServer <target server>"

Note<target server> is the placeholder for the name of the target server.

↑ Back to the top