Posted by essjae on March 2, 2017
If you’re playing around with older OSes in the latest versions of Hyper-V, you’re missing one thing, the Integration Components (IC).
With Win10/Server2016 they no longer include this ISO as the current “supported” OSes all get their IC viaWindows Update.
You can get the IC from Hyper-V 2012/2012R2 Server, a free download, here:
https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2012-r2 (you’ll need to either find a way to extract it or install Hyper-V Server in a VM to get the vmguest.iso)
Or, if you’ve got a Windows 8/8.1/2012/2012R2 VM/system available with Hyper-V installed you’ll find it in the C:\windows\system32\ folder.
I’ve got a copy from Hyper-V 2012 R2 here: https://1drv.ms/u/s!AnbqFQxI6C6pidtRrLfIRLDSHKeYmw
No guarantees how long MS will allow it will stay up here, though it’s freely distributed with Hyper-V Server.
Posted in Virtualization, Hyper-V, Windows 8, W2012, Windows 2012, Windows 8.1, Windows 10, Windows 2012 r2, Windows 2016 | Tagged: Hyper-V, Hyper-V 10, Hyper-V 3.0, Microsoft, Virtualization | Leave a Comment »
Posted by essjae on May 15, 2015
Disable Secure Boot
Add a DVD drive for your ISO file
Posted in Hyper-V, Virtualization, Windows 10 | Tagged: Hyper-V 10, Microsoft, Virtualization, Windows, Windows 10 | Leave a Comment »
Posted by essjae on May 14, 2015
Update: It’s now a lot easier to create networks (using PowerShell) in Windows 10 Hyper-V: https://smudj.wordpress.com/2016/03/10/adding-nat-to-hyper-v-in-windows-10-and-higher/
Update: Build 10586.3–Loopback adapter was missing, added back, and checked Hyper-V Extensible Virtual Switch. This seems to happen with each build update. A reboot may also be required.
This procedure shows you how to set up bridged and shared (NAT) networking with a single physical network card.
Standard Bridged Networking
- Start the Hyper-V Manager and click Virtual Switch Manager
- Select External and click Create Virtual Switch
- Enter Bridged or similar to identify this network as being on your physical network
- Select the correct network adapter under External network, this should be an active network card, i.e. one that is connected to your network and your host is using.
- If you only have one network card, verify that Allow management operating system to share this network adapter.
- If you have multiple network cards, and want to use this card exclusively for VMs, uncheck Allow management operating system to share this network adapter.
- Click OK and the new virtual switch will be created.
- Verify that you don’t have any ongoing network tasks before clicking yes, as your network connection will likely be disrupted when the virtual switch is created.
- This will create a network adapter under Network Connections called vEthernet (name_used), in this case, vEthernet (Bridged)
Manually add a loopback adapter
- Open a cmd prompt with Administrator privileges.
- Type cmd, right-click on the search result and click Run as administrator
- Type hdwwiz and press enter
- Click Next to start the wizard.
- Select Install the hardware that I manually select from a list (Advanced), and click
- Highlight Network Adapters, and click Next.
- Select Microsoft from the Manufacturer column and Microsoft KM-TEST Loopback Adapter from the Model column and click Next.
- Click Finish to complete the wizard.
- Open Network Connections (CTRL+X and select Network Connections), locate the newly created loopback adapter, right-click it and click Rename, and rename it from Ethernet 2 or Ethernet 3 to Loopback.
Create the Shared Virtual Network Switch in Hyper-V
- Open the Hyper-V Manager and click Virtual Switch Manager
- Select External and click Create Virtual Switch
- Enter a descriptive name, like Shared or NAT. This will create a network adapter under Network Connections called vEthernet (name_used), in this case, vEthernet (Shared)
- Select the Loopback adapter under the External Network selection box, click OK, then click Yes, this operation will not disrupt your host networking.
Connect the Loopback Adapter and Virtual Switch to the Network
- Open Network Connections (CTRL+X and select Network Connections)
- Click Change adapter settings
- Right-click and select Properties on the vEthernet (Bridged) network adapter created under Standard Bridged Networking.
- Click the Sharing
- Click Allow other network users to connect through this computer’s Internet connection.
- Select the Shared network connection, it should be listed as vEthernet (Shared), or whatever name was used in place of Bridged.
- Click Ok.
Note: The Hyper-V networking is very fragile here, and you may need to reboot if you get errors when trying to connect and share the connections.
Here’s the completed Network Connections Window, note the Bridged and Shared Hyper-V adapters. Apologies for the pixelation, the Hyper-V Manager is not 4K screen friendly.
Here’s two VMs using the Shared networking, note, the 192.168.137.x network, the default used by ICS. Also shown is a third VM using the host network and the host’s IP.
Posted in Computers, Hyper-V, Windows 10 | Tagged: Hyper-V, Hyper-V 10, Microsoft, Virtualization, Windows 10 | 2 Comments »
Posted by essjae on May 13, 2015
Keeping ISOs on a server/network share is a great way to save space for all your installation ISOs. Unfortunately, Hyper-V does things a little different (it’s called constrained delegation) and can’t directly access an ISO file on a network share or mapped drive with your user account. Hyper-V will ignore any mapped drives you’ve got, but with Windows 10 you can add a network location from Windows Explorer’s Computer tab (1). This makes it easy to get to a remote network share quickly.
You’ve got 2 options:
- Go to the ISO location and mount it as a physical drive. This tricks Hyper-V into thinking the disk is local and not network shared. It works great for everything but Gen2.
- Constrained delegation configuration
- On a domain: this is easy, you just need to add your Hyper-V computer’s domain joined account to the network share.
- Go to the shared drive/folder and right-click–>Properties.
- Click the Sharing tab, click Advanced Sharing.
- Click Permissions, click Add.
- Click Object Types and select Computers, click OK.
- Enter the computer’s name, and click Check names, click OK to add.
- Workgroup/Microsoft accounts: this is a little more involved and care should be taken if this is used anywhere other than a home or lab network as you’re changing some security settings
- Go to Administrative Tools–>Local Security Policy, in Security Settings–>Local Policies–>Security Options change these settings:
- Network Access: Do not allow anonymous enumeration of SAM accounts and shares – Change to: Disabled
- Network Access: Let Everyone permissions apply to anonymous users – Change to: Enabled
- Network Access: Restrict anonymous access to Named Pipes and Shares – Change to: Disabled
- Network Access: Shares that can be accessed anonymously, add the name of the share on the Windows server, i.e. if the share name is “ISOs” add “ISOs” here. *I don’t have a non-Windows NAS, if you do and have found a solution for this, please let me know and I’ll post it
- Add a network share:
- Open This PC via the start menu, or Win+E.
- Click Computer, click Add a network location
- Follow the Add Network Location Wizard to finish
- For a standard Windows share, use the syntax: \\servername\sharename replacing with the actual name of the server and share.
**Content created and tested on Windows 10 Pro Insider Preview Build 10074
Posted in Computers, Hyper-V, Virtualization, Windows 10 | Tagged: Hyper-V, Hyper-V 10, Virtualization, Windows, Windows 10 | Leave a Comment »