KB5014754 Certificate based authentication changes on domain controllers

Anonymous
2025-01-31T18:20:25+00:00

I had asked an earlier question on KB 5014754 and received a response that was well thought out and detailed. It certainly helped with defining our next steps to address and accommodate for the changes. So, thank you for that.

Couple of additional follow up questions. I had replied to that earlier post but did not get a response back, so posting again.

  1. My understanding is that KB5014754 is applicable to certificate-based authentication for ADDS on domain controllers only. It does not apply to any other server roles, unless they have ADDS.  Would appreciate a confirmation of that understanding please.

2. In our small environment of less than 100 users, we have one RDS server.  The RDS server was built using server 2019. Certificate was implemented as part of the RDS server build, I did not install a certificate on that server. Certificate is not configured correctly and not trusted. Users get a notification that they then bypass to complete authentication (password based). The RDS server is not internet facing and is behind a firewall. Users connect using a secure VPN tunnel (a) if I leave the certificate as-is, does KB5014754 changes have any impact? (b) Can I safely delete the invalid certificate to remove the warning message received by users during authentication? (c) Anything else we need to be aware of regarding certificate on RDS server in conjunction with KB 5014754. TIA

Windows Server Identity and access Certificates and public key infrastructure (PKI)

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Anonymous
    2025-02-03T11:25:26+00:00

    Hello quark25IS,

    Thank you for posting in Microsoft Community forum.

    1. My understanding is that KB5014754 is applicable to certificate-based authentication for ADDS on domain controllers only. It does not apply to any other server roles, unless they have ADDS.  Would appreciate a confirmation of that understanding please.

    A1:KB5014754, which pertains to changes in how certificates are handled for certificate-based authentication in Active Directory Domain Services (AD DS), specifically targets domain controllers. Your understanding that it applies only to certificate-based authentication for AD DS on domain controllers is correct. It does not directly affect other server roles unless those roles are also functioning as domain controllers. To summarize: - KB5014754 is primarily concerned with domain controllers in an AD DS environment. - Other server roles without AD DS should not be directly impacted by this update.

    2. In our small environment of less than 100 users, we have one RDS server.  The RDS server was built using server 2019. Certificate was implemented as part of the RDS server build, I did not install a certificate on that server. Certificate is not configured correctly and not trusted. Users get a notification that they then bypass to complete authentication (password based). The RDS server is not internet facing and is behind a firewall. Users connect using a secure VPN tunnel (a) if I leave the certificate as-is, does KB5014754 changes have any impact? (b) Can I safely delete the invalid certificate to remove the warning message received by users during authentication? (c) Anything else we need to be aware of regarding certificate on RDS server in conjunction with KB 5014754.

    A2:(a) Impact of KB5014754 on your RDS server:

    Since KB5014754 primarily focuses on certificate-based authentication for domain controllers, it should not have a direct impact on your RDS server, especially if it is not being used for certificate-based authentication to an Active Directory domain controller. Since users are currently bypassing the certificate warning and authenticating using passwords, the update should not affect their ability to continue doing so.

    (b) Deleting the invalid certificate:

    If the certificate on your RDS server is not correctly configured and not trusted, and users are bypassing this warning, you may choose to delete the invalid certificate to remove the warning message. However, before doing so, ensure that:

    The RDS server doesn't require the certificate for any other critical functionality.

    No other applications or services depend on the certificate for secure communication.

    Deleting the certificate won't impact KB5014754 since it doesn't pertain to your RDS server in this context.

    (c) Other considerations regarding certificate on RDS server in conjunction with KB5014754:

    Ensure that your RDS server is not being used for any role that involves certificate-based authentication with a domain controller. Verify that other protocols or services on the RDS server do not rely on the non-trusted certificate for secure communication or other critical operations. Make sure you have a backup or recovery plan before making changes to the server configuration or certificates.

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    0 comments No comments
  2. Anonymous
    2025-02-03T16:43:25+00:00

    Hi Daisy, thank you for the response.

    the only server role that I'm aware of which implications for certificate-based authentication is Active Directory Certificate Services (AD CS). I have confirmed that ADCS role has not been added to any of my servers in my environment (including domain controllers). Is there any other role on RDS that I need to investigate that may require certificate-based authentication with domain controller?

    Thank you,

    0 comments No comments
  3. Anonymous
    2025-02-04T06:34:57+00:00

    Hello

    Greetings!

    If you do not install ADCS on any Windows server in your environment, and you do not use/install any certificate issued by any third-party certification authority on any Windows server in your environment, it seems you do not have certificate-based authentication on Windows domain controllers.

    Best Regards,
    Daisy Zhou

    0 comments No comments
  4. Anonymous
    2025-02-04T19:08:46+00:00

    Thank you.

    0 comments No comments