Hyper-V failover cluster attempts to prime kdc cache to decommissioned primary domain controller


  • Hello, I have a small issue on a Hyper-V failover cluster.

    When live migrating a virtual machine there is a noticeable delay that was not there before. When analysing the clusterlog it appears that there is a remaining record pointing to the old PDC: INFO  [RES] Network Name: [NNLIB] Priming local KDC cache to \\ for domain label domain01 . DC03 however has been correctly demoted and removed from the cluster completely. There are also no DNS records remaining that point to DC03.

    Can somebody please tell me if I'm missing something or where the clusternodes could be getting the record pointing to the decommissioned primary domain controller? The new primary domain controller is working like it should, everything else is happy except the "local kdc cache" it seems yet this does not prevent the live migration, it just delays it.

    Thanks in advance!

    Friday, February 17, 2017 7:12 PM

All replies

  • Hi Sir,

    Have you removed SRV records of that old DC ?

    Have you restarted the cluster ?

    Best Regards,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, February 20, 2017 9:08 AM