How can I fix the error "server did not finish checking the license compliance" on Windows Server 2012 R2?

Ruben Aguiar 0 Reputation points
2024-05-16T18:28:15.18+00:00

After moving my Domain Controller to a Synology NAS, I tested it and all roles seem to be working fine. However, one of my servers running old Windows Server 2012 R2 is giving me an error: "server did not finish checking the license compliance. if the server is joined to a domain, make sure that the server can connect to a domain controller. if the license compliant check cannot be completed, the server will automatically shut down in 7 days 19 hours." How can I fix this error?

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,550 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,418 questions
Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,558 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,460 questions
Windows Server Licensing
Windows Server Licensing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Licensing: Rules, regulations, and restrictions that define how software can be used and distributed.
29 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Q&A Assist
    2024-05-16T18:28:15.1966667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To fix the error "server did not finish checking the license compliance" on Windows Server 2012 R2, you need to ensure that the server can connect to a domain controller. Since you have moved your Domain Controller to a Synology NAS, you need to make sure that the affected server can connect to the new Domain Controller. You can try the following steps:

    1. Check the DNS configuration on the affected server and make sure it is pointing to the correct DNS server, which should be the new Domain Controller.
    2. Verify that the time is correctly synchronized between the affected server and the new Domain Controller.
    3. Check the "Access this computer from the network" user rights on the affected server and make sure that the appropriate users or groups are granted this right.
    4. If the issue persists, you may need to reset the machine account password on the affected server and obtain a new Kerberos ticket.

    Performing these steps should resolve the license compliance error on your Windows Server 2012 R2.


    References:

    0 comments No comments

  2. Hania Lian 10,016 Reputation points Microsoft Vendor
    2024-05-17T01:53:33.8466667+00:00

    Hello,

    This error message indicates that the server is unable to connect to the domain controller to verify its license compliance. To resolve this issue, you can try the following steps:

    1. Check the network connectivity between the server and the domain controller. Ensure that the server can ping the domain controller and vice versa.
    2. Verify that the server is joined to the correct domain and that the domain controller is available and reachable.
    3. Check the DNS settings on the server and ensure that it is pointing to the correct DNS server.
    4. If the issue persists, try removing the server from the domain and rejoining it.

    Best Regards,

    Hania Lian

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.


  3. Ruben Aguiar 0 Reputation points
    2024-05-21T15:10:51.3+00:00

    Hania I have tried following steps:

    1. I can ping the DC with no issues using ping command
    2. Verified and was able to join the domain with no issues.
    3. Check the DNS settings verified. used nslookup
    4. Tried this and it only lengthens the reboot time to another 10 days.

    Best Regards,

    Ruben Aguiar

    0 comments No comments