Diadema
Junior Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору Symptoms When a service such as Exchange server tries to reestablish the Kerberos client session during a cluster failover, it may cause the system to become unresponsive. Additionally, an LSASS CPU spike occurs after the failover. Resolution Microsoft Windows has released a fix that contains new opt-in behavior for the Kerberos client to address this issue. By enabling the Kerberos parameter, the Kerberos client can bypass the CPU intensive action of purging compounded tickets. Note The Kerberos client must opt-in for the new behavior. Follow these steps to create the registry parameter on each node of the cluster: 1.In Registry Editor, locate and then select the following subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters 2.Right-click Parameters, point to New, and then click DWORD Value. 3.Type AllowStaleDeviceAuthzData as the entry name, and then press Enter. 4.Right-click AllowStaleDeviceAuthzData, and then click Modify. 5.In the Value data box, type 1, and then click OK. https://support.microsoft.com/en-us/help/3172614/july-2016-update-rollup-for-windows-8.1-and-windows-server-2012-r2 | Всего записей: 185 | Зарегистр. 17-01-2006 | Отправлено: 12:52 23-10-2006 | Исправлено: dimonprodigy, 07:19 24-06-2017 |
|