L
Livinggreen
Hi,
I'm new to both Windows Server and virtualization, so this may be an easy question, but it's giving me some trouble. This is a three-part question:
1. If the Hyper-V role converts the original Server 2016 OS to a virtual machine running on top of Hyper-V, then why doesn't the original server 2016 OS appear in the "hyper-v manager" list of "virtual machines"?
2. For NIC teaming, does the original Server 2016 OS with hyper-V role enabled have to be treated as a virtual machine thus requiring the following instructions be followed? Create a New NIC Team in a VM
3. In general/conceptually, when configuring features for the original Server 2016 OS after the Hyper-V role has been enabled, how should I approach the original Server OS; as a Virtual Machine, as a bare metal OS, or as something else?
Thank you all for any help.
Continue reading...
I'm new to both Windows Server and virtualization, so this may be an easy question, but it's giving me some trouble. This is a three-part question:
1. If the Hyper-V role converts the original Server 2016 OS to a virtual machine running on top of Hyper-V, then why doesn't the original server 2016 OS appear in the "hyper-v manager" list of "virtual machines"?
2. For NIC teaming, does the original Server 2016 OS with hyper-V role enabled have to be treated as a virtual machine thus requiring the following instructions be followed? Create a New NIC Team in a VM
3. In general/conceptually, when configuring features for the original Server 2016 OS after the Hyper-V role has been enabled, how should I approach the original Server OS; as a Virtual Machine, as a bare metal OS, or as something else?
Thank you all for any help.
Continue reading...