Tag Info

Hot answers tagged

1

It's not renaming the adapter, its a different (virtual) adapter that abstracts your physical adapter for use with the virtual switched network Hyper-V uses. Here's a good visualization of how the virtual network works: The orange box is the adapter on your host. You should be able to use PowerShell 4.0's Rename-VMNetworkAdapter command to rename the ...


1

The solution was to add an ACL entry for the VM's default gateway, or, in case of a custom route to the 192.168.Y subnet, the IP address of the route destination, to allow packets to be routed through to the remote host. Add-VMNetworkAdapterAcl -vm $vm -RemoteIPAddress 192.168.X.1 -action allow -direction both This, sadly, is not mentioned in any ...


1

Windows 8.1 uses Client Hyper‑V, not Server Hyper‑V, which used by Windows Server. And Client Hyper‑V doesn't include RemoteFX: There are some features included in Hyper-V on server that are not included in Client Hyper-V. These include the following: The Remote FX capability to virtualize GPUs Live migration of virtual machines from ...



Only top voted, non community-wiki answers of a minimum length are eligible