Editing: How to Add NIC Drivers for Offline P2V in SCVMM 2008

Title

<html>
<body>
Note: This article is based on VMM 2008 &nbsp;and might not apply to VMM 2012 (R2) 
 
When performing a physical-to-virtual (P2V) conversion of either a Windows 2000 SP4 server or any Windows based domain controller, the only supported method to do this is via an offline conversion. With offline P2V, the source computer restarts into the Windows
 Preinstallation Environment (WinPE) before VMM converts the physical disks to Virtual Hard Disks (VHDs). The steps below describe how to identify and add the network drivers for a NIC not supported with in-box drivers during this process.

Note: For the purposes of the below example, I'm using a HP NC3163 Fast Ethernet NIC.

Identifying and adding the driver:
1. Collect the setupapi.app.log file from 'x:\windows\inf' while booted into WinPE.&nbsp;

2. Open the log file and navigate to the bottom and search up for a failure indicating that a compatible Ethernet driver could not be found.

&nbsp;&nbsp;&nbsp; &lt; excerpt from setupapi.app.log &gt; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;&gt;&gt;&nbsp; [DIF_SELECTBESTCOMPATDRV -&nbsp;&nbsp;&nbsp;&nbsp; PCI\VEN_8086&amp;DEV_1229&amp;SUBSYS_B1340E11&amp;REV_08\3&amp;13C0B0C5&amp;0&amp;28]
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;&gt;&gt;&nbsp; Section start 2009/03/24 14:31:58.828 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cmd: wpeinit 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dvi: No class installer for 'Ethernet Controller' 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dvi: No CoInstallers found 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dvi: Default installer: Enter 14:31:58.828 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dvi:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {Select Best Driver} 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !&nbsp;&nbsp;&nbsp; dvi:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Selecting driver failed(0xe0000228) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dvi:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {Select Best Driver - exit(0xe0000228)} 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !&nbsp;&nbsp;&nbsp; dvi: Default installer: failed! 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !&nbsp;&nbsp;&nbsp; dvi: Error 0xe0000228: There are no compatible drivers for this device.
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;&lt;&lt;&nbsp; Section end 2009/03/24 14:31:58.828 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;&lt;&lt;&nbsp; [Exit status: FAILURE(0xe0000228)] 
3. Verify the PnPID of the installed NIC by collecting the NFO file from the server.&nbsp; Use the following steps to collect this file and locate the PnPID of the installed NIC:
 
&nbsp;&nbsp;&nbsp; a.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Click Start, point to Run and type &quot;msinfo32&quot; (without the quotes) in the Open box and click Ok.
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b.&nbsp;&nbsp;&nbsp;&nbsp; This will open the System Information dialog. 
&nbsp;&nbsp;&nbsp; c.&nbsp;&nbsp;&nbsp; Under System Summary, expand Components and then Network followed by&nbsp;&nbsp;&nbsp;&nbsp; Adapter.
 
&nbsp;&nbsp;&nbsp; d.&nbsp;&nbsp;&nbsp; In the right hand pane, a list of all the installed adapters is displayed.
 
&nbsp;&nbsp;&nbsp; e.&nbsp;&nbsp;&nbsp; Scroll down to locate the physical adapter and note the PnPID. 
&nbsp;&nbsp;&nbsp; f.&nbsp;&nbsp;&nbsp; This PnPID should match the one listed in the error from the setupapi.app.log.
 
&nbsp;&nbsp;&nbsp; g.&nbsp;&nbsp;&nbsp; This should look similar to the following: 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Name [00000008] HP NC3163 Fast Ethernet NIC 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Product Name HP NC3163 Fast Ethernet NIC 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PNP Device ID PCI\VEN_8086&amp;DEV_1229&amp;SUBSYS_B1340E11&amp;REV_08\3&amp;13C0B0C5&amp;0&amp;28

4. Next, locate the correct driver for this NIC from the hardware vendor.&nbsp; A quick search for the NIC used in the example turned up the following downloads for this NIC on HP's site.

<a href="http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=407753&amp;lang=en&amp;cc=us&amp;prodTypeId=329290&amp;prodSeriesId=407751&amp;taskId=135">http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=407753&amp;lang=en&amp;cc=us&amp;prodTypeId=329290&amp;prodSeriesId=407751&amp;taskId=135</a>
5. Now we need to locate the correct WinPE driver from the hardware vendor’s site for the offline conversion.&nbsp; Since VMM2008 uses the version of WinPE from Windows Server 2008, you will want to first locate W2K8/Vista drivers for the installed adapter.

6. Here are the drivers available from the hardware vendor for this particular NIC.&nbsp; Note the absence of W2K8/Vista drivers.

&nbsp;&nbsp;&nbsp; Microsoft MS-DOS 
&nbsp;&nbsp;&nbsp; Microsoft Windows 2000 
&nbsp;&nbsp;&nbsp; Microsoft Windows NT 4.0 
&nbsp;&nbsp;&nbsp; Microsoft Windows Server 2003 
&nbsp;&nbsp;&nbsp; Microsoft Windows Server 2003 for 64-bit extended systems 
7. Here is where we're going to run into a bit of trouble with this particular NIC.&nbsp; The NIC is pretty old and the vendor doesn't provide any drivers for Vista or W2K8.&nbsp; We're going to have to try some older drivers and hopefully one of those will work,
 but it will be trial and error, plusit may end up that none of them are compatible with WinPE.

8. I selected the latest released driver for this adapter which happens to be for Microsoft Windows Server 2003 (cp009602) and downloaded it to the C:\HP directory.&nbsp; The contents of the driver download can be extracted by double clicking on it.&nbsp; It's always
 a good idea to extract the contents to a different folder than where the actual executable is.

Here are the extracted contents to the C:\HP\Flat folder:
&nbsp;&nbsp;&nbsp; cp009602.xml 
&nbsp;&nbsp;&nbsp; cp_data.xml 
&nbsp;&nbsp;&nbsp; cpqsetup.exe 
&nbsp;&nbsp;&nbsp; install.xml 
&nbsp;&nbsp;&nbsp; n100w32.sec 
&nbsp;&nbsp;&nbsp; n100325.sys 
&nbsp;&nbsp;&nbsp; netcpqi.ini 
&nbsp;&nbsp;&nbsp; nicdrvd.dll 
9. Now we need to copy the contents of C:\HP\Flat to 'C:\Program Files\Microsoft System Center Virtual Machine Manager 2008\Driver Import' directory.&nbsp; Create a logical folder structure under the 'Driver Import' folder such as ...NIC\HP NC3163.

10. Then we're ready to start the P2V wizard again in SCVMM. 
11. Select the Offline conversion.&nbsp; This is on the same screen where you select the drives to convert.&nbsp; This option is located near the lower left hand corner on this screen.&nbsp; Once expanded, select 'Offline conversion' and OK.&nbsp; The following screen is called
 'Specify offline conversion options'.&nbsp; The default option is 'obtain IP automatically' but you'll want to change that to 'use the following IPv4'.&nbsp; This will automatically pull the IP information from the source and display it in a window that can be edited.&nbsp;
 Verify this information is correct and continue forward and complete the P2V wizard.&nbsp;

If the driver selected was the correct one, the P2V process&nbsp; should complete without any further problems.&nbsp; If it wasn't, then follow the same steps outlined above with another of the drivers from the hardware vendor’s site.&nbsp; Hopefully one will work with
 this version of WinPE and allow the P2V conversion to complete as expected.&nbsp; 
Another option is to temporarily install another newer NIC in the server as a workaround just to get the server virtualized.&nbsp;

For information on the requirements for source computers for P2V conversions please refer to the following TechNet article:&nbsp;
<a href="http://technet.microsoft.com/en-us/library/bb963740.aspx">http://technet.microsoft.com/en-us/library/bb963740.aspx</a>
Note: This information was originally provided by&nbsp;Mike Briggs,&nbsp;Senior Support Escalation Engineer,&nbsp;on the System Center Virtual Machine Manager Team blog:
<a href="http://blogs.technet.com/scvmm/archive/2009/05/05/how-to-add-nic-drivers-for-offline-p2v-in-vmm2008.aspx">http://blogs.technet.com/scvmm/archive/2009/05/05/how-to-add-nic-drivers-for-offline-p2v-in-vmm2008.aspx</a>
</body>
</html>

Comment

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?