Hi Folks,
I am not even sure is this fully supported by Microsoft . I am doing POC for this one. Sharing with the rest of you of what I have out found also to spare you some time of troubleshooting.
1. Adding 2016 node must be done in Windows 2016 Failover clustering manager. Failing to do so cause the cluster to go offline.
2.In mixed mode ironically, configuring the file server role in Windows 2016 Failover clustering manager will not work . I need to do it in Windows 2012 node for it to work.
3. At this point everything seems ok. Both Cluster and Client Access Point are up.
4. Problem arises when I want that 2016 node to take ownership of the File server role (need to do this as I want to evict 2012 node one by one). The File server role immediately gone down when I do this.
Troubleshooting steps taken:
1. Delete the Virtual name computer object and create the new one.
Any help and tips will be appreciated. Thank you.