Video Screencast Help

Mouse and Keyboard in HyperV BMR Restore is not working

Created: 20 Dec 2012 • Updated: 21 Dec 2012 | 1 comment


Local NBU backup and restore is working but when we are trying to do BMR restore remotely, the peripherals like mouse and keyboard is not working properly or is not responding. We have tried using iLO or RDS but the situation is the same. We are using Win PE during the BMR. Do we have any issues in terms of this situation? Hope you can help.



Comments 1 CommentJump to latest comment

mandar_khanolkar's picture

Please follow below tech-note to get this problem resolved.




  1.  BMR Restore on Hyper- V virtual machine fails to provide mouse or keyboard access in the restore environment.
  2. BMR Restore on Hyper-V virtual machine fails to detect a Virtual Hard disk.
  3. BMR Restore environment on Hyper-V virtual machine fails to detect the virtual network adapter.


On a Hyper-V virtual machine, BMR restore process needs to communicate with synthetic or emulated devices. The new architecture of synthetic devices with Hyper-V poses some unique challenges for system administrators. Without the integration components, users are required to move their VHD's around to the IDE controller, which limits the amount of VHD's that can be used at any given point in time. Additionally, legacy network adapters might need to be added to the VM to provide network access. Also the mouse and keyboard do not work.

However, by adding the integration components to a Windows PE image, those are no longer concerns. The Integration Components of Hyper-V are a set of drivers that are a significant performance change that you can apply to virtual machines for them to be able to install synthetic devices instead of emulated devices.

Some of the drivers that are installed using the Integration Components are: Video driver, network driver (with this you avoid using Hyper-V’s Legacy Network adapter), storage driver, VMBUS (transport for synthetic devices), time sync (time synchronization with the host), etc


  1. Download and install the Windows Automated Installation Kit (AIK) 1.1

Note: Size of WAIK is quite big. You can contact Symantec Support to get smaller and required footprint of this SDK.

2.   We need to extract two files from the c:\windows\system32\vmguest.iso file, which is part of Hyper-V RC1 (available at

You can also mount the ISO image in a VM and extract the files as well. We’re looking for two files. Copy the file that is appropriate for your architecture:

  • 32 Bit: \support\x86\Windows6.0-KB951633-x86.msu
  • 64 Bit: \support\amd64\Windows6.0-KB951633-x64.msu

           At times there are .CAB files present instead of the MSU. Copy the file  

          that is appropriate for your architecture at a folder ---- MSUSOURCE


3.  Create a directory by name “IC” on the same system you installed the AIK, and store the file(s) above there.

4. Expand the CAB file within the directory: %MSUSOURCE%\IC\Drivers

5. Copy the SRT WIM image SRT.WIM and SRT_x64.WIM to a temporary directory ---   PESOURCE

6. Create the folder where you are going to mount the WIM image. “C:\Temp\mount

7. Mount the WIM file using imagex tool:

imagex  /mountrw “%PESOURCE%\srt.wim” 1 “C:\Temp\mount”

imagex  /mountrw “%PESOURCE%\srt_x64.wim” 1 “C:\Temp\mount

8. Inject all drivers one by one using PEIMG tool considering the SRT and driver architecture:

      peimg  /inf= %MSUSOURCE%\IC\Drivers\x86\*.inf /image=”C:\Temp\mount

peimg  /inf= %MSUSOURCE%\IC\Drivers\amd64\*.inf /image=”C:\Temp\mount

*.inf is representing all the previous drivers that we added above. Repeat the command line for each file.

9. Commit changes:

imagex /unmount /commit C:\Temp\mount.