大网数据广告活动
故障转移群集

Cluster service doesn't start after you apply CIS Windows Server 2025 Benchmark v1.x recommendations

· 52CE 我爱测

Discusses how to resolve an issue in which the Windows Failover Cluster service fails to start after you apply security hardening recommendations.

Summary

This article discusses how to resolve an issue in which the Windows Failover Cluster service doesn't start in a Windows Server 2025 failover cluster after you apply security hardening recommendations from the Center for Internet Security (CIS) or similar security sources. CIS has published updated recommendations that don't cause this issue, and this article includes procedures for reconfiguring the policy setting that caused the issue.

Symptoms

To harden your clustering environment, you configure it according to the recommendations of "CIS Microsoft Windows Server 2025 Benchmark version 1.x", or similar hardening tools. Afterward, the Windows Failover Cluster service doesn't start. Cluster nodes might report errors that indicate that the Cluster Authentication Manager (CAM) can't load.

Cause

CIS Microsoft Windows Server 2025 Benchmark v1.x recommends that you disable the following Group Policy setting in the LocalSecurityAuthority administrative template:

  • Policy setting: Allow Custom SSPs and APs to be loaded into LSASS
  • Policy location: Computer Configuration > Administrative Templates > System > Local Security Authority
  • Registry storage location and entry: HKLM\SOFTWARE\Policies\Microsoft\Windows\System\AllowCustomSSPsAPs

If this setting is disabled, Local Security Authority Subsystem Service (LSASS) can't load custom Security Support Providers (SSPs) and Authentication Providers (APs). However, the CAM functions as an SSP. If the CAM can't load into LSASS, Windows clusters can't authenticate and start.

Custom or third-party hardening tools might also include this Group Policy recommendation.

Resolution

"CIS Microsoft Windows Server 2025 Benchmark v2.0" fixes this issue by scoping the recommendation to domain controllers (DCs) but not member servers. To harden your environment, use "CIS Microsoft Windows Server 2025 Benchmark v2.0" or similarly updated standards or tools.

If you already implemented the v1.x recommendations, use one of the following methods to restore cluster functionality.

Method 1: Change the policy setting directly on a cluster node

  1. Open the Local Group Policy Editor (gpedit.msc).
  2. In the policy editor, locate Computer Configuration > Administrative Templates > System > Local Security Authority.
  3. Right-click Allow Custom SSPs and APs to be loaded into LSASS, and then select Edit.
  4. Select Enabled, and then select OK.
  5. Restart the Cluster service on the node.

Method 2: Change the policy setting at the domain or forest level

  1. Open the Group Policy Management Console (GPMC) on a DC.
  2. Right-click the Group Policy Object (GPO) that controls Allow Custom SSPs and APs to be loaded into LSASS on cluster nodes, and then select Edit.
  3. In the policy editor, locate Computer Configuration > Administrative Templates > System > Local Security Authority.
  4. Right-click Allow Custom SSPs and APs to be loaded into LSASS, and then select Edit.
  5. Select Enabled, and then select OK.
  6. To propagate the updated policy, run gpupdate /force on the affected nodes
  7. To start the affected nodes, run a command such as the Windows PowerShell Start-Cluster cmdlet or Start-ClusterNode cmdlet.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 04/22/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。