Hello Seraphina Kingsley,
The failure of certificate deployment via Group Policy on Windows 11 clients usually points to changes in how the OS handles authentication and secure channel communication rather than a broken GPO itself. Windows 11 enforces hardened defaults around NTLM, RPC, and Kerberos, and if your legacy environment still relies on NTLM fallback or older cryptographic providers, the certificate auto‑enrollment can silently fail. The first diagnostic step is to check the Event Viewer → Applications and Services Logs → Microsoft → Windows → CertificateServicesClient‑AutoEnrollment on a Windows 11 client, which will show explicit error codes if enrollment is blocked. You should also review the gpresult /h report.html output to confirm that the GPO is being applied and that the client has the correct permissions on the certificate template in ADCS.
If no errors appear in GPO processing, the next place to look is the secure channel logs under System → Netlogon and Security → Kerberos events, since Windows 11 may reject weak encryption types or unsigned LDAP binds that older servers still allow. In some cases, enabling modern template compatibility (Key Storage Provider instead of legacy CSP) resolves the issue. If you confirm that the GPO is applied but enrollment fails, it is almost always due to deprecated authentication protocols or template misconfiguration that doesn’t meet Windows 11’s stricter defaults.
If my answer is useful for you, please hit Accept the answer to support me.
Thank you so much!!
QQ.