The server manager refresh icon is giving error after I removed cluster members from Hyper-V cluster

Question

I have total 5 nodes in my Hyper-V Windows Server 2012 R2 cluster. I am migrating everything to Windows Server 2019. Per MS recommendation, the mixed mode path would be 2012 r2 -->2016-->2019. I have added my Win 2016 server successfully in Win 2012 r2 cluster and migrated the VM. Now I removed my Win 2012 R2 nodes from cluster. But when I login to my Win 2016 server (cluster members), they are giving refresh error as show in below image and detail is as below.

Answer 1

I have already removed old Windows Server 2012 R2 Hyper-V nodes from cluster membership but still that refresh error is coming on new servers. Everytime, I open server mgr on Win 2016 Hyper-V server, it tries to connect with Win 2012 r2 nodes which have been removed. Not sure why?

I suspect even though Win 2012 r2 nodes are removed from cluster but somewhere, their entry remaining in new nodes. If someone can guide me, pls.

Answer 2

Hi,

As per to the error messages in the picture, WInRM is not working properly. Open Windows PowerShell as administrator from the start menu and run Enable-PSRemoting to enable WinRM.

Follow the steps in below link to create firewall rules to allow the RPC traffic.

https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/create-inbound-rules-to-support-rpc

Best Regards,

Ian Xue

---

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

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

After migration, I had turn off the old nodes. Whenever I will power on those old nodes, they will be registered in Manageability and then my new servers will try to connect those servers and when I power off the old servers, connectivity between old and new nodes will fail via WinRIM service. So, either you can ignore this error or decommission the old nodes and then finally remove it from Server Manager-->Manageability list.