Some nice things I've found, now that I stopped using VMware Workstation for work and have started using Client Hyper-V 3.0:
Powershell management is pre-configured.
You can now use a WiFi adapter for an external virtual network, which is something that required some creativity in the past.
I'm not sure if it's because I assigned both a WiFi linked and an Ethernet linked external virtual adapter, or if it's a change in how Hyper-V treats virtual switches, but apparently you don't need to set up an internal network adapter to remote desktop into a child OS. While the experience still isn't as immersive as VMware Worksation, you at least get full screen and easy access to drives and printers attached to the host.
Powershell management is pre-configured.
You can now use a WiFi adapter for an external virtual network, which is something that required some creativity in the past.
I'm not sure if it's because I assigned both a WiFi linked and an Ethernet linked external virtual adapter, or if it's a change in how Hyper-V treats virtual switches, but apparently you don't need to set up an internal network adapter to remote desktop into a child OS. While the experience still isn't as immersive as VMware Worksation, you at least get full screen and easy access to drives and printers attached to the host.
My Computer
System One
-
- OS
- Windows Server 2012 Standard w/Hyper-V
- Computer type
- PC/Desktop
- System Manufacturer/Model
- HP ProBook 4430s
- CPU
- Intel Core i3-2310M
- Memory
- 16GB DDR3
- Hard Drives
- 80GB Intel 320 SSD
500GB Samsung Momentus