Issues around BMR restore of Windows clients in case of Hyper-V
|Article:TECH159025|||||Created: 2011-04-28|||||Updated: 2013-11-27|||||Article URL http://www.symantec.com/docs/TECH159025|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
- BMR Restore on Hyper- V virtual machine fails to provide mouse or keyboard access in the restore environment.
- BMR Restore on Hyper-V virtual machine fails to detect a Virtual Hard disk.
- 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 a few challenges for the system administrators. Without the integration components, users are required to move their VHDs around the IDE controller, which limits the amount of VHDs that can be used at any given point in time. Additionally, you may need to add the legacy network adapters to the VM to provide network access. The mouse and keyboard also fail to work.
However, by adding the integration components to a Windows PE image, you can eliminate these problems. The Integration Components of Hyper-V are a set of drivers that offer a significant performance change that you can apply to virtual machines 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), and so on.
By carrying out the following procedure, you can resolve the problem:
- Download the Windows Automated Installation Kit (AIK) 1.1 from the following location and install it:
- We need to extract two files from the c:\windows\system32\vmguest.iso file, which is part of Hyper-V RC1 and is available at:
- 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
- For Windows 32-bit - Windows6.0-HyperVIntegrationServices-x86.cab
- For Windows 64-bit - Windows6.0-HyperVIntegrationServices-x64.cab
- Create a directory by name “IC” on the same system you installed the AIK, and store the file(s) above there.
- Expand the CAB file within the directory: %MSUSOURCE%\IC\Drivers
- Copy the SRT WIM image SRT.WIM and SRT_x64.WIM to a temporary directory --- PESOURCE
- Create the folder where you are going to mount the WIM image. “C:\Temp\mount”
- Mount the WIM file using the imagex tool depending on the OS architechture:
- Inject all drivers one by one using the PEIMG tool considering the SRT and driver architecture:
For Windows 32-bit, run the following command:
peimg /inf= %MSUSOURCE%\IC\Drivers\x86\*.inf /image=”C:\Temp\mount”
For Windows 64-bit, run the following command:
peimg /inf= %MSUSOURCE%\IC\Drivers\amd64\*.inf /image=”C:\Temp\mount”
Note: .inf is representing all the previous drivers that you have added.
Repeat the command line for each file.
- Commit changes by using the imagex tool: imagex /unmount /commit C:\Temp\mount.
Article URL http://www.symantec.com/docs/TECH159025