New to Failover clustering in Microsoft so this may be a fairly basic question.
2 nodes in a failover cluster running Windows server 2016 and for some reason the CNO is not in ADUC (don't know whether it was ever there or whether it has been deleted as I did not build this cluster). Live migrations were failing so I built a test lab, replicated the exact problem and tried two different things -
1) created an entry in ADUC in the computers group and then within FCM took the cluster server name offline, ran a repair and then brought it back online which allowed live migrations to work but in Server Manager -> All Servers it is still complaining about not being able to find the CNO (kerberos authentication error reported) and if I try to add it manually using "Add Servers" it cannot find the CNO in AD.
I suspect this is because when the entry is created automatically when setting up a new failover cluster there is more going on than what I did by simply adding an entry manually.
2) destroyed the cluster and recreated it which resulted in everything working correctly ie. not just live migrations but also the CNO is now displayed as online in Server Manager -> All Servers etc and the CNO entry was created automatically in ADUC computer group.
So my question is do I have to rebuild the cluster to avoid any future problems ie. if I do option 1) I can do live migrations but the fact that I am still getting errors in Server Manager and the CNO is not online makes me think I may face other issues further down the line.
Is there a way to go with option 1 and resolve all the issues ?
If not and rebuilding the cluster is the best thing to do are there any gotcha's I should look out for (my test lab rebuild went fine but the production setup is a lot more complicated).
Many thanks for any pointers.
2 nodes in a failover cluster running Windows server 2016 and for some reason the CNO is not in ADUC (don't know whether it was ever there or whether it has been deleted as I did not build this cluster). Live migrations were failing so I built a test lab, replicated the exact problem and tried two different things -
1) created an entry in ADUC in the computers group and then within FCM took the cluster server name offline, ran a repair and then brought it back online which allowed live migrations to work but in Server Manager -> All Servers it is still complaining about not being able to find the CNO (kerberos authentication error reported) and if I try to add it manually using "Add Servers" it cannot find the CNO in AD.
I suspect this is because when the entry is created automatically when setting up a new failover cluster there is more going on than what I did by simply adding an entry manually.
2) destroyed the cluster and recreated it which resulted in everything working correctly ie. not just live migrations but also the CNO is now displayed as online in Server Manager -> All Servers etc and the CNO entry was created automatically in ADUC computer group.
So my question is do I have to rebuild the cluster to avoid any future problems ie. if I do option 1) I can do live migrations but the fact that I am still getting errors in Server Manager and the CNO is not online makes me think I may face other issues further down the line.
Is there a way to go with option 1 and resolve all the issues ?
If not and rebuilding the cluster is the best thing to do are there any gotcha's I should look out for (my test lab rebuild went fine but the production setup is a lot more complicated).
Many thanks for any pointers.