I'm going to upgrade my server this weekend, and I plan to move from using Windows Server 2016 over to using Windows Nano Server 2016 with Hyper-V Hypervisior to host all my servers as VM's.
Nano Server 2016 is basically Windows Hyper-V Server 2016 with a lot of "crap" removed to lower the footprint. Which again is basically Windows Server 2016 running Server Core only with a few packages unavailable to install.
The thing is that I have three virtual disks running on a LSI/Avagao/Broadcom SAS RAID controller, they are all GPT, ReFS formatted and I don't want to loose any of this data. I want these partitions mounted directly to one of the virtual machines running on the Nano Server installation.
Is there any reason why this should not work? I will remove the RAID controller while doing the Nano Server installation and setup and re-add it afterwards just to make sure the installation doesn't mess with anything. But is there any reason why the disks, partitions etc won't show and be available to attach to virtual machines in Hyper-V afterwards?
Nano Server 2016 is basically Windows Hyper-V Server 2016 with a lot of "crap" removed to lower the footprint. Which again is basically Windows Server 2016 running Server Core only with a few packages unavailable to install.
The thing is that I have three virtual disks running on a LSI/Avagao/Broadcom SAS RAID controller, they are all GPT, ReFS formatted and I don't want to loose any of this data. I want these partitions mounted directly to one of the virtual machines running on the Nano Server installation.
Is there any reason why this should not work? I will remove the RAID controller while doing the Nano Server installation and setup and re-add it afterwards just to make sure the installation doesn't mess with anything. But is there any reason why the disks, partitions etc won't show and be available to attach to virtual machines in Hyper-V afterwards?