Jonathan's Manage and Automate

VMM SCO SMA WAP - Solutions and Guidance

Drivers Required for Offline P2V - How to Download, Extract and Stage

Drivers Required for Offline P2V - How to Download, Extract and Stage

  • Comments 3
  • Likes

Drivers Required for Offline P2V - How to Extract and Where to Place

There are two types of P2V with SCVMM 2008: offline and online. Online is the way to go most of the time, if you are using Windows 2003 or higher. In a few instances you will need to perform an offline conversion instead. If the Source machine (the machine to be converted) is Windows 2000 SP4, you have no choice… Offline is the only option. Another time to use offline conversion is when the source machine is a domain controller. Here’s a doc to explain the ramifications (USN rollback situations):

Deployment Considerations for Virtualized Domain Controllers

http://technet.microsoft.com/en-us/library/dd348449.aspx

 

The offline conversion process entails booting the source machine into WinPE and copying the contents of the hard drive via BITS to the destination Host. WinPE as included in SCVMM is based on Vista SP1 (Windows 2008). This means that while there is a good chance the network and mass storage drivers required are included in WinPE, the list is not inexhaustible and there will be times when the correct driver needs to be provided. The rest of this article explains how to do this.

 

This article describes how to provide the correct network drivers for WinPE during  the offline phase of P2V. The same principles apply when WinPE instead needs the correct mass storage drivers to access the disk.

Indications of a driver issue
When booted into the WinPE phase of an Offline P2V, WinPE has no network connectivity. 'ipconfig /all' at the command prompt returns an error or no information. Alternately, there may simply be a failure to access the disk as correct SCSI card drivers are required.

Errors from the 'scvmm_winpe_setupapi.log' file
(See Related Links at end of this post for instructions on creating this trace file)
Log excerpt
>>> [DIF_SELECTBESTCOMPATDRV -  PCI\VEN_8086&DEV_105E&SUBSYS_105E8086&REV_78\3&61AAA01&0&48]
>>> Section start 2008/10/31 14:24:35.352

cmd: winpeshl.exe
dvi: No class installer for 'Ethernet Controller'
dvi: No CoInstallers found
dvi: Default installer: Enter 14:24:35.363
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.

<<< Section end 2008/10/31 14:24:35.363
<<< [Exit status: FAILURE(0xe0000228)]

Locate the correct drivers for your network card
NOTE: Most manufacturers now provide a single installation application to install drivers in Windows for you. This single .EXE or .MSI file CANNOT be used without first extracting the file contents.

- The drivers must designed for VISTA or WINDOWS 2008. The version of WinPE used by
SCVMM is based on Vista/Windows 2008

- There must be .SYS, .INF, and .CAT files for the offline driver install
- It is recommended that drivers are downloaded from the NIC manufacturer's site.
(NOTE: If using SCVMM 2007, locate drivers designed for Windows 2003 instead)

Identify the Network Card (NIC)
The SCVMM Admin Console will detect the type of network card on the source machine, and this description may be good enough to locate the correct NIC driver online

 If you need further details on the NIC
     - Open Device Manager in the Source machine to determine the type of NIC used.
     - The VEN identifies the NIC exactly and is useful in locating compatible drivers.


This can be easily  found in Windows or in the WinPE trace log.
     - In Windows: The '%windir%\setupapi.log' file lists all installed hardware
     - In WinPE use the 'scvmm_winpe_setupapi.log'
     - Using the example above we see the VEN:

PCI\VEN_8086&DEV_105E&SUBSYS_105E8086&REV_78\3&61AAA01&0&48


Download the Correct NIC Driver
Search the vendor's site for the correct card. If you are unable to locate it, search the web for the VEN number.
Example keywords for this NIC: VEN 8086 DEV 105E

This is the vendor's site and lists of adapters that have matching VEN numbers
http://www.intel.com/support/network/sb/CS-012904.htm

 

Locate the correct driver on the vendor site. We will use this site for this example:
http://www.intel.com/support/network/sb/CS-006120.htm


- Select the correct NIC and you will be taken to a page listing drivers for different Windows builds.

- Choose the drivers for Vista 32bit.

- 'PROVISTA32.EXE' is the link you will select in this example

- On this page you see the actual download 'PROVISTA32_V13_4.exe' and a link to the 'ReadMe'

- Download and save the driver to a temp directory close to the root of C: such as ‘C:\temp’

- Open the online ‘Readme’ to determine how to properly extract the drivers from  'PROVISTA32_V13_4.exe'


Extract the contents of the Executable
Create a directory to extract the files to. Do NOT extract the files to the same directory in which the  executable (PROVISTA32_V13_4.exe) resides

Example Steps

- Make a directory named 'c:\temp\Intelextracted'

- In this instance the readme shows that you type 'PROVISTA32_V13_4.exe /e /f c:\temp\Intelextracted’

- This extracts the files and saves them to 'c:\temp\Intelextracted'

- Open the c:\temp\Intelextracted directory and locate the correct drivers

- Sometimes you will find the files in a Platform directory that has a folder for the correct operating system. In this example you would open the PRO1000 folder as the card is a PRO1000. This folder contains a Win32 folder with many .inf, .cat and .sys files.

- Rename the Win32 directory to PRO1000 and place the directory in 'C:\Program
Files\Microsoft System Center Virtual Machine Manager 2008\Patch Import'


Perform P2V again with the correct drivers
Start the P2V process again, and this time when hardware has been detected and the network card description is show, click the 'Browse' button at the bottom and select the 'C:\Program Files\Microsoft System Center Virtual Machine Manager 2008\Patch Import\PRO1000' folder, then click Next

If you selected the correct drivers WinPE will now be able to initialize the NIC and gain network access during the offline process.

Related Links
Trace file creation during WinPE phase of P2V process

P2V: Converting Physical Computers to Virtual Machines in VMM
http://technet.microsoft.com/en-us/library/cc764232.aspx


Converting Physical Computers to Virtual Machines in VMM (P2V Conversions)
http://technet.microsoft.com/en-us/library/bb963740.aspx

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment