<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Below are some workarounds for stop error 0x7d after a conversion from physical to virtual.  I unfortunately had to use two out of the three workarounds to get my problem machine running.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Reason:</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">The source virtual machine does not have the appropriate drivers.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">A log file error message such as "Unable to find symmpi.sys in the specified CAB files," indicates that reconfiguration failed because the appropriate drivers are not present on the source operating system. This is usually observed in Windows 2003 Server Service Pack 1. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Workaround 1:</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Upgrade source server to service pack 2 and rerun the migration.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Workaround 2:</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Set aside the virtual machine created during the failed import. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Attach the VMDK file containing the system folder to another Windows 2003 virtual machine. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Replace the WINDOWSDriver Cachei386driver.cab file in the target virtual machine with a version of the driver.cab file that includes the missing driver from the helper virtual machine. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Detach the VMDK file from the helper virtual machine and run the Configure Machine wizard on the target virtual Machine.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Workaround 3: </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Replace the driver.cab file, as mentioned above in the source virtual or physical machine before the migration. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Rerun the migration</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"> </p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;">Will Turbeville, eGroup</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: small; font-family: Calibri;"><a href="http://egroup.jasonmangone.com">http://egroup.jasonmangone.com</a></span></p>