I needed to convert a physical Windows XP Professional machine running ZENworks into a VMware virtual machine, but only after removing the unique identifiers like the Windows’ SID and ZENworks’ GUID, so that I could later make multiple copies of the VM without them all writing to the same ZENworks object. After weighing my options, I decided that it wouldn’t be practical to hot clone the physical machine. The best method would be to unregister the ZENworks object, uninstall the Adaptive Agent, pull it off the network, reinstall the Adaptive Agent, and then sysprep -reseal -shutdown the machine. This would leave me with a hard drive with a XP installation ready to generate new IDs the next time it was powered on. But as you well know, the VMware vCenter Converter Standalone app can only perform P2V hot cloning.
Cold cloning requires the VMware Cold Clone Boot ISO, which is only available to VMware Converter Enterprise license-holders. After some Googling around, I came across this thing called, Multi-Operating system Administration. Basically, it creates a LiveCD that runs the free VMware Converter on top of a Windows Server 2003 kernel. It’s very, very nice and developed by an obvious super-genius. Just how cool is it?
How about the ability to boot a physical box and start the originally installed system as a virtual machine? Here are the steps I took to build my free cold clone boot CD. Creating the cold clone boot CD This builds a LiveCD using Windows Server 2003 that can then run VMware vCenter Converter Standalone 3.0.3 (previously known as VMware Converter Starter Edition) in order to cold clone a hard drive. Caveats The version of Windows running in the LiveCD should be the same as, or later than, the version of the Windows machine you want to convert to a VM. VMware recommends, when cold cloning using their boot CD, that the source physical machine have 364MB of memory, with a minimum of 264MB.
MOA recommends, for the Bandit version ISO, that the physical machine have at least 512MB and preferably 1GB or more. Required files Download moa241-setup.exe (2.7MB) from You will need to sign up at the forums to gain access to the download. Download X13-05665.img (596MB) (Windows Server 2003) from Download VMware-converter-3.0.3-89816.exe (30.1MB) from Put all three files in the same folder (with no spaces in the folder name) on a NTFS-formatted disk. MOA will refer to this as the ‘building directory’.
Assemble the ISO Run moa241-setup.exe. In the application menu, click moa - create MOA core. If you have put the X13-05665.img file into the root of the building directory, MOA will extract the files automatically.
If the X13-05665.img file is in a different location or if you are using a different OS to build the LiveCD, MOA setup asks for the location of your Windows-sources. This must be a 32-bit OS, like XP or Server 2003. If you have the files on a CD or mounted using Daemon-tools, just select the drive letter; if you have them extracted somewhere on your hard disk, point to the directory one level higher than the I386 directory.
The MOA setup app asks a few questions about the environment you want to build. Answer these very quickly, as they appear to have a default answer which will be selected automatically after a very short timeout (maybe like 10 seconds). The MOA setup runs a nifty little DOS app that downloads another 20.34MB of core files. It will ask if you want to download drivers, which is another 17MB download.
After another few questions, it runs PE Builder v3.1.10a. The MOA setup then asks if you want to install VMware Converter 3.0.3 (the default is no, so quickly click yes). After which, it asks you if you want the converter to autostart (default is no, which is fine). A standard image ISO is created automatically. You can also create a Bandit image ISO, which seems to be what most people use.
In my case, the standard image is 374,622KB, while the Bandit image is 296,810KB. The Bandit version should also be faster than the standard version. The ISO files are saved to iso-out. Burn to CD or DVD using whatever method you prefer. Booting from the LiveCD When booting from the Bandit image, you will get the following message, “can’t find vmware – starting plan B”, which makes it seem like something is wrong.
An Open File dialogue box then opens in the ramdisk vm folder and displays “can’t find vmware files in default location – please select a different path”. It’s looking for a Workstation or VMware Player installation here, not the Converter. Just click Cancel.
Another Open File dialogue box will open, stating “still can’t find VMware – you may want to mount a wim”. Click Cancel again. After a few more seconds, MOA will be finished booting up and the GUI will minimize. Click the taskbar button to open it back up, then right-click the button with the image of the desktop PC with the VMware logo on the screen and select “start converter” from the menu. A Browse for Folder dialogue box will open. Browse to X:/moahome/vm/converter/ and click OK.
VMware Converter will launch. If things are not going as expected, the developer has made a video tutorial showing a boot into MOA followed by a cold cloning operation, located at I saved my new virtual machine to a second physical disk, then put that drive into another machine with VMware Server 1.0.9 already installed and copied over the three vm files. I started VMware Server and clicked Open Existing Virtual Machine, but when I tried to add the new vm to the inventory, VMware Server Console popped up an error: Unable to add virtual machine “D:Virtual Machinescoldclonetestcoldclonetest.vmx” to the inventory.
Configuration file was created by a VMware product with more features than this version. Some quick Googling led to the fix: Open the virtual machine’s two 1 KB configuration files in a text editor. In the.vmx file, change virtualHW.version = '6' to virtualHW.version = '4' In the.vmdk file, change ddb.virtualHWVersion = '6' to ddb.virtualHWVersion = '4' After I made those changes, the virtual machine powered on and booted into XP, running all the expected install scripts and generating unique Windows and ZENworks identifiers. I’ve also successfully cold cloned a Windows 2000 machine using the same boot CD. MOA on a bootable USB drive If you would prefer to use a bootable USB drive instead of a LiveCD, here are some tips for getting MOA onto a USB drive: This entry was posted in, and tagged, on.
Post navigation. Ken Almond I’ve been struggling to convert my old laptop with XP into a VM for permanent archival/access.
After many IDE ‘driver’ explanations with no solution, I ran accross this article. All went well with this article until I kept getting 34KB.iso(s) that would not boot – AGH. download it manually from this link: and put it in the directory where you initially put moa241-setup-v3.exe and your problem should be solved! This comment (above) saved me and it worked and I WAS SUCCESSFUL in creating an XP VM running unter VMware Player 5.0.1.
BTW – I tried MOA under 32-bit Windows 7 and 64-bit Windows – 7. Didn’t make any difference.
I was successful under 64-bit Windows 7 with the pebuilder3110a.zip added to my working dir. Thanks to you-all. Its a few years, at least 10 attempts to get this and today I succeeded!
It's been some time since I last used winbuilder and all the other tools referenced here in the forum. But I am facing a difficult task and I remembered reboot.pro could have the solution to my problem. VMware used to have a BootCD for their vCenter Converter tool but unfortunately it was discontinued since version 4.3 (current is v5.x). I know that vCenter Converter Standalone can be installed on the any system that I wish to convert to virtual but somehow our credentials don't allow us to install software on this particular server (not even Windows updates). Worse than that, we've been told that if we find a way to install anything on this server we will void the maintenance contract.
Accounting software server. We reeeeally don't want to mess with our accounting software. So we checked with them and they don't see any problem in converting the system to virtual. So our only hope is to build a BootCD with network support that could run vCenter Converter 5.x. Does anyone know how we could do that? Thanks in advance.
I guess I am confused, since AFAIK, to even get the OS (you didn't say, but I'm guessing it is a windows flavor'd OS that runs the accounting SW) to run on virtual HW, you would have to install drivers and such.So wouldn't that also change the image. Maybe give us more background on what server it is, etc.
Couldn't you create the Virtual server, and give it a pretty big (empty) disk, and then use cloning SW (think GHOST or other more modern equivelents) to copy the disk image over to the virtual disk? But as I said above, in my experiance, the issues with getting it to boot and non-trivail when going to all 'virtual' devices. Maybe someone else here has any 'bright' ideas. I guess I am confused, since AFAIK, to even get the OS (you didn't say, but I'm guessing it is a windows flavor'd OS that runs the accounting SW) to run on virtual HW, you would have to install drivers and such.So wouldn't that also change the image.You know, I hadn't thought about that. Indeed, when the VM is booted on the hypervisor it will immediately start uninstalling old drivers and ask for new drivers. That has almost the same impact (not to say a whole lot more impact!) than installing a small vCenter agent that has been tested by hundreds of thousands of companies for over the last 5 years. I will keep that in mind but to make it more clear, we didn't simply install vCenter agent because those guys from the accounting software are pussies and said they would drop support on us.
And they have agreed to support the product in a VM. So I honestly don't care as long as we can make the conversion and that it works properly. Maybe give us more background on what server it is, etc.Sure. The old server is a Windows 2003 Standard (before R2). It has 2 PSU units but 1 of them has failed and since it is a 'white label' hardware we can't find spares. So we really need to either migrate the OS and software to a new hardware or convert it to virtual and add it to our VMware cluster.
Now, the software is very old and was discontinued. At the proper time we didn't opt to migrate to a new platform. Now we have a system whose hardware can suddenly become a huge paper-weight and whose software is stopped in time back in 2005. We are already working ( since 2 years ago) on a new accounting software and server but we need to keep old data available for historical and legal reasons for another 6 years.:? Couldn't you create the Virtual server, and give it a pretty big (empty) disk, and then use cloning SW (think GHOST or other more modern equivelents) to copy the disk image over to the virtual disk?In the past we've tried doing that on a couple of occasions and it didn't work out for us.
Lots of errors and lots of red crosses in device manager after the VM booted. That has never happened with any of the P2V conversions that we've done using vCenter Converter. You can try PWBoot.Thanks for the hint, TheHive.
I will surely take a good look at PWBoot. Hope it allows me to install software. Thanks to both for your replies. Also take a look at: ETBoot, Boot your full Windows installation from CDDVD-ROM project can create a real bootable Windows Live CD/DVD, so you will be able to use full installation of Windows operating system on CD/DVD without installation. Tested working Windows version list:. Windows XP (5.1 Build 2600 - SP2, SP3).
Windows Fundamentals for Legacy PCs (5.1 Build 2600 - SP2). Windows Server 2003 (5.2 Build 3790 - SP1, SP2). Windows Code Name 'Longhorn' (6.0 Build 4051) Possible working Windows version list:. Windows XP (5.1 Build 2600 - SP0, SP1, SP2, SP3).
Windows Fundamentals for Legacy PCs (5.1 Build 2600 - SP2). Windows Server 2003 (5.2 Build 3790 - SP0, SP1, SP2). Windows Code Name 'Longhorn' (6.0 Build 35514094). Windows Home Server (5.2 Build 4500). I can sympathize with the dilemma! I would also look at Disk2VHD, but if you have missing drivers, they will have to be mapped or updated.
I'm guessing that the vCenter tool does a lot of that for you, but no matter what, the basics of the underlying HW (real to emulated) will change somewhat. Here is link to article on it. I am guessing best approach might be to use some other bootable OS image to 'clone' the disk onto a separate hard-drive, then play with that one - i.e. Attach that cloned drive to another computer to run the disk2vhd conversion, then see if you can boot that drive. Keep us posted.
The new Converter Standalone 5 lacks the Converter Boot CD. Fortunately you can still use the old version 4.1 Converter Boot CD, which is also compatible with vSphere 5! The Converter Boot CD is available for download on the VMware website, although you will need an Enterprise license. I thought it would be good idead to create a short feature comparison between Converter Standalone 5 and the Boot CD.
Update:You can find this tool on my page. I’ve added a direct download link from my folder there. I’m not sure that the original link when this article was written still works. I hope you will find it useful. On the Free tools page, there are not only VMware utilities, but also Microsoft or other freeware which admins uses on they day to day routine.
We’re trying to maintain that page in order to provide high value for virtualization and IT community. Why Would You Need VMware Cold Clone ISO? You cannot do a every time.
Sometimes you need to perform a cold clone to convert your physical servers in order to capture a “dead” state of the server, with all services, software, DBs shut down. It’s sometimes difficult to VSS an application running on a physical server if that particular application was written ages ago. Then you’re asking, where to get the converter cold clone boot CD? So, there exists the cold-clone disc. This is a bootable CD-ROM disc that you actually boot the physical server from.
The disc contains a pre-installed Windows 2003 image that runs a built-in version of Converter. Since you boot from the CD, none of the server’s processes start-up so you can get a good clone of the hard drive.
This website is maintained. Vladan is as an Independent consultant, professional blogger, vExpert 2009 - 2018, VCAP-DCA/DCD, VCP. ESX Virtualization site has started as a simple bookmarking site, but quickly found a large following of readers and subscribers. Visiting Indian Ocean and Reunion Island? My wife Nicole and I just opened our B&B with private jacuzzi. Check it out!
![]()
AloeveraBeach - Rent a Flat 300m from the beach. Capacity 4 pers. Feel free to network via Twitter.
Hi Robin, Check out this KB To download the VMware Converter Boot CD: 1. Under Datacenter Downloads, click VMware vSphere 4. Scroll to the licensing arrangement that matches your entitlement (for example, Essentials Plus). Click View History beside the link that reads VMware vCenter Server 4.1 Update 1 and modules. Click VMware vCenter Server 4 Update 1 or VMware vCenter Server 4 Update 2. Note: The Converter Boot CD is not directly available under vCenter Server 4.1. You must go to one of the listed update links. In the Components section, click Show Details. This displays in the list: VMware vCenter Converter BootCD File size: 98.8 MB File type: zip MD5SUM: 3df94eb0e93deada2a3799 SHA1SUM: 5d7c04e4f9f8ae25adc8de5963fefd8a4c92464c 7.
General tolerances iso 2768. General Tolerances to DIN ISO 2768. • The latest DIN standard sheet version applies to all parts made to DIN standards. • Variations on dimensions without. Mechanical Tolerance Chart Data. General ISO Geometrical Tolerances Per. NOTE: Nominal Diameter 250 mm. Table of Hole Tolerances ISO 286. ISO 2768 for the following: Linear Dimensions, External Radius and Chamfer. Preferred Tolerance Grade Zones ISO 286 ISO 286 Table Shaft Tolerances. NOTE *Complete ISO System of Limits and Fits is now stored a CD KOK ISOTOLTM. TABLE 6-2 PREFERRED HOLE BASIS CLEARANCE FITS (ANSI B4.2).
Click Download. Enter your appropriate portal access details, then read and accept the EULA. When you accept the EULA, you are presented with download instructions.
Hirens Boot Cd Download
Download the appropriate file (at time of writing, this is a 98.8MB.zip file). Unzip the file and burn it to a CD/DVD. C&c red alert 3 please install at least one language pack. This is your Converter Boot CD. Subject RE: VMware Gurus:1638 - Sco open server 5.0.5 physical to vertual Migration Hi, Thanks a lot Ankit.but where I can get vCenter converter boot CD( VMware vCenter Converter 3.0.2 Update 1 Enterprise Edition). It is asking license when I trying to download. Regards Robin From: On Behalf Of Ankit Mehrotra Sent: Saturday, July 16, 2011 2:49 PM To: Robin Joseph; Subject: RE: VMware Gurus:1637 - Sco open server 5.0.5 physical to vertual Migration Hi Robin, sco open server is not a supported source type for hot conversion using vCenter Converter. You need to cold clone the physical machine using vCenter converter boot CD. Beforehand, make sure the server is in state that it will come up when rebooted J Thanks & Regards, Ankit Mehrotra ENTERPRISE ARCHITECT 504,Paharpur Business Centre, 21, Nehru Place Greens, New Delhi-110019 Office + 7764 / 63 Mobile +7787 From: On Behalf Of Robin Joseph Sent: Friday, July 15, 2011 10:04 AM To: Subject: VMware Gurus:1632 - Sco open server 5.0.5 physical to vertual Migration Hi, Need help to migrate sco open server 5.0.5 to virtual.
I have one sco open server 5.0.5 installed HCL net infinity 9 year old server, how can I migrate the system to vmware 4.1 environment. Thanks and Regards Robin Joseph Nortech infonet pvt ltd, cochin, kerala Cell: - You received this message because you are one of the few 'Gurus' on VMware technology who can make a difference. To post to this group, send email to To unsubscribe from this group, send email to Robin Joseph 17/7/2011, 21:20 น.
Hi Santosh; You can download vCenter Converter BootCD ISO image from below link: esx-DVD-4.1.0-260247.iso File size:659M File type.iso ESX 4.1 (DVD ISO) Boot your server with this DVD in order to install ESX 4.1. NOTE: VMware ESX 4.1 and ESXi 4.1 require 64-bit capable servers for installation and execution. Please refer to the VMware Compatibility Guide for a list of qualified server hardware. MD5SUM:8dca1352a42dab842af30749636f73d1 SHA1SUM:297d9e28565217fb790907cfb4a66b5ea9c6fb5d Hope this helps you. Hello Santosh, Your required information is provided at page 13 on the VMware vCenter Converter Standalone User's Guide ( ). Excerpts: Prepare for Cold Cloning Because Converter Standalone 4.3 and later do not support cold cloning, you must use the Boot CD of an earlier vCenter Converter edition. The features supported on the Boot CD depend on the product version you choose.
When you cold clone a machine, you reboot the source machine from a CD that has its own operating system and also includes the vCenter Converter application. You can find a detailed description of the cold cloning process in the documentation of the Boot CD you decide to use. VMware vCenter Converter 4.1.x is not a free software product. Procedure 1 To obtain a Boot CD, go to the VMware Download Web site and download the vCenter Converter 4.1.x installation package. 2 Extract the Boot CD.iso file from the installation package.
3 Write the Boot CD.iso file on a CD. What to do nex Follow the onscreen instructions to proceed with cold cloning After the installation of the Converter you will get the iso files in the following location (If you have done installation at the default location): Install to the default location, then look here: C: Program Files VMware VMware vCenter Converter Standalone Look for the converter-helper-vm.iso and converter-helper-vm-x64.iso So, 1. You will not get the iso files in the latest converter standalone product. VMware Converter 4.1.x is not a free product.
Free Windows Xp Boot Cd Download
After the installation you need to get the iso files for the above mentioned location. Please let me know if you need more information. From: mailto: On Behalf Of Ajit Kundan Sent: Monday, July 02, 2012 9:03 AM To: Santosh Agrawal; Subject: RE: VMware Gurus:1878 - Sco open server 5.0.5 physical to vertual Migration Hi Santosh; You can download vCenter Converter BootCD ISO image from below link: esx-DVD-4.1.0-260247.iso File size:659M File type.iso ESX 4.1 (DVD ISO) Boot your server with this DVD in order to install ESX 4.1. NOTE: VMware ESX 4.1 and ESXi 4.1 require 64-bit capable servers for installation and execution. Please refer to the VMware Compatibility Guide for a list of qualified server hardware. MD5SUM:8dca1352a42dab842af30749636f73d1 SHA1SUM:297d9e28565217fb790907cfb4a66b5ea9c6fb5d Hope this helps you.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |