Remote PowerShell cmdlet fails in an Exchange Server 2013 environment


Assume that an administrator logs on to a server in a Microsoft Exchange Server 2013 environment and then tries to run a Windows PowerShell cmdlet that requires a proxy to a different back-end mailbox server. (For example, the administrator tries to run set-userphoto.) In this situation, the operation fails, and the administrator receives an error that resembles the following:
Error on proxy command 'Set-Mailbox -Type:'Shared' -Identity: <ID>
-Confirm:$False -Force:$True' to server Exchange_Server: Server version <version number>, Proxy method RPS:
The WinRM client cannot process the request. The connection string should be of the form
[transport://]host[:port][/suffix] where transport is one of "http" or "https". Transport, port and suffix are optional. The host may be a hostname or an IP address. For IPv6 addresses, enclose the address in brackets - e.g. "http://[1::2]:80/wsman". Change the connection string and try the request again.  


This issue occurs because the access token of the current Exchange administrator is so large that it exceeds the connection string length limitation in the Windows Remote Management (WinRM) component. The connection string length limitation is hard-coded to 2,048 bytes.


To work around this issue, use one or more of the following methods. 

Method 1: Install Exchange Server 2013 Cumulative Update 2 or a later cumulative update

With Exchange Server 2013 Cumulative Update 2, a feature was added to compress the access token. However, if the token remains larger than the limitation in WinRM, even after it is compressed, the error continues to occur. In this case, use either method 2 or method 3 to work around the issue.

Method 2: Reduce the number of groups of which the Exchange administrator is a member

Method 3: Create a new Exchange administrator account

Create a new account for Exchange administrative use, and make sure that this account is a member of only the minimum number of required groups.


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

Article ID: 3067263 - Last Review: 13 Jul 2015 - Revision: 1