Windows 10: Windows 10 deployment via WDS in Hyper-V VM not working

Hello all,
I have WDS (Windows Deployment Services) running Windows Server 2012 (not R2) which is used to deploy Windows 7 and Windows 8.1 without problems.

Now I want to deploy Windows 10, but the problem is - when I add Windows 10 (build 10240) boot.wim to my WDS and try to network boot a virtual machine (hyper-v), windows logo appears and nothing else.

Screenshot where boot process stops and doesn't continue:




However, when I try to network boot using a physical hardware (a laptop), boot process works just fine, everything is as expected.
The some goes for using Oracle VM Virtualbox; when I do a network boot in this virtual machine, it works.

So my guess is there is a problem with Hyper-V.
I'm using Hyper-V on Windows 8.1 x64.

Anyone else has this problem ?

:)

 

Remote Desktop Connection problem with Virtual Machine

We made the big mistake of configuring a WINDOWS-10 VM to allow for Remote Desktop Connections. We are unable to disassociate the VM from RDM. We can no longer access the VM!!! The following is the pertinenet
information:

• Server is running Windows-10 Professional 64 with Hyper-V installed.
• VM is Windows-10 Professional 64.
• In VM allowed Remote Desktop Connections.
• From server successfully connected to VM via RDM.
• Closed RDM connection. Unable to access VM.
• Turned off VM from Hyper-V Manager.
• Attempted to restart VM, unable to connect via Hyper-V from message box the following is displayed:
  
  Video Remoting was disconnected. The virtual maching is currently using the Remote X 3D video adapter. A user is currently connected via Remote Desktop Connect to the virtual machine by using Remote Desktop Connection.
• Connected via Remote Desktop Connection. Attempted to turn off allowing Remote Desktop Connection. VM hung.
• VM Wouldn't turn off via Hyper-V manager.
• Shutdown host system and rebooted.
• Unable to connect via console or RDM.
• Shutdown host system and rebooted.
• Deleted VM via Hyper-V Manager.
• Restored VM system disk from backup prior to RDM usage.
• Created new VM. the messages in itm 7 above are displayed.

What can be done to recover? Why does Hyper-V retain a broken connection?

 

MSDN Win 10 Pro Activation Issues

Hello,

I'm trying to activate the Windows 10 virtual machine running on my Windows 2012 R2 / Windows 10 Hyper-V machine.

The ISO was downloaded from MSDN, the license key comes with my MSDN subscription.

Installed the OS on a physical machine and activated the OS. This one worked fine. Next I've created a Windows 10 VM and run it in Hyper-V. Using the same and all other keys I can get via MSDN, non of them work. Some report error 7008001c, some non-core
windows, etc ....

How do I get my Windows 10 VM activated?

Regards, V.

 

Problem solved.
Due to my unique environment, I had a different value under DHCP 67 option Bootfile name. By 'different' I mean some custom bootfile name we use in our environment.
Once I changed it to "\boot\x64\wdsnbp.com" it worked in Hyper-V too.

 

Thanks for sharing the fix, it may help others *Thumbs