Here’s a new Knowledge Base article we published today. This one shows you how to quickly fix an issue where a P2V in System Center 2012 Virtual Machine Manager fails when using NIC teaming.
When using System Center 2012 Virtual Machine Manager (VMM) to perform an offline P2V (Physical to Virtual migration) of Windows Server 2003 machines configured with HP network teaming, the process only identifies the network adapter configured with an address which is the “HP Network Teaming Virtual Miniport Driver”. The P2V wizard also displays the following error message:
Error (13246): No compatible drivers were identified for the device: HP Network Teaming Virtual Miniport Driver. The offline physical-to-virtual conversion requires a driver for this device. Device Type: network adapter Device Description: HP Network Teaming Virtual Miniport Driver Device Manufacturer: Hewlett-Packard Company Hardware IDs (listed in order of preference):cq_cpqteammp Compatible IDs (listed in order of preference):None Recommended Action: Create a new folder under C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\Driver Import on the Virtual Machine Manager management server and then copy the necessary 32-bit Windows Vista driver package files for this device to the new folder. The driver package files include the driver (.sys) and installation (.inf and .cat) files. Check the device manufacturer's website for the necessary drivers.
The offline P2V migration fails as there is no driver available for the physical network adapter, which in this case is the “HP NC373i Multifunction Gigabit Server Adapter”.
During an offline P2V, the wizards scans for whether the drivers used for the WinPE boot are already available to the winpe.wim. For systems running Windows Server 2003 and configured with the HP network teaming software “Network Configuration Utility” (NCU), the requirement scan only reports the active network adapter (e.g. HP Network Teaming Virtual Miniport Driver) instead of the physical network adapter (e.g. HP NC373i Multifunction Gigabit Server Adapter).
The problem can be solved by injecting the required drivers for the physical network adapter manually into the WinPE image on the VMM management server using DISM. The following PowerShell script does this automatically: Only the source WinPE image, a temporary directory and the missing driver have to be specified. Provide the 32-Bit Windows Vista driver package files to patch the WinPE image. Important This section, method, or task contains steps that tell you how to patch the WinPE image. However, serious problems might occur if you modify the image incorrectly. Therefore, make sure that you create and keep a backup of the original image before proceeding with the script.
#Original WinPE image (‘amd64’ or ‘x86’)
$WinPE = ‘C:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim’
$TempPath = ‘C:\Temp\WinPE\’
#Driver for physical network adapter
$DriverPath = ‘C:\Temp\WinPE\NC373i\bxvbd.inf’
copy $WinPE $TempPath
$WinPEimage = $TempPath + ‘winpe.wim’
$WinPEimageTemp = $WinPEimage + ‘.tmp’
$MountDir = ‘C:\Temp\WinPE\Mount’
copy $WinPEimage $WinPEimageTemp
dism /mount-wim /wimfile:$WinPEimageTemp /index:1 /mountdir:$MountDir
dism /image:$MountDir /add-driver /driver:$DriverPath
dism /unmount-wim /mountdir:$MountDir /commit
copy $WinPEimageTemp $WinPE
On source servers running Windows Server 2008 and newer, the requirement scan reports the correct network adapter and no manual workaround is required.
For more information about how to use DISM, see the following: http://technet.microsoft.com/en-us/library/cc766067(v=ws.10).aspx
For the most current version of this article please see the following:
2685483 : A P2V in System Center 2012 Virtual Machine Manager fails with "No compatible drivers were identified"
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/