Sounds like we have a lot of windows folks here. I was following recommendations in Patrick's thread and trying to build-out a Windows lab.
Machine 1
Memory 32GB
Drives 32GB boot SSD, 4TB Seagate NAS, 240GB scratch
Machine 2
Memory 32GB
Drives 32GB boot SSD, 2TB WD, 240GB scratch
Here is what I have done so far:
1. Installed Hyper-V on Machine 1's 32GB SSD
2. Made a share on the 32GB SSD (used Server manager)
3. Made a VM sitting in the shared folder and installed Windows Server 2012 Std
4. Added domain controller on 2012 Std VM
5. Made a domain test.local
6. Made a user called HyperV test.local
When I tried to join the Hyper-V server to test.local using test\HyperV it said it could not reach the DC. I can troubleshoot this but it isn't done yet.
Next I want to do the following:
1n. Install Hyper-V on the second machine
2n. Make a second domain controller on the second machine
3n. Somehow make a shared pool using the (2) 240GB ssd and (2) hard drives
4n. Get both the DCs VMs on that shared pool
5n. Start adding VMs on the shared pool
My question is really twofold:
a) Is 3n doable? What should I be googling to research how to make a cluster/share pool across machines?
b) I'm thinking whatever I do in a) and 3n I need to be doing on the Hyper-V servers right? Or should I pass the disks through to another VM? I am saying this since IF the Hyper-V host gets powered down, if I did a pass-through a VM would not be able to see the disks after the live migration right?
Thanks in advance! Just need a few pointers on where to look as Microsoft has 500 different types of sharing.
Machine 1
Memory 32GB
Drives 32GB boot SSD, 4TB Seagate NAS, 240GB scratch
Machine 2
Memory 32GB
Drives 32GB boot SSD, 2TB WD, 240GB scratch
Here is what I have done so far:
1. Installed Hyper-V on Machine 1's 32GB SSD
2. Made a share on the 32GB SSD (used Server manager)
3. Made a VM sitting in the shared folder and installed Windows Server 2012 Std
4. Added domain controller on 2012 Std VM
5. Made a domain test.local
6. Made a user called HyperV test.local
When I tried to join the Hyper-V server to test.local using test\HyperV it said it could not reach the DC. I can troubleshoot this but it isn't done yet.
Next I want to do the following:
1n. Install Hyper-V on the second machine
2n. Make a second domain controller on the second machine
3n. Somehow make a shared pool using the (2) 240GB ssd and (2) hard drives
4n. Get both the DCs VMs on that shared pool
5n. Start adding VMs on the shared pool
My question is really twofold:
a) Is 3n doable? What should I be googling to research how to make a cluster/share pool across machines?
b) I'm thinking whatever I do in a) and 3n I need to be doing on the Hyper-V servers right? Or should I pass the disks through to another VM? I am saying this since IF the Hyper-V host gets powered down, if I did a pass-through a VM would not be able to see the disks after the live migration right?
Thanks in advance! Just need a few pointers on where to look as Microsoft has 500 different types of sharing.