Adding Coldclone converter to WinPE 3.0

[dr_demento]

I'm trying to add the Enterprise version of ColdClone Converter to my windows PE 3.0 build, and am running into issues. I'm hoping someone has some Ideas.

I started by looking at this article: and tried adjusting it for my build. I have all the files moved into PE, and created this script:

__________________________________

rem vmware converter launch command

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinPE\Features" /v Pnp /t REG_DWORD /d 1 /f

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinPE\Features" /v Icf /t REG_DWORD /d 1 /f

drv_ctl --inst-nostart vstor2-converter X:\VMWARE-CONVERTER\vstor2-converter.sys

net start vstor2-converter

net start cryptsvc

start /min X:\VMWARE-CONVERTER\vmware-converter.exe -r vmware-converter -x 1 X:\VMWARE-CONVERTER\converter.xml

ping localhost -n 5

net start vmware-converter-1

start X:\VMWARE-CONVERTER\converter.exe -boot

____________________________________________

When running, I'm getting an Application error for VMWARE-CONVERTER.EXE (Screenshot below)

I'm hoping someone has tried to do similar, or that I've missed something simple that someone will notice.

[continuum]

what exactly do you mean by "your WinPE 3.0" ?

by the way - I wrote that instructions for MOA - I think that you will miss some dependancies in PE 3.

Thats why I want to know which one ...

Ulli




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[dr_demento]

I'm using Windows PE 3.0 Basically following this: http://technet.microsoft.com/en-us/library/dd799244(WS.10).aspx

[dr_demento]

I've gone through depends and added all the missing .dll, but still am getting the error. Perhaps a driver I'm missing? Has anyone been able to get coldclone converter working in a microsoft windows PE environment?

[continuum]

any special reasons you want to use PE 3 ?

the BartPE I use for the MOA coldclone CD is pretty nice - it allows to add drivers after boot which is a must-have for a coldclone CD IMHO.

At the moment I see no reason to change the platform.

Anyway - if you post the converter startup batch you use now I may be able to help.

Ulli

___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[dr_demento]

Thanks, here is the startup batch I'm using after looking at yours:

-

---

rem vmware converter launch command

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinPE\Features" /v Pnp /t REG_DWORD /d 1 /f

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinPE\Features" /v Icf /t REG_DWORD /d 1 /f

drv_ctl --inst-nostart vstor2-converter X:\VMWARE-CONVERTER\vstor2-converter.sys

net start vstor2-converter

net start cryptsvc

start /min X:\VMWARE-CONVERTER\vmware-converter.exe -r vmware-converter -x 1 X:\VMWARE-CONVERTER\converter.xml

ping localhost -n 5

net start vmware-converter-1

start X:\VMWARE-CONVERTER\converter.exe -boot

[continuum]

does drv_ctl work in PE 3 ?

did you check if the services are really created ?




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[dr_demento]

I believe the service is created, I'm getting no errors (See screenshot) and the I can find it in the registry.

[continuum]

looks good so far

in latest MOA I use a different command to start the ufad service - I have to look it up in my code ...




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[continuum]

by the way - this problem was already solved by Joachim

see http://communities.vmware.com/docs/DOC-9800




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[marklanglcs]

I am attempting the same thing as Dr_Demento and running into similar issues. I have followed Joachim's instructions, using Converter 3.0.3 with his loader and now I am receiving a Visual C++ Error. All of the dll files are in the proper place and the service appears to start properly as well. Joachim's method says that he has it working on VistaPE and Server 2008, which is helpful but not the right answer needed for WinPE 3, which is based on the Windows 7 core. I have tried an older version of Converter and the version of Converter that is on the VMWare Cold Clone Boot WinPE 1 disc, and it produced a different error message than the Visual C++ Error.

From what I can tell based on some of the other converter problems, it might be a problem with the environment or a variable that is not set. All of the variables appear to be there, however, so I am at a loss for a solution.

To answer an old question you had continuum, WinPE 3 adds a LOT of functionality to the PE environment over Bart/UBCD (based on WinPE 1.x) and much more functionality over WinPE 2 (based on Vista/Server 2008).

Thank you both for starting this conversation, as there really isn't any other information current on the subject out there.

[continuum]

WinPE 3 adds a LOT of functionality to the PE environment over Bart/UBCD ...

only advantage in PE 3 that I can see is 64 bit support - other then that what do you have in mind ?

personally I still use my own MOA build (heavily modified BartPE) for P2V and see no reason to change.

It runs all versions of Converter and Workstation and vspshere - client - so it has everything you need for this task.

being able to add drivers after boot is very nice ...




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[marklanglcs]

Most of the drivers in WinPE are preloaded, and for the most part all you need is LAN drivers to function. 64 bit functionality is nice, but I use WinPE for both USB and CDROM booting on PCs as well as part of our Windows Deployment Services we use to image our machines in the office. Hot-swappable USB is great, too, as I can add or remove USB devices as needed (and don't need to include them at boot time). I understand that this feature is possible in UBCD, but not Bart.

The WIM file used in WinPE loads very quickly, and offers a slight extra level of security of the contained programs over Bart's option of leaving everything in plain sight.

You are absolutely right, though, for your uses, there really is no reason to change. Unless for some reason your Bart disc doesn't load for newer computers, there isn't any reason to switch.

Dr. Demento, it seems like everything should be working fine so that it isn't a problem with VMWare but possibly a missing pointer or registry entry in WinPE.

[continuum]

hot swapable USB works nice here too




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[dr_demento]

Thank guys for your replies, I'm still at a loss. I've tried Joachim's instructions and am still coming up with errors.

I'd like to stick with WinPE 3 as I have a lot of tools and automation in the build that are working currently and would like to continue to build on that.

[continuum]

then you may have to wait for a Converter version that supports Windows 7 hosts ?

AFAIK this does not even work on regular Windows 7




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[marklanglcs]

The version of Converter that supports cold cloning (based on Joachim's build) - version 3.0.3 - can run on Windows 7, so I don't think that is the problem.

Continuum, do you have any VisualC or DotNet plugins enabled in your WinPE? Reading up on the VisualC++ 2005 Redistributable and other internet posts about it, everything looks to tie back to DotNet. DotNet doesn't work in WinPE (without heavy hacking), so that might be part of the problem. If you enabled it in your BartPE, that would at least explain why it might work for you but not for us.

[continuum]

hey - you are right - I do not need dotnet to run Converter - but all my builds have the visualC runtime.

I only start dotnet support for vsphere client.

So maybe it helps to make the installation of the runtime the first action in the converter start batch




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[marklanglcs]

What are you using to call the Visual C runtimes? I found something for Bart but it simply adds one line to the registry. Is your method more involved than that?

The assistance is greatly appreciated!

[continuum]

one line in registry ? - that will not do it.

I use one line too - but in the startup batch - this line executes an Installrite-package with the runtime.

You could also use a cmd that installs it silently.




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook