Hey everyone! We're working with a 4-node Hyper-V cluster connected to a Lenovo DE2000H with SSDs, and we're planning to migrate to a new Active Directory domain. The goal is to set up two new domain controllers in a management VLAN and gradually transition the Hyper-V servers one by one. As we do this, we need to move the VMs from the old Failover Cluster Manager to the new one. We're considering creating a temporary VLAN between the old and new domains to facilitate this process. My main question is whether I can use the same iSCSI volume that's currently attached to the production cluster and connect it to the new domain as well. If so, can I simply remove the VM from the old cluster manager and add it to the new one by referencing the correct .vhdx files? Or will I need to set up a separate volume and transfer each VM folder with the .vhdx files individually? I appreciate any insights you can provide!
1 Answer
You definitely need to plan this carefully. When migrating domains, especially with a Hyper-V setup, it's crucial to ensure that your storage access permissions are properly configured on the new domain. Regarding your question, it might be risky to just plug in the iSCSI volume to the new domain without taking precautions first. You may need a clean setup so that all the permissions and paths are recognized correctly in the new environment. It would probably be safer to create a separate volume initially, then migrate each VM folder properly. That way, you avoid any potential conflicts with existing permissions.
Yeah, I think it's better to be cautious. Setting up a new volume sounds like a solid plan to keep things smooth during the transition.