Thursday, November 21, 2013

Vmware Driver Injection post migration, Fix stop 7b

Driver Injection Files for Windows 2003 32bit

Files can be grabbed from here

// p2v pre migration driver injection Lsilogic controller for vmware
Import Reg files on the source migration server
.sys files need to be copied to %windir%\systems32\drivers
system should boot and no post migration task need be performed

// p2v post migration driver injection lsilogic controller for vmware
failure to do pre migration task will result in stop 7b error/blue screen
to resolve;
1. boot hirens bootcd on the vm and select 'mini windows xp'
2. when booted, click the Hiren menu icon in the tray -> Registry -> Registry Editor PE.
5. When asked to, set the remote Windows directory (usually C:\Windows) and press OK.
6. Click OK on each window to select the related registry hive. If you want to edit a registry
value from HKEY_CURRENT_USER you will need to select Yes when asked if you want to load an
NTUSER.DAT and locate the file in the user directory, however this is not required.
7. Expand HKEY_LOCAL_MACHINE and the hives will automatically load with the _REMOTE_ prefix.
Navigate to _REMOTE_SYSTEM. Check the number of the ControlSet, reg files have been made for 001
and 003, if another number shows up then you'll have to copy a set and edit accordingly.
8. Goto File > import all reg remote control set00X that are required one by one.
9. .sys files need to be copied to %windir%\systems32\drivers on the offline os
reboot and system should boot.

Sources
http://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1005208
http://www.webbosworld.co.uk/blog/?p=306
http://www.raymond.cc/blog/how-to-edit-windows-registry-key-values-without-booting-in-windows/