RPC encryption requirement is re-enabled for RPC Client Access Service after you upgrade server in Exchange Server 2013

Symptoms

Assume that you run the Set-RpcClientAccess cmdlet to set the EncryptionRequired parameter to False. However, when you install a new cumulative update or a service pack for server update that is earlier than Cumulative Update 9, the setting of the encryption requirement switches back to True, and that may cause an outage on Microsoft Outlook in a Microsoft Exchange Server 2013 environment.

Cause

This issue occurs because of a by design logic in the Exchange Server 2013 environment.

Resolution

To resolve this issue, install Cumulative Update 9 for Exchange Server 2013.

Note The setting will not be changed after you install Cumulative Update 9 or a later version update.

Workaround

To work around this issue, run the following cmdlet to manually set the EncryptionRequired parameter to False after the server upgrade:
Set-RpcClientAccess - Server $RoleFqdnOrName -EncryptionRequired $False

Status

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

Article ID: 3068681 - Last Review: Jun 16, 2015 - Revision: 1

Microsoft Exchange Server 2013 Enterprise, Microsoft Exchange Server 2013 Standard Edition

Feedback