This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 21%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EET%3C/text%3E%3C/svg%3E)
Seems like this bug or issue has been around for a decade or more - I've tried setting the reserve to 0 instead of 1 failed node out of 3 already with the same error.
Warning (13926)
Host cluster cluster.fqdn was not fully refreshed because not all of the nodes could be contacted. Highly available storage and virtual switch information reported for this cluster might be inaccurate.
All of the nodes I can right-click and view the "status" with all green checkmarks. Each node I can access the hardware tab and see all the CPU/RAM/Storage areas without problems and it's all correct and pulling all the information from the cluster. It's obviously speaking to the cluster, and it IS pulling accurate information. But none of my VMs show up, the cluster does not refresh - always get this same error (Warning 13926), and trying to refresh my VMs immediately fails with this error:
Error (10683)
Unable to contact the cluster service on the host computer (NODE1.FQDN).
Obviously, the cluster is working - passes validation in the normal Failover cluster manager on each node - and I am not having any issues with the cluster at all - I just wanted to fully integrate this new cluster into SCVMM and start learning more and enjoying the benefits of SCVMM since we have licenses for it.
Anyone have any ideas I can try here?
Just for everyone's glee in the future - apparently, MS dropped the ball and SCVMM 2019 does not allow/support hyper-v 2022.
Upgraded SCVMM to 2022 and now my 2022 cluster can be added to SCVMM without erroneous errors.