VMware Communities: Message List - Ultimate-P2V Available for Download

Re: Ultimate-P2V Available for Download

ukturtle — Thu, 08 Nov 2007 13:21:11 GMT

I've got a real problem with P2V'ing a Fedora5 machine to a VMware Server vm and I'm wondering if anyone can help?

My FC5 box is a hybrid I built myself. The vm is on a W2K3 server with VMware server 1.0.4. Nothing special about either machines except FC5 server is not RAID'd but W2K3 box is.

Im using the BartPE disk and everything works fine and the Ghost32 starts copying data (disk-to-disk) from master to slave but it gets 14% of the way through, stops and gives me an "application error 29004" and then something to do with some bad sectors its found and cant continue. I've tried using -FRO option but it still doesn't work - gets a little further but then comes back with same error.

I'm running a scan of the FC5 servers hard disk now using HDD Regenerator but its taking a VERY long time so thought I'd ask you guys to see if there was some other problem. Btw, when I start Ghost from the physical server and the virtual server they both say there's not cdrom support even though i put all the ghost files recommended on the ultimate p2v instructions into the correct directory. Does this have anything to do with my problem do you think?

Any help would be much appreciated as I'm using this method because Platespin PowerConvert doesn't support my versions of Linux and I've already bought 1 license so I'm getting in a bit of a pickle!

Thanks guys.

Bryn

Re: Ultimate-P2V Available for Download

Mike_Laverick — Wed, 07 Feb 2007 20:32:06 GMT

A new version of the Fixvmscsi plug-in has been released. It's been written by RTFM Education reader, Jeffery Crystal. Jeffery has made some substantial changes and improvements - so many than that I have decided to rename the old plug-in originally written by Qui Hong as the "Classic Version" - and referring to Jeff's as the "New Improved Version". Jeff has added better Dell PERC support, and has made the plug-in more work like a plug-in. It is also compatiable with Sherpya XPE Desktop Support.

I've yet to have time to test JeffÃ¢'s plug-in - as I am up to my neck in writing the new book! But it will be on my to do list when I have more free time.

You can download the new version from the Ultimate-P2V home page

Link:

http://www.rtfm-ed.co.uk/?page_id=174

Regards
Mike

Message was edited by: to get rid of the funny characters!
Mike_Laverick

Re: Ultimate-P2V Available for Download

McRight — Sat, 03 Feb 2007 23:31:20 GMT

indeed, the mouse and keyboard hang.

Re: Ultimate-P2V Available for Download

devzero — Sat, 03 Feb 2007 13:08:24 GMT

After the injection of Qui Hongs FixVM-SCSI the system boots
but halts on the syskey password, which I have but cant type.

you mean, the system doesn`t react to any keyboard input?
try pressing left-shift twice and see if this makes any difference. i have my VMs loosing keyboard from time to time - for example when installing sles9 - and 2x left-shift fixes the problem.

Re: Ultimate-P2V Available for Download

McRight — Sat, 03 Feb 2007 11:58:10 GMT

hi, i have a question concerning p2v and post it here in the hope somebody responds to it.

Thanks to the articles posted on rtfm to perform a p2v migration, i managed to partially migrate my old system in vmware.

My old system was a dual boot xp/sb2003.

The both os are cloned as provided in the manual.

XP works fine, SBS2003 is protected with syskey.

After the injection of Qui Hongs FixVM-SCSI the system boots but halts on the syskey password, which I have but cant type.

The tools for resetting the syskey are linux based and so I cant provide the Buslogic drivers at startup with the F6 key.

Thank you very much for any help provided

Re: Ultimate-P2V Available for Download

AaronM — Thu, 11 Jan 2007 01:59:05 GMT

Ok, here is my solution for P2V using Altiris, WindowsPE, and VMware Workstation. Hopefully this helps someone else!

Physical machine
model: IBM 8213-H1M
OS: Windows XP SP2 Corp

Virtual Machine:
VMware Workstation 5.5.2 running on Windows Vista Business host.

Notes:
- The HAL (and the ntoskernel.exe etc) were extracted from a VM built from a genuine XPSP2 cd.

Known issues:
- Mini setup still asks for sbsetup.exe for soundblaster (cancel allows you to continue) - I suspect this is due to my BTS driverpack source files having been removed. Your mileage will vary again. I can probably fix this, but too lazy for now.

See the appendix section for file content and directory listings.

----------------------Part A - Capture IMG from Physical machine-------------------

1) Build physical workstation and apply all windows updates, patches, programs etc required.

2) Sysprep physical workstation and shut down.

3) PXE boot to WinPE and map various network drives

4) Use RDeploy to capture image to a network drive

----------------------Part B - Prepare new VM Workstation--------------------------

5) Create a new VMware workstation using default settings.

----------------------Part C - Deploy Image to Virtual PC, and Prep --------------------------

6) PXE boot vm to WinPE and map various network drives

7) Use RDeploy to restore image captured in step 4 (do not restart).

8) Copy VMware drivers to newly imaged drive:

[code]
FIRM -RECURSE COPY "U:\%#!computer@prod_name%" prod:Drivers\
[/code]

9) Load registry hive and inject keys, copy mass storage drivers to imaged drive

[code]
F:\FIRM -FORCE COPY PROD:Windows\System32\Config\System F:\Temp\%ID%.hiv

REG LOAD HKLM\System_00 F:\Temp\%ID%.hiv
REG IMPORT "U:\%#!computer@prod_name%\MassStorage\fix_ide_01.reg"
REG IMPORT "U:\%#!computer@prod_name%\MassStorage\fix_ide_02.reg"
REG UNLOAD HKLM\System_00

F:\FIRM -FORCE COPY F:\Temp\%ID%.hiv PROD:Windows\System32\Config\System

F:\FIRM -FORCE COPY "U:\%#!computer@prod_name%\MassStorage\*.sys" PROD:Windows\System32\Drivers
[/code]

10) Copy correct HAL to imaged drive

[code]
F:\FIRM -FORCE COPY "U:\%#!computer@prod_name%" prod:Windows\system32
[/code]

11) Prep sysprep.inf copy to imaged drive:

[code]
REM ReplaceTokens .\sysprep\storepatch.inf .\temp\%ID%.inf
F:\FIRM -FORCE COPY F:\temp\%ID%.inf prod:sysprep\sysprep.inf
[/code]

12) Reboot, wait approx 20 mins, then enjoy.

---------------------------------------Appendix-----------------------------------------------------------------------

Listing of U drive mapping (drivers) - I specify the folder structure c:\drivers\xxxxx as a driver source using registry key in the base image
As mentioned above, I map U drive to different locations based on the machine type I am building.
[code]
Directory of U:\

10/01/2007 03:47 p.m. <DIR> VMware Virtual Platform
0 File(s) 0 bytes

Directory of U:\VMware Virtual Platform

04/01/2007 01:49 p.m. 0 '
10/01/2007 02:46 p.m. <DIR> Audio
10/01/2007 03:47 p.m. <DIR> Chipset
04/08/2004 05:00 a.m. 131,968 hal.dll
10/01/2007 04:05 p.m. <DIR> MassStorage
21/12/2006 11:20 a.m. <DIR> Misc1
10/01/2007 03:00 p.m. <DIR> Misc2
10/01/2007 03:01 p.m. <DIR> Misc3
21/12/2006 11:20 a.m. <DIR> Net
04/08/2004 05:00 a.m. 2,056,832 ntkrnlpa.exe
04/08/2004 05:00 a.m. 2,180,992 ntoskrnl.exe
21/12/2006 11:20 a.m. <DIR> Video
4 File(s) 4,369,792 bytes

Directory of U:\VMware Virtual Platform\Audio

12/01/1999 06:26 a.m. 59,392 a3d.dll
19/07/2005 02:57 p.m. 163,840 ADIHdAud.sys
18/08/2001 02:59 a.m. 3,072 audstub.sys
31/07/2000 02:00 p.m. 130,048 ctpcir32.dll
22/06/2002 12:26 a.m. 30,720 CTSETRes.dll
22/01/1999 06:31 a.m. 2,259,070 eapci2m.ecw
27/02/2006 04:23 a.m. 22,820 oem481.inf
14/10/2005 02:16 p.m. 26,535 oem689.inf
07/09/2001 02:00 p.m. 3,126 SBPCI.bmp
07/09/2001 02:00 p.m. 3,638 SBPCI.ico
23/10/2002 04:45 a.m. 668,160 sbpci.sys
12/10/2002 01:26 p.m. 86,016 sbres32.dll
21/12/2006 03:35 p.m. 159 Setup.DIY
05/08/2004 01:00 a.m. 3,581 wave.inf
14 File(s) 3,460,177 bytes

Directory of U:\VMware Virtual Platform\Chipset

01/07/2006 03:27 p.m. 1,621 oem4.inf
01/07/2006 03:27 p.m. 10,880 vmscsi.sys
2 File(s) 12,501 bytes

Directory of U:\VMware Virtual Platform\MassStorage

05/08/2004 01:00 a.m. 95,360 atapi.sys
10/01/2007 11:34 a.m. 6,226 fix_ide_01.reg
10/01/2007 04:04 p.m. 9,123 fix_ide_02.reg
05/08/2004 01:00 a.m. 5,504 intelide.sys
17/08/2001 01:51 p.m. 3,328 pciide.sys
05/08/2004 01:00 a.m. 25,088 pciidex.sys
09/01/2007 10:03 a.m. 11,026 vmscsi.sys
7 File(s) 155,655 bytes

Directory of U:\VMware Virtual Platform\Misc1

14/11/2006 08:50 a.m. 1,556 oem1.inf
21/12/2006 11:20 a.m. 159 Setup.DIY
14/11/2006 08:50 a.m. 7,898 vmmouse.cat
14/11/2006 08:50 a.m. 11,568 vmmouse.sys
4 File(s) 21,181 bytes

Directory of U:\VMware Virtual Platform\Misc2

28/05/2005 08:14 a.m. 142,464 aec.sys
04/08/2004 12:07 a.m. 52,864 DMusic.sys
04/08/2004 12:08 p.m. 60,288 drmk.sys
04/08/2004 12:07 a.m. 2,944 drmkaud.sys
04/08/2004 12:07 a.m. 171,776 kmixer.sys
04/08/2004 01:56 p.m. 4,096 ksuser.dll
01/02/2006 10:31 a.m. 145,920 portcls.sys
04/08/2004 12:07 a.m. 6,400 splitter.sys
05/11/2005 09:55 a.m. 48,768 stream.sys
17/08/2001 03:00 p.m. 54,272 swmidi.sys
04/08/2004 12:15 a.m. 60,800 sysaudio.sys
04/08/2004 01:56 p.m. 23,552 wdmaud.drv
04/08/2004 12:15 a.m. 82,944 wdmaud.sys
05/08/2004 01:00 a.m. 23,685 wdmaudio.inf
14 File(s) 880,773 bytes

Directory of U:\VMware Virtual Platform\Misc3

05/08/2004 01:00 a.m. 27,604 mshdc.inf
04/08/2004 01:56 p.m. 74,752 storprop.dll
2 File(s) 102,356 bytes

Directory of U:\VMware Virtual Platform\Net

14/11/2006 08:50 a.m. 3,561 oem3.inf
21/12/2006 11:20 a.m. 189 Setup.DIY
14/11/2006 08:50 a.m. 7,900 vmware-nic.cat
14/11/2006 08:50 a.m. 29,488 vmxnet.sys
4 File(s) 41,138 bytes

Directory of U:\VMware Virtual Platform\Video

14/11/2006 08:50 a.m. 2,970 oem0.inf
21/12/2006 11:20 a.m. 196 Setup.DIY
14/11/2006 08:50 a.m. 91,568 vmx_fb.dll
14/11/2006 08:50 a.m. 10,544 vmx_mode.dll
14/11/2006 08:50 a.m. 9,052 vmx_svga.cat
14/11/2006 08:50 a.m. 22,704 vmx_svga.sys
6 File(s) 137,034 bytes
[/code]

Contents of fix_ide_1.reg (directly copied from http://support.microsoft.com/kb/314082 - same as the keys listed by continuum above):

[code]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires atapi.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00

;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
[/code]

Contents of fix_ide_2.reg - this seems to be required to stop requests for vmscsi.sys during mini setup. This file was created using the differences before and after a VMI was run on an imaged virtual drive.
You can also modify the line [code]scsi0.present = "TRUE"[/code] To FALSE in the VMX file for the VM, however as this is set to TRUE by default, I didn't want to have to do this.

[code]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Control\Class{4D36E96B-E325-11CE-BFC1-08002BE10318}\0009]
"InfPath"="keyboard.inf"
"InfSection"="STANDARD_Inst"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,00,2f,0f,ee,2d,c2,01
"DriverDate"="7-18-2002"
"DriverVersion"="5.0.2195.5438"
"MatchingDeviceId"="*pnp0303"
"DriverDesc"="Standard 101/102-Key or Microsoft Natural PS/2 Keyboard"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Control\Class{4D36E96F-E325-11CE-BFC1-08002BE10318}\0009]
"EnumPropPages32"="syssetup.dll,PS2MousePropPageProvider"
"InfPath"="msmouse.inf"
"InfSection"="PS2_Inst"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,40,99,31,33,2e,bf,01
"DriverDate"="11-14-1999"
"DriverVersion"="5.0.2183.1"
"MatchingDeviceId"="*pnp0f13"
"DriverDesc"="PS/2 Compatible Mouse"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Control\Class{4D36E97B-E325-11CE-BFC1-08002BE10318}\0009]
"ProviderName"="VMware, Inc."
"DriverDateData"=hex:00,40,99,31,33,2e,bf,01
"DriverDate"="02-18-2004"
"DriverVersion"="1.2.0.2"
"MatchingDeviceId"="pci
ven_104b&dev_1040"
"DriverDesc"="VMware SCSI Controller"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_104b&dev_1040]
"Service"="vmscsi"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601]
"Service"="isapnp"
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[-HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0303\5&244c37a5&0]

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0303\4&5289e18&0]
"Capabilities"=dword:00000020
"HardwareID"=hex(7):41,00,43,00,50,00,49,00,5c,00,50,00,4e,00,50,00,30,00,33,\
00,30,00,33,00,00,00,2a,00,50,00,4e,00,50,00,30,00,33,00,30,00,33,00,00,00,\
00,00
"Service"="i8042prt"
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"ConfigFlags"=dword:00000000
"Driver"="{4D36E96B-E325-11CE-BFC1-08002BE10318}
0009"
"Mfg"="(Standard keyboards)"
"DeviceDesc"="Standard 101/102-Key or Microsoft Natural PS/2 Keyboard"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0303\4&5289e18&0\Device Parameters]
"FirmwareIdentified"=dword:00000001
"Migrated"=dword:00000001
"KeyboardDataQueueSize"=dword:00000064
"PollStatusIterations"=dword:00000001

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0303\4&5289e18&0\LogConf]
"BasicConfigVector"=hex(a):88,00,00,00,0f,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,01,00,01,00,03,00,00,00,00,01,\
01,00,11,00,00,00,01,00,00,00,01,00,00,00,60,00,00,00,00,00,00,00,60,00,00,\
00,00,00,00,00,00,01,01,00,11,00,00,00,01,00,00,00,01,00,00,00,64,00,00,00,\
00,00,00,00,64,00,00,00,00,00,00,00,00,02,01,00,01,00,00,00,01,00,00,00,01,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"BootConfig"=hex(8):01,00,00,00,0f,00,00,00,00,00,00,00,01,00,01,00,03,00,00,\
00,01,01,11,00,60,00,00,00,00,00,00,00,01,00,00,00,01,01,11,00,64,00,00,00,\
00,00,00,00,01,00,00,00,02,01,01,00,01,00,00,00,01,00,00,00,ff,ff,ff,ff

[-HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0F13\0]

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0F13\4&5289e18&0]
"Capabilities"=dword:00000020
"HardwareID"=hex(7):41,00,43,00,50,00,49,00,5c,00,50,00,4e,00,50,00,30,00,46,\
00,31,00,33,00,00,00,2a,00,50,00,4e,00,50,00,30,00,46,00,31,00,33,00,00,00,\
00,00
"Service"="i8042prt"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"ConfigFlags"=dword:00000000
"Driver"="{4D36E96F-E325-11CE-BFC1-08002BE10318}
0009"
"Mfg"="Microsoft"
"DeviceDesc"="PS/2 Compatible Mouse"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0F13\4&5289e18&0\Device Parameters]
"FirmwareIdentified"=dword:00000001
"Migrated"=dword:00000001
"EnableWheelDetection"=dword:00000002
"MouseDataQueueSize"=dword:00000064
"MouseResolution"=dword:00000003
"MouseSynchIn100ns"=dword:01312d00
"SampleRate"=dword:0000003c
"WheelDetectionTimeout"=dword:000005dc
"MouseInitializePolled"=dword:00000000

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\ACPI\PNP0F13\4&5289e18&0\LogConf]
"BasicConfigVector"=hex(a):48,00,00,00,0f,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,01,00,01,00,01,00,00,00,00,02,\

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01]

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80]
"DeviceDesc"="VMware SCSI Controller"
"LocationInformation"="PCI bus 0, device 16, function 0"
"Capabilities"=dword:00000000
"UINumber"=dword:00000002
"HardwareID"=hex(7):50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,\
00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,00,30,00,34,00,30,00,26,00,\
53,00,55,00,42,00,53,00,59,00,53,00,5f,00,31,00,30,00,34,00,30,00,31,00,30,\
00,34,00,42,00,26,00,52,00,45,00,56,00,5f,00,30,00,31,00,00,00,50,00,43,00,\
49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,26,00,44,00,45,\
00,56,00,5f,00,31,00,30,00,34,00,30,00,26,00,53,00,55,00,42,00,53,00,59,00,\
53,00,5f,00,31,00,30,00,34,00,30,00,31,00,30,00,34,00,42,00,00,00,50,00,43,\
00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,26,00,44,00,\
45,00,56,00,5f,00,31,00,30,00,34,00,30,00,26,00,43,00,43,00,5f,00,30,00,31,\
00,30,00,30,00,30,00,30,00,00,00,50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,\
5f,00,31,00,30,00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,00,30,00,34,\
00,30,00,26,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,00,00,00,00
"CompatibleIDs"=hex(7):50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,\
30,00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,00,30,00,34,00,30,00,26,\
00,52,00,45,00,56,00,5f,00,30,00,31,00,00,00,50,00,43,00,49,00,5c,00,56,00,\
45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,\
00,30,00,34,00,30,00,00,00,50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,\
31,00,30,00,34,00,42,00,26,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,30,\
00,30,00,00,00,50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,\
34,00,42,00,26,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,00,00,50,00,43,\
00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,00,00,50,00,\
43,00,49,00,5c,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,30,00,30,00,00,\
00,50,00,43,00,49,00,5c,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,00,00,\
47,00,45,00,4e,00,5f,00,53,00,43,00,53,00,49,00,41,00,44,00,41,00,50,00,54,\
00,45,00,52,00,00,00,00,00
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="vmscsi"
"ConfigFlags"=dword:00000000
"ParentIdPrefix"="4&5fcaafc&0"
"Driver"="{4D36E97B-E325-11CE-BFC1-08002BE10318}
0009"
"Mfg"="VMware"

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80\Device Parameters]

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80\Device Parameters\Scsiport]
"BusNumber"=dword:00000000
"SlotNumber"=dword:00000010
"LegacyInterfaceType"=dword:00000005

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80\LogConf]
"BasicConfigVector"=hex(a):08,01,00,00,05,00,00,00,00,00,00,00,10,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,01,00,01,00,07,00,00,00,01,01,\
01,00,31,00,00,00,20,00,00,00,01,00,00,00,c0,10,00,00,00,00,00,00,df,10,00,\
00,00,00,00,00,08,01,01,00,31,00,00,00,20,00,00,00,20,00,00,00,00,00,00,00,\
00,00,00,00,ff,ff,ff,ff,00,00,00,00,00,81,01,00,00,00,00,00,01,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,03,01,00,00,00,\
00,00,20,00,00,00,01,00,00,00,00,00,00,f4,00,00,00,00,1f,00,00,f4,00,00,00,\
00,08,03,01,00,00,00,00,00,20,00,00,00,20,00,00,00,00,00,00,00,00,00,00,00,\
ff,ff,ff,ff,00,00,00,00,00,81,01,00,00,00,00,00,01,00,00,00,01,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,03,00,00,00,00,00,00,00,\
00,00,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"BootConfig"=hex(8):01,00,00,00,05,00,00,00,00,00,00,00,01,00,01,00,03,00,00,\
00,01,00,01,00,c0,10,00,00,00,00,00,00,20,00,00,00,03,00,00,00,00,00,00,f4,\
00,00,00,00,20,00,00,00,02,03,00,00,0b,00,00,00,0b,00,00,00,ff,ff,ff,ff

[HKEY_LOCAL_MACHINE\System_00\ControlSet001\Services\vmscsi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:0000001b
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,76,00,6d,00,73,00,63,00,73,00,69,\
00,2e,00,73,00,79,00,73,00,00,00

01,00,01,00,00,00,0c,00,00,00,0c,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00
"BootConfig"=hex(8):01,00,00,00,0f,00,00,00,00,00,00,00,01,00,01,00,01,00,00,\
00,02,01,01,00,0c,00,00,00,0c,00,00,00,ff,ff,ff,ff
[/code]

Contents of Sysprep.inf file:

[code]
;SetupMgrTag
[Data]
MsDosInitiated=No
AutoPartition=1
UnattendedInstall=Yes

[Unattended]
NonDriverSigningPolicy=Ignore
DriverSigningPolicy=Ignore
UpdateInstalledDrivers=yes
DUDisable=No
OemSkipEula=Yes
Hibernation=No
TargetPath=\WINDOWS
UnattendSwitch=Yes
KeyboardLayout=US-International
Repartition=Yes
InstallFilesPath=C:\sysprep\i386

[GUIUnattended]
AdminPassword="AdminPassword"
AutoLogon=Yes
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=290
OemSkipWelcome=1
AutoLogonCount=1

[UserData]
ComputerName=%#!computer@name%
ProductKey= *VOLUME LICENSE KEY HERE*
FullName="User Name"
OrgName="Org Name"

[Display]
BitsPerPel=32
Xresolution=800
YResolution=600
Vrefresh=60
AutoConfirm=1

[Branding]
BrandIEUsingUnattended=Yes

[URL]
Home_Page=http://www.google.com

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=1

[Identification]
JoinDomain="Your domain name here"
DomainAdmin= DA Account Name here
DomainAdminPassword= DA password here

[Networking]
InstallDefaultComponents=Yes

[TerminalServices]
AllowConnections=1

[Components]
msmsgs=Off
msnexplr=Off
freecell=Off
hearts=Off
minesweeper=Off
pinball=Off
solitaire=Off
spider=Off
zonegames=Off

[Shell]
CustomDefaultThemeFile=%WinDir%\Resources\Themes\Royale.theme

[WindowsFirewall]
Profiles=WindowsFirewall.Standard
LogFile=%WINDIR%\pfirewall.log
LogSize=4096
LogDroppedPackets=1
LogConnections=0
Type=8
Mode=1
Exceptions=1
Notifications=1
MulticastBroadcastResponse=1
AllowedPrograms=WindowsFirewall.pcAnywhere_Host
Services=WindowsFirewall.RemoteDesktop
PortOpenings=WindowsFirewall.Port445, WindowsFirewall.Port137, WindowsFirewall.Port138, WindowsFirewall.Port139
IcmpSettings=WindowsFirewall.EchoRequest
Scope=1
Protocol=17
Port=138
Name="File and Printer Sharing"

[RegionalSettings]
LanguageGroup=1
Language=00001409

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist

[Sysprep]
BuildMassStorageSection = Yes

[SysprepMassStorage]
[/code]

Re: Ultimate-P2V Available for Download

AaronM — Thu, 11 Jan 2007 21:20:38 GMT

Oops. You are correct, and that line would be ignored because of the shortened HKLM. Unfortunately I cannot edit my post any longer, but it doesn't seem to make a difference to the VM booting anyway.

Re: Ultimate-P2V Available for Download

continuum — Thu, 11 Jan 2007 20:26:52 GMT

Aaron - I was wondering about the shortened HKLM instead of the long form.

Re: Ultimate-P2V Available for Download

AaronM — Thu, 11 Jan 2007 20:06:16 GMT

Hi Aaron

cool - very detailed explanation - thank you.

There's one line where I don't know if it is ok:
[-HKLM\System_00\ControlSet001\Enum\ACPI\PNP0303\5&244
c37a5&0]

If you read this while you can still edit the post -
please correct it - or is this intentional ?

Hi Ulli

If you are referring to the '-' character at the start of that line, then yes it is intentional - it causes the specified key and all subkeys to be deleted.

I'm not pretending to know what all keys in the file are actually for - as mentioned it was a change made when VMI was run, and I am simply copying what it did.

One question on the sysprep-details. I am not very
experienced with sysprep so the next point may not
apply - I'm not sure ?

What if your P2V-candidate doesn't use Controlset001
but for eample Controlset003 - you can look this up
in
HKEY_LOCAL_MACHINE\SYSTEM\Select

Does sysprep change this so that it allways uses
Controlset001 or do we have to prepare for
translating all the reg-patches ?

Believe it or not I've never uses Sysprep myself either. Most of the details in the inf file are the same as the winnt.sif file for an unnatended xp build, and were simply copied from there. I have read some of the CHM for sysprep, and it doesn't look too complicated. With regard to your question, I'm fairly certain sysprep doesn't have any impact on the controlsets - it certainly doesn't have any entries in the file itself for them. I can't profess to know a lot about what they do either - my basic understanding is that they are used for different hardware profiles? Certainly I thought 001 was always used unless explicitly specified in System Properties. I would imagine that it wouldn't be a problem to do a simple search/replace and generate the reg files for 003 as well as 001?

A last point - do not be afraid to change
scsi0.present to false

This is a VMware default that only makes sense if you
really plan to use SCSI-disks. You really do not need
a SCSI-controller connected to nothing.

You can also set
sound.present to false if that causes any problems
during first virtual boot.
Adding a sound-card to the VM later doesn't change
PCI-slots so you can safely do this at any later
time.

Thanks again for that detailed howto

Ulli

Thanks, I did have a read of your page on the devices and VMX files. I don't have a problem setting it to false with regard to how it affects the machine. My only problem is that I'm creating many machines regularly, and I'll definitely forget to change the setting for a few, then it'll cost me an hour each time as I have to go back and reimage etc. Easier to just inject a few more keys and files and not have to change the VM from it's defaults

BTW you're more than welcom for my post, I couldn't have done it without the help here

Re: Ultimate-P2V Available for Download

continuum — Thu, 11 Jan 2007 14:24:43 GMT

Hi Aaron

cool - very detailed explanation - thank you.

There's one line where I don't know if it is ok:
[-HKLM\System_00\ControlSet001\Enum\ACPI\PNP0303\5&244c37a5&0]

If you read this while you can still edit the post - please correct it - or is this intentional ?

One question on the sysprep-details. I am not very experienced with sysprep so the next point may not apply - I'm not sure ?

What if your P2V-candidate doesn't use Controlset001 but for eample Controlset003 - you can look this up in
HKEY_LOCAL_MACHINE\SYSTEM\Select

Does sysprep change this so that it allways uses Controlset001 or do we have to prepare for translating all the reg-patches ?

A last point - do not be afraid to change
scsi0.present to false

This is a VMware default that only makes sense if you really plan to use SCSI-disks. You really do not need a SCSI-controller connected to nothing.

You can also set
sound.present to false if that causes any problems during first virtual boot.
Adding a sound-card to the VM later doesn't change PCI-slots so you can safely do this at any later time.

Thanks again for that detailed howto

Ulli

Re: Ultimate-P2V Available for Download

RDPetruska — Tue, 09 Jan 2007 23:51:54 GMT

Please give a short summary on how you imported a IDE-box into a IDE-VM ...

I can tell you what I did... I ran UP2V...
1. Create a new VM, with an IDE drive.
2. Follow the UP2V instructions - ghost peer to peer.
3. Once image has been transferred, run the reconfiguration scripts (no need for the SCSI one).
4. Reboot the guest. Done.

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 23:26:01 GMT

Scsi0.present = true means that one of your virtual pci-slots is populated by a VMware-SCSI-controller. This is independant from the question if you really use some SCSI-disks connected to the controller.

So if you do not use scsi-disks - you also do not need that controller.
Be careful - adding or removing this controller also does have unexpected effects on your virtual nics. See my site on vmx > pci-slots if you are interested in the details.

Re: Ultimate-P2V Available for Download

AaronM — Tue, 09 Jan 2007 23:07:36 GMT

No problemo. I am just refining my scripts so they're a little tidier, and I will post a full summary
My VM just asked for vmscsi.sys during mini setup and I had to remove the scsi0.present = true to get past it, and restart. I may have to re-add it, just looking at why it asked for it.

Message was edited by:
AaronM

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 23:04:35 GMT

Hombre - don't expect that we will let you get away with this so easy

Please give a short summary on how you imported a IDE-box into a IDE-VM ...

Ulli

Re: Ultimate-P2V Available for Download

AaronM — Tue, 09 Jan 2007 22:49:16 GMT

Hokay.

I have located the source of ALL my issues. I feel like dying. How embarrasing!

For some reason I had been using HKLM as a substitute for HKEY_LOCAL_MACHINE in all my .reg files. I don't know where I got that idea from, but it DOES NOT WORK!! (although REG LOAD reports a successful import!)

So. Now that I have put the full string into my reg files, the original IDE fix continuum posted above works a treat, with no other vmscsi rubbish required.

Holy hell.. talk about wasting time over something simple!!! I could probably have got this working 3 or 4 days ago if I had realised the issue!

So, I wish to say a massive thankyou to Continuum, and anyone else following this thread who has put up with my ocnfusing nonsensesical posts! Please disgregard everything I have said previously, as it is (now) clearly rubbish!

Message was edited by:
AaronM

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 22:07:24 GMT

First of all - do not use a batch continuum.cmd -

will very likely cure your asthma - but do nothing
really useful

Heh, I beg to differ... at the moment continuum.cmd
works, but boring old massstorage.cmd does not! hehe

Be careful - maybe infectous - first continuum.cmd sabotages your massstorage.cmd and then it cures your asthma

You said you got
scsi0.present = true
in your vmx-file.
Remove it - it is not necessary and maybe the reason why you bluescreen with that SCSI-drivers.

Re: Ultimate-P2V Available for Download

AaronM — Tue, 09 Jan 2007 21:52:27 GMT

First of all - do not use a batch continuum.cmd - it
will very likely cure your asthma - but do nothing
really useful

Heh, I beg to differ... at the moment continuum.cmd works, but boring old massstorage.cmd does not! hehe

Aaron - I'm puzzled on what you do - didn't we wanted
to import the system without useing anything of those
VMware-tools - just you, Altiris, your XP and me ?

You're 100% correct. The only reason I have been using VMI is because it was the only solution which worked. So, I examined what changes the VMI tool was doing, and attempted to replicate it using altiris.

Ok - back to work - if you use VMI you will run into
that SCSI-issue again - I am not aware of any
VMware-tool that imports to IDE.

Apparently VMI (v2 at least?) supports IDE... my default IDE WS machines after being imported are still running on IDE drives...

VMs running on IDE cannot be moved to ESX - so
following the VMware-logic there is no need in
converting to IDE.
Even when you select WS as target - you will get a
SCSI-VM.

I don't think you do get a SCSI vm.. I think it uses whatever the source VM was, and simply injects appropriate drivers.

So you may want to use Altiris only - then just add
those 4 files and merge the reg ...

As above, when doing just that I still get a bluescreen. Not until after I add the vmscsi drivers did it work. Very confusing!

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 21:42:26 GMT

First of all - do not use a batch continuum.cmd - it will very likely cure your asthma - but do nothing really useful

Aaron - I'm puzzled on what you do - didn't we wanted to import the system without useing anything of those VMware-tools - just you, Altiris, your XP and me ?

Ok - back to work - if you use VMI you will run into that SCSI-issue again - I am not aware of any VMware-tool that imports to IDE.

VMs running on IDE cannot be moved to ESX - so following the VMware-logic there is no need in converting to IDE.
Even when you select WS as target - you will get a SCSI-VM.

So you may want to use Altiris only - then just add those 4 files and merge the reg ...

Message was edited by:
continuum

Re: Ultimate-P2V Available for Download

AaronM — Tue, 09 Jan 2007 21:24:10 GMT

I wish I knew! I can only offer an uneducated guess that it is required based on these:

1) There is a line in the .vmx file: scsi0.present = "TRUE" (this is a default so don't want to change it) - there are no other references to SCSI devices, and it lists ide0:0.fileName = "Windows XP Professional-.vmdk" - so the drive is definitely IDE

2) The VMI v2 program injected vmscsi.sys (I know you said that the VMI is geared toward VMware server products, however it specifically has options which list Workstation as one of the products to import an imaged drive for).

3) With just the IDE driver it didn't work. With both it did.

I've had another sucess this morning using my batch file called continuum.cmd (maybe it's in the name? hah) (firm is an altiris command which can copy to unmounted drives (prod)):

[code]
F:\FIRM COPY PROD:Windows\system32\config\SYSTEM F:\Temp

REG LOAD HKLM\System_00 f:\TEMp\SYSTeM
REG IMPORT f:\temp\old\vmdiff.REG
REG IMPORT f:\temp\old\continuum.REG
REG UNLOAD hklm\system_00

F:\FIRM copy F:\temp\system PROD:Windows\system32\config

REM Insert HAL

F:\Firm -force copy "U:\VMware Virtual Platform" prod:Windows\system32
F:\Firm -force copy F:\temp\old\sysprep.inf prod:sysprep\sysprep.inf
[/code]

And another failure after this when I tried to automate the script instead of running it manually. I'm closing in on a solution, but I keep changing too many things at one.. need to slow down but it's hard when there's finally light at the end of the tunnel!

[code]
REM Insert MassStorageDrivers

F:\FIRM -FORCE COPY PROD:Windows\System32\Config\System F:\Temp\%ID%.hiv

REG LOAD HKLM\System_00 F:\Temp\%ID%.hiv
REG IMPORT "U:\%#!computer@prod_name%\MassStorage\fix_ide_01.reg"
PAUSE
REG IMPORT "U:\%#!computer@prod_name%\MassStorage\fix_ide_02.reg"
REG UNLOAD HKLM\System_00
PAUSE

F:\FIRM -FORCE COPY F:\Temp\%ID%.hiv PROD:Windows\System32\Config\System

F:\FIRM -FORCE COPY "U:\%#!computer@prod_name%\MassStorage\*.sys" PROD:Windows\System32\Drivers

PAUSE
[/code]

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 20:24:02 GMT

Why do you need vmscsi driver if you use IDE ?

Re: Ultimate-P2V Available for Download

AaronM — Tue, 09 Jan 2007 20:02:40 GMT

Hokay.. seems I spoke a bit too soon.

Since my initial success yesterday (I think I had VMI'd that image before applying the above reg keys) I've had more failures.

Newly imaged drive + above patch and .sys files = bluescreen.
Take the image that bluescreened, boot to pe again and inject additional reg keys from my before/after VMI snapshots - WORKED. This is a significant milestone as this is the first ever image I've had boot without resorting to VMI

New imaged v-drive, combined all reg keys into one file, copied all .sys files - bluescreen.

New imaged v-drive, import VMI differences keys, then above keys, copied all .sys files - bluescreen.

So... I soldier on. More variations to try, it's frustrating having to reimage every time, but I'm used to it by now!

BTW, here are the reg keys I'm injecting (along with copying vmscsi.sys to c:\windows\system32\drivers):

[code]
Windows Registry Editor Version 5.00

[HKLM\System_00\ControlSet001\Control\Class{4D36E96B-E325-11CE-BFC1-08002BE10318}\0009]
"InfPath"="keyboard.inf"
"InfSection"="STANDARD_Inst"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,00,2f,0f,ee,2d,c2,01
"DriverDate"="7-18-2002"
"DriverVersion"="5.0.2195.5438"
"MatchingDeviceId"="*pnp0303"
"DriverDesc"="Standard 101/102-Key or Microsoft Natural PS/2 Keyboard"

[HKLM\System_00\ControlSet001\Control\Class{4D36E96F-E325-11CE-BFC1-08002BE10318}\0009]
"EnumPropPages32"="syssetup.dll,PS2MousePropPageProvider"
"InfPath"="msmouse.inf"
"InfSection"="PS2_Inst"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,40,99,31,33,2e,bf,01
"DriverDate"="11-14-1999"
"DriverVersion"="5.0.2183.1"
"MatchingDeviceId"="*pnp0f13"
"DriverDesc"="PS/2 Compatible Mouse"

[HKLM\System_00\ControlSet001\Control\Class{4D36E97B-E325-11CE-BFC1-08002BE10318}\0009]
"ProviderName"="VMware, Inc."
"DriverDateData"=hex:00,40,99,31,33,2e,bf,01
"DriverDate"="02-18-2004"
"DriverVersion"="1.2.0.2"
"MatchingDeviceId"="pci
ven_104b&dev_1040"
"DriverDesc"="VMware SCSI Controller"

[HKLM\System_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_104b&dev_1040]
"Service"="vmscsi"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKLM\System_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601]
"Service"="isapnp"
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[-HKLM\System_00\ControlSet001\Enum\ACPI\PNP0303\5&244c37a5&0]

[HKLM\System_00\ControlSet001\Enum\ACPI\PNP0303\4&5289e18&0]
"Capabilities"=dword:00000020
"HardwareID"=hex(7):41,00,43,00,50,00,49,00,5c,00,50,00,4e,00,50,00,30,00,33,\
00,30,00,33,00,00,00,2a,00,50,00,4e,00,50,00,30,00,33,00,30,00,33,00,00,00,\
00,00
"Service"="i8042prt"
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"ConfigFlags"=dword:00000000
"Driver"="{4D36E96B-E325-11CE-BFC1-08002BE10318}
0009"
"Mfg"="(Standard keyboards)"
"DeviceDesc"="Standard 101/102-Key or Microsoft Natural PS/2 Keyboard"

[HKLM\System_00\ControlSet001\Enum\ACPI\PNP0303\4&5289e18&0\Device Parameters]
"FirmwareIdentified"=dword:00000001
"Migrated"=dword:00000001
"KeyboardDataQueueSize"=dword:00000064
"PollStatusIterations"=dword:00000001

[HKLM\System_00\ControlSet001\Enum\ACPI\PNP0303\4&5289e18&0\LogConf]
"BasicConfigVector"=hex(a):88,00,00,00,0f,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,01,00,01,00,03,00,00,00,00,01,\
01,00,11,00,00,00,01,00,00,00,01,00,00,00,60,00,00,00,00,00,00,00,60,00,00,\
00,00,00,00,00,00,01,01,00,11,00,00,00,01,00,00,00,01,00,00,00,64,00,00,00,\
00,00,00,00,64,00,00,00,00,00,00,00,00,02,01,00,01,00,00,00,01,00,00,00,01,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"BootConfig"=hex(8):01,00,00,00,0f,00,00,00,00,00,00,00,01,00,01,00,03,00,00,\
00,01,01,11,00,60,00,00,00,00,00,00,00,01,00,00,00,01,01,11,00,64,00,00,00,\
00,00,00,00,01,00,00,00,02,01,01,00,01,00,00,00,01,00,00,00,ff,ff,ff,ff

[-HKLM\System_00\ControlSet001\Enum\ACPI\PNP0F13\0]

[HKLM\System_00\ControlSet001\Enum\ACPI\PNP0F13\4&5289e18&0]
"Capabilities"=dword:00000020
"HardwareID"=hex(7):41,00,43,00,50,00,49,00,5c,00,50,00,4e,00,50,00,30,00,46,\
00,31,00,33,00,00,00,2a,00,50,00,4e,00,50,00,30,00,46,00,31,00,33,00,00,00,\
00,00
"Service"="i8042prt"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"ConfigFlags"=dword:00000000
"Driver"="{4D36E96F-E325-11CE-BFC1-08002BE10318}
0009"
"Mfg"="Microsoft"
"DeviceDesc"="PS/2 Compatible Mouse"

[HKLM\System_00\ControlSet001\Enum\ACPI\PNP0F13\4&5289e18&0\Device Parameters]
"FirmwareIdentified"=dword:00000001
"Migrated"=dword:00000001
"EnableWheelDetection"=dword:00000002
"MouseDataQueueSize"=dword:00000064
"MouseResolution"=dword:00000003
"MouseSynchIn100ns"=dword:01312d00
"SampleRate"=dword:0000003c
"WheelDetectionTimeout"=dword:000005dc
"MouseInitializePolled"=dword:00000000

[HKLM\System_00\ControlSet001\Enum\ACPI\PNP0F13\4&5289e18&0\LogConf]
"BasicConfigVector"=hex(a):48,00,00,00,0f,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,01,00,01,00,01,00,00,00,00,02,\

[HKLM\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01]

[HKLM\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80]
"DeviceDesc"="VMware SCSI Controller"
"LocationInformation"="PCI bus 0, device 16, function 0"
"Capabilities"=dword:00000000
"UINumber"=dword:00000002
"HardwareID"=hex(7):50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,\
00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,00,30,00,34,00,30,00,26,00,\
53,00,55,00,42,00,53,00,59,00,53,00,5f,00,31,00,30,00,34,00,30,00,31,00,30,\
00,34,00,42,00,26,00,52,00,45,00,56,00,5f,00,30,00,31,00,00,00,50,00,43,00,\
49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,26,00,44,00,45,\
00,56,00,5f,00,31,00,30,00,34,00,30,00,26,00,53,00,55,00,42,00,53,00,59,00,\
53,00,5f,00,31,00,30,00,34,00,30,00,31,00,30,00,34,00,42,00,00,00,50,00,43,\
00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,26,00,44,00,\
45,00,56,00,5f,00,31,00,30,00,34,00,30,00,26,00,43,00,43,00,5f,00,30,00,31,\
00,30,00,30,00,30,00,30,00,00,00,50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,\
5f,00,31,00,30,00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,00,30,00,34,\
00,30,00,26,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,00,00,00,00
"CompatibleIDs"=hex(7):50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,\
30,00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,00,30,00,34,00,30,00,26,\
00,52,00,45,00,56,00,5f,00,30,00,31,00,00,00,50,00,43,00,49,00,5c,00,56,00,\
45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,26,00,44,00,45,00,56,00,5f,00,31,\
00,30,00,34,00,30,00,00,00,50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,\
31,00,30,00,34,00,42,00,26,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,30,\
00,30,00,00,00,50,00,43,00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,\
34,00,42,00,26,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,00,00,50,00,43,\
00,49,00,5c,00,56,00,45,00,4e,00,5f,00,31,00,30,00,34,00,42,00,00,00,50,00,\
43,00,49,00,5c,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,30,00,30,00,00,\
00,50,00,43,00,49,00,5c,00,43,00,43,00,5f,00,30,00,31,00,30,00,30,00,00,00,\
47,00,45,00,4e,00,5f,00,53,00,43,00,53,00,49,00,41,00,44,00,41,00,50,00,54,\
00,45,00,52,00,00,00,00,00
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="vmscsi"
"ConfigFlags"=dword:00000000
"ParentIdPrefix"="4&5fcaafc&0"
"Driver"="{4D36E97B-E325-11CE-BFC1-08002BE10318}
0009"
"Mfg"="VMware"

[HKLM\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80\Device Parameters]

[HKLM\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80\Device Parameters\Scsiport]
"BusNumber"=dword:00000000
"SlotNumber"=dword:00000010
"LegacyInterfaceType"=dword:00000005

[HKLM\System_00\ControlSet001\Enum\PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61aaa01&0&80\LogConf]
"BasicConfigVector"=hex(a):08,01,00,00,05,00,00,00,00,00,00,00,10,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,01,00,01,00,07,00,00,00,01,01,\
01,00,31,00,00,00,20,00,00,00,01,00,00,00,c0,10,00,00,00,00,00,00,df,10,00,\
00,00,00,00,00,08,01,01,00,31,00,00,00,20,00,00,00,20,00,00,00,00,00,00,00,\
00,00,00,00,ff,ff,ff,ff,00,00,00,00,00,81,01,00,00,00,00,00,01,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,03,01,00,00,00,\
00,00,20,00,00,00,01,00,00,00,00,00,00,f4,00,00,00,00,1f,00,00,f4,00,00,00,\
00,08,03,01,00,00,00,00,00,20,00,00,00,20,00,00,00,00,00,00,00,00,00,00,00,\
ff,ff,ff,ff,00,00,00,00,00,81,01,00,00,00,00,00,01,00,00,00,01,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,03,00,00,00,00,00,00,00,\
00,00,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"BootConfig"=hex(8):01,00,00,00,05,00,00,00,00,00,00,00,01,00,01,00,03,00,00,\
00,01,00,01,00,c0,10,00,00,00,00,00,00,20,00,00,00,03,00,00,00,00,00,00,f4,\
00,00,00,00,20,00,00,00,02,03,00,00,0b,00,00,00,0b,00,00,00,ff,ff,ff,ff

[HKLM\System_00\ControlSet001\Services\vmscsi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:0000001b
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,76,00,6d,00,73,00,63,00,73,00,69,\
00,2e,00,73,00,79,00,73,00,00,00

01,00,01,00,00,00,0c,00,00,00,0c,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00
"BootConfig"=hex(8):01,00,00,00,0f,00,00,00,00,00,00,00,01,00,01,00,01,00,00,\
00,02,01,01,00,0c,00,00,00,0c,00,00,00,ff,ff,ff,ff
[/code]

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 14:48:06 GMT

Hi
good news

BTW - that patch from above can be used for almost any IDE-based systems - no matter if it is VMware or whatever. It is useful when you changed the motherboard and want to adjust the system on harddisk to a new board ...
If you need a patch that is taylored for VMware-IDE machines you got to wait for the patchman - this patch is more invasive than the one from above.

Ulli

Re: Ultimate-P2V Available for Download

AaronM — Tue, 09 Jan 2007 01:41:43 GMT

Thanks again continuum!

I can tentatively say that worked! However I applied the reg key to an imaged drive I had already messed with a bit.

Starting over - will let you know what happens when I apply your reg key, copy the drivers and nothing else

Re: Ultimate-P2V Available for Download

continuum — Tue, 09 Jan 2007 00:00:27 GMT

Aaron - check out this reg file ...

(it is an old traditional from the BartPE-builder scene ...)

You do not even have to bother with BartPE.

Just use the Altiris-way you are used to and restore the image to a ide-vmdk.
Then mount the vmdk with Ken Katos vdk.exe like this
vdk open 0 imported.vmdk /rw

Next you run regedit and load the system hive of the windows in the mounted vmdk. Load it to HKLM\system_00 and merge this regfile.
Make sure you got this files in system32\drivers:
atapi.sys,
Intelide.sys,
Pciide.sys,
Pciidex.sys

If any of them is missing expand them from the driver-cabs.

Let me know if you need additional help

[code]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires atapi.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00

;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
[/code]

Re: Ultimate-P2V Available for Download

AaronM — Mon, 08 Jan 2007 23:32:34 GMT

Thanks continuum - your help has been much appreciated so far.

My position wrt IDE is that I'm packaging desktop applications, building desktop machines, and using VMware Workstation (which defaults to IDE disks - I definitely want to leave it on defaults to make it as user friendly as possible).

I'm off to google for that fixide patch in the hope I can modify it for use with altiris images (ghost is out of the question).

I've also reverted back to WS 5.5.2 (was on the 6 beta) as the unknowns of the beta are just too much to deal with at the moment.

Thanks again
aaron

Re: Ultimate-P2V Available for Download

continuum — Mon, 08 Jan 2007 22:21:01 GMT

Aaron - all that VMware-tools are totally ESX-centered. So whenever you use Importer, P2V-assistant or Converter they will convert your IDE-system into a SCSI-based system.

If you really want IDE as the output you are on your own - use ghost and then run the fix-ide-patch that can be found in google - or wait till the end of this week and use the patchman I'm working on .

The disable-list that I talked about - sets all IDE or SCSI-controllers that definetely do not belong into a VM to startuptype = manual.
(well - not all of course - just those that I ever stumbled across)
This makes sure you do not run into a BSOD just because your old physical IDE-controller is still set to come up on boot.
I also started to add all kinds of hardware-monitoring services that make no sense in a VM.

If you do not find that fixide-patch I can send you a copy

Ulli

Re: Ultimate-P2V Available for Download

AaronM — Mon, 08 Jan 2007 22:03:25 GMT

Rob - there are some computers available that migrate
into a IDE-VM without changing anything - this
problem hasn't much to do with wether you build the
BartPE with XP or 2k3.
You will only run into problems - based on the BartPE
build if you are useing XP-sp1 or 2k3-no servicepack
on large disks (larger than 130Gb)

I build my BartPE disk with 2k3 R2, the image'd .vmdk is only 1.8GB - didn't work

This morning I tried the following which has worked in the past, but now doesn't work for me anymore:
Created a brand new VM, and imaged with my usual Altiris image.
Shut down the VM
Ran VMI v2 (ended up running VMI inside an XP VM, as it doesn't seem to like Vista) (reported successful import).
Booted the VM again - bluescreen

I also looked at and noted the differences in the file structures and registry of the pre and post VMI process. Copied relevant registry settings and files out.

Interestingly the only new file was VMSCSI.sys (I'm so confused about this right now - I thought the virtual drive was IDE).
There were a number of new registry entries which I also copied.

I haven't bothered attempting to manually apply these differences to an imaged virtual machine as as mentioned, the VMI'd machine bluescreened.

Talk about going round in circles... now I can't even get VMI to work when it did before!

continuum :

The concept of the Disable List is new to me. Where does this reside/How does it work?

I can show you an export of the key you mention, but it is huge.. perhaps I could email it rather than pasting it here?

Re: Ultimate-P2V Available for Download

continuum — Mon, 08 Jan 2007 16:45:08 GMT

Rob - there are some computers available that migrate into a IDE-VM without changing anything - this problem hasn't much to do with wether you build the BartPE with XP or 2k3.
You will only run into problems - based on the BartPE build if you are useing XP-sp1 or 2k3-no servicepack on large disks (larger than 130Gb)

Re: Ultimate-P2V Available for Download

dtdionne — Mon, 08 Jan 2007 16:38:14 GMT

Mike, i think its cause of the 304859303950339458 gazillion issues with scsi vm disks and the 0 issues with ide vm disks but that's just my opinion.

oh, and the fact that esx does not come with a ide drive option.

Re: Ultimate-P2V Available for Download

RDPetruska — Mon, 08 Jan 2007 16:32:31 GMT

AaronM:
I built a UP2V disc a few months ago, and ran it on my wife's new PC to image it into a VM. IDE drive. Worked perfectly. I believe I built the ISO with 2K3-SP1... if you're using XP instead, YMMV.

Re: Ultimate-P2V Available for Download

continuum — Mon, 08 Jan 2007 13:46:31 GMT

Extract atapi.sys, intelide.sys, pciide.sys and pciidex.sys from the latest cab and import critical device database, service and enum-settings ...
Also disable all other ide-controllers like via-ide ...

Does it work ? - all my trials worked. Depends on the quality of your disable-list.
If you want to help in improving it - I need exports of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

BTW - if you only need IDE-support for CDroms - you can skip pciidex.sys

Re: Ultimate-P2V Available for Download

Mike_Laverick — Mon, 08 Jan 2007 09:10:54 GMT

Hi there,

I've been lurking on this thread about IDE drives - but not stepped in a for a simple reason... I've never had this problem, and I'm at a lost to know why you would need a special driver for an IDE drive... (Ulli?)

Perhaps this contractor who figured it all out is the best bet...?

Regards
Mike

Re: Ultimate-P2V Available for Download

AaronM — Mon, 08 Jan 2007 00:29:57 GMT

Working on a tool that works for IDE-disks as well
and will run from WinPE
http://sanbarrow.com/moa2/a3.jpg

Check my site occasionally

Looks promising! Do you have injection working and no bluescreen on reboot with ide? Would love to test/see the files/keys you are injecting!

Re: Ultimate-P2V Available for Download

continuum — Sun, 07 Jan 2007 23:39:14 GMT

Working on a tool that works for IDE-disks as well and will run from WinPE
http://sanbarrow.com/moa2/a3.jpg

Check my site occasionally

Re: Ultimate-P2V Available for Download

AaronM — Sun, 07 Jan 2007 20:49:00 GMT

OK, I understand your position...

I guess to stay on the right side of M$ you
technically supposed to license the BartPE disk,
where you don't with WinPE... (nuts I think, but
that's M$ for you)

To answer you question... you download and unzip the
various pluggins - the cmd files and reg files are
there to view... if that doesn't help you - I could
try get Qui Hong who wrote fix-vmscsi to tell you
more...

Regards
Mike

Hi Mike, happy new year

I've been bashing this some more over the last three days, with no success. Had a contractor in just before christmas, who made a couple of tweaks to our base image, and got it working with this modified base. Unfortunately I didn't take close note of what he modified (have emailed to find out) but it proves that I should be able to use the existing image, modify while in bartpe/winpe and get it going. I definitely don't want to have to use the modified image for virtual builds, and the original for physical.

Anyway, after re-reading the UP2V docs some more, it would appear that there is no driver for use with an IDE disk setup in VMware WS (this is the default disk type). I went to the trouble of creating a BartPE disk exactly as documented, and worked through the process with my imaged VM disk.
This may have been my problem all along, and I was tempted to try using a SCSI disk but for the fact I have this image (created by contractor) which does work with the IDE disk.

I did work through the cmd files, and combined with this KB article from MS, I have a fairly good understanding of what they're doing now, but it just won't boot. Definitely one of the most frustrating things I have come across in IT!

http://support.microsoft.com/kb/314082

Would appreciate any further input here from Qui Hong or yourself.

Cheers
Aaron

Re: Ultimate-P2V Available for Download

continuum — Wed, 03 Jan 2007 20:50:11 GMT

Did you ever tried to launch the depending services manually before tring to start diskmanagement or diskpart ?

I have in mind
net start rpc
net start rpcss
net start dmadmin

Re: Ultimate-P2V Available for Download

dtdionne — Wed, 03 Jan 2007 19:34:14 GMT

Wow....this issue is rapidly closing in on the most frustrating IT issue I have ever had.

I have tried 2003 ent/std bart images with and without "RpcSS needs to launch DComLaunch Service first - SP2 Only" enabled.

I have tried 2003 w/sp1 ent/std bart images with and without "RpcSS needs to launch DComLaunch Service first - SP2 Only" enabled.

What in the world could I be doing wrong?

Re: Ultimate-P2V Available for Download

continuum — Wed, 03 Jan 2007 01:01:28 GMT

Do you got the dcom-launch plugin activated ?

Should be part of recent pebuilder downloads

Sorry for that account issue - had lots of troubles with spam recently - your user should have access now

Ulli

Just to make sure:
you need dcom-launch plugin for 2k3-sp1 and higher
you have to disable it for 2k3 no servicepack

Message was edited by:
continuum

Re: Ultimate-P2V Available for Download

dtdionne — Wed, 03 Jan 2007 00:22:59 GMT

I just made a bart image from Server 2003 Standard pre SP1 and I am still getting the:

"Diskpart encountered an error starting the COM services"

I thought a pre sp1 2003 server source solved all of these issues....what am I missing?

Re: Ultimate-P2V Available for Download

dtdionne — Wed, 03 Jan 2007 00:19:42 GMT

I tried the links but the site says that my account is inactive and there is nothing more I can do...is that your site? If so, my user id is the same as it is here, dtdionne...could you reactivate me?

Re: Ultimate-P2V Available for Download

continuum — Tue, 02 Jan 2007 17:26:29 GMT

Drivers for BartPE / VMware
based on XP
http://ubcd4win.com
based on 2k3
http://sanbarrow.com/phpBB2/viewtopic.php?t=161

Re: Ultimate-P2V Available for Download

dtdionne — Thu, 28 Dec 2006 01:15:27 GMT

Shew...sorry for venting. On the bright side, I would not have believed someone if they would have told me that I would have been capable of getting up n brushing myself off this many times.

Here is my config...

ESX 2.5.2 Build-16390
3.06 HT enabled proc
SuperMicro Gen 5 mobo
16 GB RAM
500GB RAID 5
3 10/100/1000 Eth - 2 for VM's ,1 shared
4 2003 server VM's
1 2003 SBS Server VM - this is the one crushing me

Virtual Infrastructure 2.0.0 Build-27704
VirtInfra Server @ 172.20.0.56/24
VirtInfra Client @ 172.20.0.42/24
ESX 2.5.2 Server @ 172.19.0.62/24 Shared Interface
EXS 2.5.2 VM's @ 192.168.0.20 and 40/24

My issue stems from the fact that I don't have physical access, and all I have is a copy of the SBS 2003 DVD on a hard drive. Therefore, here is what I am attempting:
1. Booting my new SBS VM with a BartPE ISO as the CDROM.
2. Maping a drive to the shared SBS Directory
3. Launching the winnt32.exe install executable

It works great until it can't find the drive so I figured that I would "fdisk and format" the drive with bartpe and that is where I am...

I am unable to see the virtual scsi hard drive....

Please help....this should be cake

Message was edited by:
dtdionne

Re: Ultimate-P2V Available for Download

dtdionne — Tue, 26 Dec 2006 14:16:00 GMT

Chud,

I have the same issue...been fighting it for awhile now. I've actually worn out 3 Server 2003 disks.

I don't think anyone REALLY knows what the hell is going on...i would be hard pressed to find another technical subject this fortified wth such a high concentration of missinformation.

It's a damn joke...i will say this....in my ~11 years of working with vmware products I have NOT ONCE had EVEN ONE SINGLE ISSUE with the IDE drivers....

scsi can go on down and work with the devil

Re: Ultimate-P2V Available for Download

RDPetruska — Tue, 19 Dec 2006 17:55:45 GMT

It's on his forum area...
http://sanbarrow.com/phpBB2/viewtopic.php?t=161

Re: Ultimate-P2V Available for Download

brian1967graham — Tue, 19 Dec 2006 17:50:19 GMT

Got a basic driver pack for 2k3-sp1 built BartPE on
my site - it contains all VMware related stuff - get
it , put it into the drivers-dir and rebuilt

Went to http://sanbarrow.com/ which I assume is your site but couldn't find the basic driver pack for 2k3-sp1. Please post the link to the driver pack.

The CD I attempt to use has not has sp1 slipstreamed in, from what i read that's not a requirement. Could the reason my process isn't working is becuase I'm using standard 2k3 and not one with sp1 included?

Re: Ultimate-P2V Available for Download

continuum — Tue, 19 Dec 2006 06:53:13 GMT

Got a basic driver pack for 2k3-sp1 built BartPE on my site - it contains all VMware related stuff - get it , put it into the drivers-dir and rebuilt

Re: Ultimate-P2V Available for Download

brian1967graham — Mon, 18 Dec 2006 18:04:48 GMT

need the LSI folder here since I'm using 2k3 right?
I tried it both ways with same behaviour. I don't
see the VM SCSI Disk so I can't load the
image...help!

I think you do need the LSIlogic driver copied to the BartPE cd drivers location >>otherwise BartPE can't load the controller driver to read your disk. Hence your >>disk is missing... even if you have used W2K3 as the source of your BartPE >>disk - i think you still need to do this...

Thanks for the fast reply Mike. I have tried with, just the LSI driver in the bartpe build directory structure. then just the VMScsi driver in the bartpe build directory structure, and both in the bartpe build directory structure.

I'm sure this is where I am messing up but I can't determine how to verify this. I look at the bartpe build messages and see what appears to be the appropriate messages indicating that the drivers are being picked up from the directory structure during the process. Is there anyway to see what drivers are being used once booted into the cd? This should be the simplest part of the process...very frustrating Also if I am unclear on what is happening or where I have put the drivers what else can I provide here to help clear things up?

I am looking on the the new vm migration tool with no success yet but I tried it once late last night then went to sleep.

Thanks...

Re: Ultimate-P2V Available for Download

Jusin_Kase — Mon, 18 Dec 2006 15:34:34 GMT

Thanks Mike

Very much appreciated.

J

Re: Ultimate-P2V Available for Download

Mike_Laverick — Mon, 18 Dec 2006 08:59:53 GMT

need the LSI folder here since I'm using 2k3 right?
I tried it both ways with same behaviour. I don't
see the VM SCSI Disk so I can't load the
image...help!

I think you do need the LSIlogic driver copied to the BartPE cd drivers location otherwise BartPE can't load the controller driver to read your disk. Hence your disk is missing... even if you have used W2K3 as the source of your BartPE disk - i think you still need to do this...

Regards
Mike

Re: Ultimate-P2V Available for Download

brian1967graham — Sun, 17 Dec 2006 17:51:44 GMT

This product and the documentaiton is really pretty good. I am having one major problem and can't figure it out. When I boot up the VM from the CD (.iso image actually) everything boots fine but I don't see the vm's SCSI disk so I can't create the VM Instance using the ghost image I created.

I don't see anyone else with this problem so possibly it's simple. I am using Win2k3 CD and double checked that I have the vmscsi folder in "prebuilder\drivers\scsiadapter\vmscsi". I don't need the LSI folder here since I'm using 2k3 right? I tried it both ways with same behaviour. I don't see the VM SCSI Disk so I can't load the image...help!

Thanks.

Re: Ultimate-P2V Available for Download

Mike_Laverick — Wed, 13 Dec 2006 17:19:47 GMT

This is diskpart error is a known issue. If the source of the BartPE disk is Windows XP. It doesn't happen with W2K3.

Your suppose to be able to start a disk management service in XP which make diskpart work. But I've never had this work...

The problem can be resolved by reboot... but diskpart with W2K3 removes this unnecessary reboot... so its an M$ issue more than P2V issue per-se...

Regards
Mike

Re: Ultimate-P2V Available for Download

GR — Wed, 13 Dec 2006 12:38:50 GMT

The solution is great, but with me it does
not work. I think the problem is that the diskpart ends in an error. The
bartpe recognizes the partition c: and its stuff and I can add the
buslogic driver for my win2000 vm but booting it still results in the
blue screen

In detail I
- used the acronis true image boot cd to restore the image of the
physical machine (win 2000 SP4)
- run "Set Disk0 and Partition1 to be C: " giving "Die
Datentraegerverwaltungsdienste konnte den Vorgang nicht abschliessen."
sorry its in german, must be something like "disk adminstration services did
not complete"
- add vmscsi(buslogic) ... with successfull results

I have no ideas what went wrong

Re: Ultimate-P2V Available for Download

chuss — Thu, 30 Nov 2006 23:16:34 GMT

Mike,

I wonder if the UltimateP2V project is very popular? It looks like 26,000+ people have read this thread. How many other threads can say that?

Chris

Re: Ultimate-P2V Available for Download

RDPetruska — Wed, 22 Nov 2006 18:59:33 GMT

Mike - I successfully used UP2V with Workstation (5.5.1 or 2 at the time - can't remember which) to clone my wife's new Win XP Home computer, and I used virtual IDE disk. Zero problems. Of course, I skipped the vmscsi step as I was using IDE.
Rob

Re: Ultimate-P2V Available for Download

Mike_Laverick — Wed, 22 Nov 2006 18:26:54 GMT

UP2V was not tested under VMware Workstation - although we have many reports of its successful use.

If you want to UP2V on Vmware workstation - you must use a SCSI not IDE virtual disk. Could this be the problem?

You might also now want to register for the beta of the new tool from vmware called - VMware Convertor. When this product ships it will be FREE for non-bulk conversions...

Regards
Mike

Re: Ultimate-P2V Available for Download

rainey — Tue, 21 Nov 2006 22:10:32 GMT

I am running VM workstation 5.5.2 and have not got the UP2V disk to work for me.

This is what dose work and it works very well.

I make an image of a running PC with acronis True Image 9.1 to my USB drive.
I make a new VM with a drive as bag as the partition i made the image of.
I boot to the TI9.1 boot CD, and under the tools menu i setup my network IP.
Then is start the restore and under computer near me i find the shared folder when the image is stored and select it.
Select the destination partition, (this did not require and special drivers so far).
I restore the image at about 1gig per minute.
I reboot and use a Partition program to make sure the restore drive is marked active. I also sometime edit the boot.ini to correct the boot partition number if needed.
I then run the VMware importer V.2 on the VM.
Then i boot to the VM and it plugs and plays all the drivers. You must not reboot to soon as it will keep install drivers, just cancel the video driver (found new hardware) prompt.
Then install the VMtools and reboot.

This has worked great for me.

Re: Ultimate-P2V Available for Download

Mike_Laverick — Fri, 17 Nov 2006 09:45:29 GMT

OK, I understand your position...

I guess to stay on the right side of M$ you technically supposed to license the BartPE disk, where you don't with WinPE... (nuts I think, but that's M$ for you)

To answer you question... you download and unzip the various pluggins - the cmd files and reg files are there to view... if that doesn't help you - I could try get Qui Hong who wrote fix-vmscsi to tell you more...

Regards
Mike

Re: Ultimate-P2V Available for Download

AaronM — Fri, 17 Nov 2006 02:30:29 GMT

Thanks Mike

Unfortuantely being a large corporate we're never going to sway toward BartPE. Besides which we have invested heavily in the Altiris product and need to use the images it creates given we have them in a production environment.

We have tried the VMWare converter, and it failed to convert the VM imaged from our Altiris created image. We have also used the VMware machine importer, which was successful but there is no command line interface available which limits us in terms of automation.

Everything that is achievable in bartpe is definitely achievable in winpe. All I need is a breakdown and explanation of the scripts and regkeys used in the fixvmscsi plugins.

Reagards
Aaron

Re: Ultimate-P2V Available for Download

Mike_Laverick — Thu, 16 Nov 2006 10:27:11 GMT

Firstly, UP2V is untested on WinPE. So I would try remove that from the list of variables and use BartPE and see how you get on...

Secondly, i think i got muddled up. At the end of page on my website I mention:

http://www.mechrest.com/plugins/

But these are Acronis, not Alteris plug-ins... (neither system I have used - so hence the muddle up)...

Lastly, a couple of weeks ago VMware release for FREE, the beta version of VMware Convertor (VMWare P2V+Importer combined). When the product goes GA it will also be FREE.... so I would recommend looking at that in the first instance, and only using UltimateP2V if you

a.) prefer it
b.) VMware Convertor doesn't work for you...

Regards
Mike

Re: Ultimate-P2V Available for Download

AaronM — Thu, 16 Nov 2006 02:27:59 GMT

Hi everyone. I'm relatively new to VMware, but I am a fast learner.

I'm trying to build a new VM from an Altiris image taken from a physical machine. The image is WinXP.

Mike - above you mention you have links to Altiris plugins on your RTFM site - but I had a scout around and couldn't find them?

My process goes like this:

1) Altiris boots the VM to WinPE
2) While in WinPE download and image the virtual hdd using aforementioned Altiris image from physical pc
3) Still in WinPE, inspect machine type and inject appropriate driver
package to C:\drivers on the vm's C drive
4) Still in WinPE sysprep and restart - boot to XP

5).... bluescreen of death - identified as hdd driver issue by reading on this forum..
http://img.photobucket.com/albums/v441/evobit/vm_error.jpg

I've read through the documentation for UP2V (although I haven't worked through it), and it appears to be basically doing exactly what I have above, using BartPE instead of WinPE.

So what I need to know is exactly how to identify what drivers I need to inject, and any registry keys which need updating on the VM. These steps seem to be automated in the BartPE plugin, and I don't know how to get at them to dissasemble and understand/implement for my situation. I have tried various combinations of the drivers in the UP2V package, and different types of virtual hdd's (scsc/ide) with no luck. I'm probably doing something basic wrong, but until I fully understand the automated steps the bartpe plugins perform, I'm stuck!

Re: Ultimate-P2V Available for Download

Mike_Laverick — Wed, 18 Oct 2006 12:10:10 GMT

unfortunately, we don't offical "do" linux P2V.... however, I think if you installed your linux drivers (buslogic/lsilogic) it would work - to be honest you don't really need our vm-fixscsi plug-in to do this...

If you would like to script and add support for linux to ultimateP2V we would be interested...

Regards
Mike

Re: Ultimate-P2V Available for Download

petjez — Wed, 18 Oct 2006 11:59:44 GMT

I've used UltimateP2V to image a Linux disk to a VMDK. But how can i insert the linux VMware drivers now. Or is Linux not supported. I like to convert my Linux host to a VM..

Regards,
Patrick

Re: Ultimate-P2V Available for Download

chud — Sun, 15 Oct 2006 15:37:40 GMT

Hi,

I get the following error with Rajeev's DISKPART plugin [Diskpart functionality in Win2k3 - SP1 only] (on page2) using SP1 source:

''Diskpart encountered an error starting the COM services''

I also tried using diskpart.exe from non SP1 with same error.

Any ideas?

Re: Ultimate-P2V Available for Download

Hal Styli — Sat, 30 Sep 2006 20:18:50 GMT

IDE P2Vs confession....

I have done a few Ultimate-P2Vs now but I'm getting
probably the 2nd most common problem and it's
stumping me.

I retried it with an IDE vmdk and it worked...
I should only P2V when I need to!

Hal.

Re: Ultimate-P2V Available for Download

Mike_Laverick — Mon, 25 Sep 2006 13:18:17 GMT

Hi there,

On the ultimatep2v site...

www.rtfm-ed.co.uk

there are some links where you can download plug-ins for Altris... they are not hosted on rtfm-ed but we have links to them... so you could use Altris to clone a DL, and then the FixVMSCSI to solve the boot disk problem...

Regards
Mike

Re: Ultimate-P2V Available for Download

lonelyjp — Mon, 25 Sep 2006 08:12:11 GMT

What if I already have Altiris images of a couple of DL360s and there's no way to retake image using Ghost? Is there a way to use Ultimate P2V in order to deploy the images to a VM? (When I deploy without Ultimate P2V, I get an INACCESSIBLE_BOOT_DEVICE whenever the VM boots)

Please help!

Thanks.

-Steve

Re: Ultimate-P2V Available for Download

hadaak — Sat, 23 Sep 2006 22:05:14 GMT

Hi All,

Haven't read all the post but I have a small detail to add.
I had a black screen after restarting a P2Ved ghosted physical image into a vm. Of course I ran the fixvmscsi tool. I had to do a restorembr.exe (ghost 9 tool) to boot normally.
So If you can just add an mbr restore to your tool it would be helpful. Of course I don't know the impact on all kinds of P2Ved configuration. Mine was a Proliant 5500.
Thanks for the great job.

Re: Ultimate-P2V Available for Download

chuss — Thu, 21 Sep 2006 18:32:52 GMT

Thanks Qui, for all of your contributions to this project. Little did we all know how well the UltimateP2V project would take off and be so widely used and accepted.

Glad to see you're still out there and doing well.

Chris

Re: Ultimate-P2V Available for Download

quihong — Thu, 21 Sep 2006 17:00:16 GMT

Hello all,

Just wanted to drop in and say hi. I quite suprise how many hits this thread got and very happy that Ultimate P2V is so popular.

I switched position at my current company last year and haven't been very active with VMWare but I still try to keep up with the technology. If we ever get a Forum site up for Ultimate P2V, I will surely participate.

Thank Chris and Mike for putting Ultimate P2V together. Keep up the good work.

Qui

Re: Ultimate-P2V Available for Download

quihong — Thu, 21 Sep 2006 16:59:56 GMT

Re: Ultimate-P2V Available for Download

notorious_bdg — Thu, 21 Sep 2006 14:59:38 GMT

Try replacing the HAL with the ACPI Uniprocessor PC HAL using the Recovery Console method on http://support.microsoft.com/kb/237556/.

Re: Ultimate-P2V Available for Download

chuss — Thu, 21 Sep 2006 14:18:21 GMT

Hal,

Is it possible to mount that vmdk as a secondary drive in another VM...so you can run a chkdsk /f and defrag on that drive? It might help.

Chris

Re: Ultimate-P2V Available for Download

Hal Styli — Wed, 20 Sep 2006 16:49:29 GMT

Sorry to bring up my usual fetish of IDE P2Vs again but....

I have done a few Ultimate-P2Vs now but I'm getting probably the 2nd most common problem and it's stumping me.

I think I have done it by the book: I ghosted a bog standard desktop Win2k IDE machine, created a vm with scsi vmdk, restored the image and ran the buslogic related p2v tools. On starting the VM, I get a hang at the 'starting up...' screen with 10 bars.

There are quite a few references to hangs on the same screen on google and in these forums. I think I have checked all of the recommendations but there's always a chance I missed a couple.

I am convinced that I have done this before succesfully using the same procedure.

Any clues?

Thanks for any help given
Hal

Re: Ultimate-P2V Available for Download

williambishop — Sun, 10 Sep 2006 01:24:53 GMT

You crazy kids are going to end up replacing p2v and saving us big dollars at the rate you're going.

Re: Ultimate-P2V Available for Download

chuss — Thu, 31 Aug 2006 02:29:39 GMT

That would be great! If we had a way to add the fixvmscsi plugin to your PBA...we'd have a P2V solution that we could freely distribute.

Chris

Re: Ultimate-P2V Available for Download

rxhui — Wed, 30 Aug 2006 21:21:55 GMT

Yes, you should be able to use PBA in place of ghost, but at present, that is, in the current version, it's a two step process. You backup the physical server over the network to the PBA VM and the backup is stored in a set of files, then you restore to a VM over the network, and the VM disk is written with the contents from the archive stored on the PBA VM. When I started work on PBA, I never considered adding a peer to peer cloning option without going through a server first because that would not necessitate having the PBA server VM at all, but now that I think about it some more, I could add this feature as a client only option. In fact, I've used this technique in other tools that I put together in my day job, so it's definitely do-able. It would work something like this. You boot from the client CD in the physical system, then you boot from the client CD in the VM. Then on the physical system, you invoke the peer-to-peer cloning option and specify the IP address of the VM. It's on my list for the next version of PBA.

Re: Ultimate-P2V Available for Download

chuss — Wed, 30 Aug 2006 18:23:03 GMT

If PBA could do a peer-to-peer image from the physical server to the VM....then we really wouldn't need Ghost anymore.

Chris

Re: Ultimate-P2V Available for Download

rxhui — Wed, 30 Aug 2006 14:45:47 GMT

FWIW, I've used ultimate-p2v successfully on clones made with my Personal Backup Appliance VM (instead of Ghost), but I don't know how well it will do across a wide range of configurations. I'm interested in knowing if it works for you (or if it doesn't work for you).

Hard Disk Backup and Restore Walk-through using PBA (updated with new screenshots)
http://canned-os.blogspot.com/2006/08/hard-disk-backup-and-restore-using-pba.html

P2V - Virtualizing an existing OS install using PBA
http://canned-os.blogspot.com/2006/08/p2v-virtualizing-existing-os-install.html

Re: Ultimate-P2V Available for Download

Jasemccarty — Mon, 28 Aug 2006 15:27:31 GMT

You are right there with the fact that the VMImporter won't handle .gho files.

And it needs both the .v2i and .sv2i files to import.

I had a similar issue, where I used our Corporate version of Ghost (8.x), and I had to use the Ultimate P2V. It worked 100% as described, actually much better than the VMware P2V product.

Re: Ultimate-P2V Available for Download

benducklow — Mon, 28 Aug 2006 15:16:38 GMT

Yeah, just now I tried. I DL'd the beta vmimporter, isnstalled and tried after I saw your post on this thread... The VMImporter doesn't see my *.gho files, only *.sv2i format. (I am using Ghost 8.x). If you have another way to do this, I'd appreciate to know about it!

Thanks!

Re: Ultimate-P2V Available for Download

Jasemccarty — Mon, 28 Aug 2006 15:13:30 GMT

If you already had a Ghost image, did you attempt to use the VMImporter?

It will take a Ghost image, and convert it to a VM for you.

Re: Ultimate-P2V Available for Download

benducklow — Thu, 24 Aug 2006 19:50:07 GMT

I was hoping someone can help me out. I have been put to task on converting a Win2k ghosted image (in it's sysyprep'd state) to a VM Workstation machine. I have been pulling my hair out because I am so close. I am following the instructions but as soon as I boot up the VM after its been tweaked with the FIMVMSCSI directions, the machine will lock-up at the W2k Pro splash screen.

Is there something I am missing? Please let me know if I can provide any other details, screenshots.

I've messed out with changing the VM settings; I just haven't seen any posts on doing a W2k machine specifically.

Thanks in advance for any assistance!

Ben

Message was edited by:
benducklow

I got this to work by changing my vm disk set to the LSILogic SCSI setting. Then after the ghosting process, I inserted the matching driver (LSILogic SCSI) via the FIXVMSCSI. Thought I would share my 12 hour struggle with you. I though you were not supposed to use the LSILogic setting?

Re: Ultimate-P2V Available for Download

nick.couchman — Mon, 21 Aug 2006 20:46:54 GMT

Fantastic - this product works great for me! I've P2V's Windows NT4 and Windows Server 2003 so far with this without any problems at all!

Re: Ultimate-P2V Available for Download

Mike_Laverick — Fri, 04 Aug 2006 02:21:09 GMT

Cheers...

I will check these out - also had a private message about a free PHP forum site...

Regards
Mike

Re: Ultimate-P2V Available for Download

krismcewan — Thu, 03 Aug 2006 09:26:36 GMT

Hi Mike

as per our discussion in the clas in Dublin here is the link to the forum software i have used.

www.Fusionbb.com

i know it costs but you do get what you pay for and the support with these people is spot on.

Re: Ultimate-P2V Available for Download

continuum — Wed, 02 Aug 2006 19:39:56 GMT

You are invited to settle down here ...
http://sanbarrow.com/phpBB2/

Ulli

Re: Ultimate-P2V Available for Download

Mike_Laverick — Wed, 02 Aug 2006 18:55:18 GMT

Hello,

I think a new forum rather than a single thread is
needed for Ultimate-P2V then posts like this won't
cut into the current thrust of this thread - which is
quite interesting incidently.

Yes, I've been looking into some free forum provider - with "stick FAQ's" - instead of hogging VMware's forums... but been too busy to sort this out

Regards
Mike

Re: Ultimate-P2V Available for Download

Hal Styli — Wed, 02 Aug 2006 17:46:13 GMT

Ok Thanks.

I should have done that first rather than rely on my memory!
I'm off to RTFM agen.

Hal

Re: Ultimate-P2V Available for Download

Hal Styli — Wed, 02 Aug 2006 17:12:04 GMT

Hello,

I think a new forum rather than a single thread is needed for Ultimate-P2V then posts like this won't cut into the current thrust of this thread - which is quite interesting incidently.

Anyway as we don't have a whole forum, here is my query...

It's a bit of a newbieish query I fear and by coincidence involves subst'd drives....

It's a while since I used Ultimate-P2V but I seem to remember that the steps were broadly:-
1) using bartpe/up2v, ghost your physical box (lets assume it runs xp) to say x:\yyy
2) create two empty vmdks, say xprestored.vmdk and temp.vmdk
3) copy the ghost image files from x:\yyy into temp.vmdk
4) using bartpe/up2v in a vm, ghost the files from temp.dsk onto xprestored.vmdk
5) scsi fix xprestored.vmdk
6) boot xprestored.vmdk

I wondered if it would be possible to change 3) and 4) to:-
3) subst z: x:\yyy
4) using bartpe/up2v in a vm, with z: showing as a physical disk, ghost the files from z: onto xprestored.vmdk

I guess I want to access a subst'd folder as if it were a real drive.
Is it possible? If so, is it dangerous given that it would only ever be read from?

The advantage is time and space since temp.vmdk is simply a wrapper for the ghost image files.

Thinking about it again, Perhaps using a virtual network and share would be best?

Thanks for all help given.

Hal.

Re: Ultimate-P2V Available for Download

RDPetruska — Wed, 02 Aug 2006 17:19:00 GMT

Actually, if you follow the UP2V guide, there's no reason to create a ghost image and save it anywhere - use peer-to-peer network image, and cut out the middle step (and space). As far as the forum - since the UP2V is not a VMware product, that's highly unlikely to happen.

Re: Ultimate-P2V Available for Download

continuum — Wed, 19 Jul 2006 01:53:48 GMT

B_Mann

you seem to be proceeding in the direction of using BartPE as an alternate workspace.

That's not what I'm interested in. Would take years to get there with BartPE where Knoppix is now ....

I'm interested in VMware with BartPE.
I think it is possible (and not very far away) to go to a physical box, boot it with BartPE and then run the original physically installed OS inside a VM as demonstraion for a customer.
I'm interested in having a system that has the tools to do vmdk-repair.
I'm interested in having a CD that you could use as VMserver emergency replacement.

I don't know and in a way don't care if anybody can use this as I do this just for fun.

Then I thought that you guys might be able to use something of this?
On the other hand I'd like to know if this stuff works on Enterprise-hardware as well - so use it or ignore it ...

About the driveletters: it is really not that simple ... ever tried to create a pagefile on a ramdrive? - if you use it like a fixed disk you can consider doing stunts like that ...

Ulli

Re: Ultimate-P2V Available for Download

EZP2V — Tue, 18 Jul 2006 22:40:07 GMT

Ulli,
If I understand you right, you seem to be proceeding in the direction of using BartPE as an alternate workspace. What I mean by that is that instead of simply using BartPE as a utility CD, you want to actually run applications as you would from your desktop. Although I see a value in this, I think this should be kept separate from an automated P2V solution. A focus should be made at providing a clean P2V solution and perhaps a parallel effort be made to create a self-supporting application operating environment.
But to change the drive letter for the %ramdrv% or %temp%, simply change the value for the RamDiskDriveLetter setting in the plugins\ramdisk\ramdisk.inf file from

RamDiskDriveLetter="B:"

to

RamDiskDriveLetter="R:"

I would recommend that any reference to this be through the environment variable (%ramdrv%). That way it does not matter what the drive letter is changed to.

B-Mann

Re: Ultimate-P2V Available for Download

continuum — Tue, 18 Jul 2006 21:24:00 GMT

Hi Clay - nice to hear from you again

subst b: R:\temp
as it would be in my case ...
Yep you can do this - but I don't like a redirection for a redirection as I often create a junction from R:\temp to some local disk ... hmmm does subst work in this case?

Clay - try this: create a VM with 2 disks.
Use driveletter X: for the first and R: for the second.
Install XP-sp2 or 2k3-sp1 into "X:\sbin"
Configure the system so that you have

"R:\home" instead of "X:\documents and settings",
"R:\programs" instead of "X:\program files",
"R:\temp" instead of X:\sbin\temp"

Then layout your BartPE that it uses

X:\sbin for the readonly Windows-directory from CD
R: for the RAMdrive
R:\temp
R:\home
R:\redologs
R:\programs

After BartPE start mount a vmdk (NTFS compressed containing all programs) as Q: in undoable mode with Ken Katos vdk.
Create a junction from R:\programs to Q:

Now you can enjoy a fully writeable programs-directory - no more copying complete directories into RAMdrive when all you need to write to is just a ini-file.
All changes go into a small REDOlog in the RAMdrive - this way I was able to run things like dreamweaver from BartPE - without copying 100MBs dreamweaver-files into RAMdrive.

With the customized regular install with the same layout I can build a startmenu by dragging icons ... adding stuff is much easier now.

I guess you agree that useing the same layout for BartPE and buildSystem makes a lot of sense ...
Useing B: for %temp% and RAMdrive makes all this impossible - without offering any advantage to compensate this.

If you ask me - the BartPE-plugin system is about to kill itself soon - it started good but the plugin-creators missed the point where they should have setup standards or simplify radically.
I tried to start a discussion about a year ago but gave up after some months.
Big parts of the BartPE scene regard running stuff like VMware or Dreamweaver as kind of crime against the spirit of BartPE.
"... don't wake up sleeping dogs by useing this for more than just system repair"

If you look at the scene now you will see a dimished interest in the forum - looks like Reatogo is going to swallow all active users sooner or later.

Now Reatogo is good for users but not for plugin-authors. I wanted to make a VMplayer plugin for Reatogo some time ago - in 3 evenings I had the VMplayer running but 2 months later of hacking with reatogo-explorer-shell I lost interest.

Oops - this is starting to become offtopic
Clay - I hope you can see why I don't like workarounds like subst ...

Ulli

Re: Ultimate-P2V Available for Download

ClayMon — Tue, 18 Jul 2006 19:50:43 GMT

Ulli:

How about using the SUBST command. I just tried this and it worked on my XP machine.

subst b: c:\temp

Thanks

Re: Ultimate-P2V Available for Download

continuum — Tue, 18 Jul 2006 17:46:00 GMT

I would go ahead and do what you need to do...

Sure - I'll do that though this can be boring sometimes ...

certainly U2PV doesn't use these sort of directories ...

Mike this is not correct - your BartPE certainly uses %temp%.
Last time I looked at out-of-the-box-BartPe %temp% points to the RAMdrive-letter which is usually B:

If you change %temp% from B: or %ramdrv% to R:\temp you will find that many plugins no longer work. You will have to look thru every plugin you use and eventually change paths.
I believe even Reatogo still uses B: for the ramdrive like UBCD4WIN and Sherpya.
I tried to discuss this in the BartPE-forum but this question is discussed with almost religious attitude and I thik that BartPE mainstream will continue to use B:

If you ask me this is very stupid. You cannot assign B: to a harddisk which means your temporary writeable area must use a RAMdrive or a Floppy.
The result: mainstream needs to write a plugin to add simple programs like selfimage to a new built.
I can add selfimage to my built with simple drag and drop. The BartPE-scene didn't liked that at all .... don't ask me

Mike - I feel honoured when you invite me to set standards but you really should think twice before you leave wellknown ground.

But we should agree on some conventions for the system-patching-tools we develope.

Lets think modular: it should be possible to use my rawdisk-trick and then use the U2PV-LSI-patch and finally use Peter's cleanup-bat.
Brings us back to the questions: automatic or wizzard and what is the target?

What do you think about a concept like this ...

1. go to any box - physical, parallels, virtual server, vmserver whatever
2. select the windows-directory to work with
3. run an analysis of the system and create a standardized report
4. set the target - I think this should be a vmx-file (not limited to ESX or SCSI only)

(report and vmx-file make a job. Once you know the job the wizzard reads a standardized options.ini - if this ini says
[transport]
ghost8-available = yes

the wizzard offers this as a transport option.
If selfimage-available = yes or dd-available = yes the wizzard will offer this as well.

This will work with some standardizations:
a subdir of the wizzard would be named ghost8 and would need a start-transport.cmd. Now when we always move disk OMEGA2 to NEWHOME for example we can work with transport-plugins.

When we can agree on a common layout we can create plugins like "LSI-2-ESX-2ksp4" or "VMwareSVGA-2-VMserver-2k3" and so on.

All patching tools read the report - to find out what services to disable and reads the vmx to find out which drivers to inject.

I think of the vmx as a system-description in general here - maybe one day we have a line like ethernet0.virtualDev = "parallels_networkcard".

In case we can agree on a layout we should also consider to start thinking about some kind of forum where the wizzard can sent his report and check if for the target-vmx already a clean-up patch exists ...
Recently I added install-rite to my bartPE and with a tool like this you can even consider having a wizzard-learn-mode.
Consider you have 20 boxes of the same kind: you create the report, the vmx and then set the wizzard to learn-mode. Install-rites creates a snapshot of the system 2 move before you start patching it. Then you do the first box manually - maybe by trial-and-error- or voodoo or whatever. Once it works you creaye a second snapshot and have install-rite sum-up the changes.

Ok - this is getting a long post - I sum it up a bit:

let's define some standards - so that I can use your clean-up scripts, you can use my ide2scsi-vmdk-processing, and we both can use the scripts of "EZP2V" or whoever writes some smart stuff next week.

We should agree on a format for a standardized report file, for a standardized target-vmx and some ini-stuff.

Next we should define some breakpoints in the complete job - like :
source-analysis
transport
vmdk-processing
file-injection
reg-patching
reg-clean-up
and so on ...

Mike - you told me to go ahead and do what I need to - and you are right.

But - it is simply more fun to walk together ...

Ulli

Re: Ultimate-P2V Available for Download

Mike_Laverick — Tue, 18 Jul 2006 08:08:12 GMT

Mike - I just noticed that I can fully automate the
process so that it would be possible to have a
startmenu entry with options like this:

Ulli, I would go ahead and do what you need to do... certainly U2PV doesn't use these sort of directories - so why don't you set the standard which the rest of us will follow...?

Regards
Mike

Re: Ultimate-P2V Available for Download

DanBw — Mon, 17 Jul 2006 23:38:47 GMT

Hi Alex,
Can you confirm that when you created your VM that you chose SCSI as the interface rather than IDE?

Re: Ultimate-P2V Available for Download

alexisb — Mon, 17 Jul 2006 21:09:16 GMT

I'm having a couple of issues with this setup.

I am using the trial version of VMWorkstation 5.5.1 and a virtual machine based XP Pro SP2 as the OS I'm trying to clone.

I'm using the Ultimate P2V plugs, and the LSILogic SCSI driver.

I'm able to get past step 8, so I have a good base VMware image but I'm unable to boot into XP Pro. I get a STOP 0x0000007B blue screen.

I noticed on this site:
http://www.911cd.net/forums//index.php?showtopic=17381

That the stop message is from not finding the correct drivers however I have tried either the VMSCSI and the LSILogic drivers to no avail, I still get a bluescreen.

Is there something in the version of VMWorkstation that I'm using, since it's the trial ed, that disallows changes to the virtual machine images?

Any pointers anyone can lend would help

Re: Ultimate-P2V Available for Download

continuum — Fri, 14 Jul 2006 22:21:51 GMT

Mike - I just noticed that I can fully automate the process so that it would be possible to have a startmenu entry with options like this:

convert physical drive 0
convert physical drive 1
convert physical drive 2
convert physical drive 3
convert physical drive 4
convert physical drive 0 - partition 1 only
convert physical drive 1 - partition 1 only
convert physical drive 2 - partition 1 only
convert physical drive 3 - partition 1 only
convert physical drive 4 - partition 1 only

Can we agree on some conventions?
It would help to have some fixed locations where we can store temporary files on BartPE.

I have

R:\temp > the usual %temp% dir
R:\vm\vmware > installation directory for WS or VMserver
R:\vm\machines > directory for virtual machines

If I automate this I would add a raw-disk to the VM
R:\vm\machines\bogus\bogus.vmx

The raw-disks would be named and stored like this
R:\vm\machines\bogus\physicaldisk0.vmdk
R:\vm\machines\bogus\physicaldisk1.vmdk
...

I would convert them to
R:\vm\export\physicaldisk0-converted.vmdk
...

R:\vm\export would be a junction to a networkshare mapped to a driveletter or a traveldisk or some local drive ...

Remember you can always junction the directories to a different location ...

Ulli

Re: Ultimate-P2V Available for Download

RDPetruska — Fri, 14 Jul 2006 12:44:43 GMT

Give me some time - the VMserver release came one
week earlier than I had expected.

Really? It came a week later than I had expected. Based on all the user license keys expiring on July 13, I expected that VMware would give everyone at least a week or two to get the new licenses.