Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


Cause

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

↑ Back to the top


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.

↑ Back to the top


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

↑ 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


Keywords: kbqfe, kbsurveynew, kbfix, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 3068681
Revision : 1
Created on : 1/7/2017
Published on : 6/16/2015
Exists online : False
Views : 288