Warning: Unable to locate the required Sysprep files. Please upload them under C:\ProgramData\VMware\VMware vCenter Converter Standalone\sysprep\svr2003 if you have been running into this error there is a simple fix although not usually the one posted all over the web about downloading them from Microsoft’s website. Maybe they are on there somewhere but here is the easy solution. Insert the Windows 2003 x86 CD it doesn’t if its R2, SP2 or whatever as long as its x86 or x64 to match the version of the OS your trying to copy over. Open the directory on YOUR Machine, NOT the server your trying to convert. You will see the directory already exists but is empty, now open the Server 2003 CD and browse to \SUPPORT\TOOLS and you will see Deploy.CAB. You may need a program like WINRAR for this next part, right click on the Deploy.cab and select “Extract Files” you will want to extract the files to any location it really doesn’t matter because it will create a new folder called “Deploy” and what we need
Recently while working on the new Virtualization shootout testing I came across the issue that Microsoft Hyper-V doesn’t offer any built in Physical to Virtual machine conversion tools so I set out for an easy way to convert a physical machine for some quick and simple testing. I found two options and I will present them both, the first option is a tool I recently became familiar with due to the fact that we are considering moving our internal virtual environment at the office to Citrix. Its obvious at this point who makes the tool but for the name its rather obvious as well and is called the XenConvert tool by Citrix. This tool is absolutely killer, it can convert physical machines, specific volumes, Microsoft VHD files, VMware VMDK files, Open virtualization OVF files and Xen virtual Appliances to XenServer Appliances, XenServer Hard Disks (VHD), Open Virtualization Packages (OVF), and Provisioning Services vDisk. Download Citrix XenConvert Next up on the list is a tool from Microsoft (go figure) although not directly linked or marketed for
Once the new server is built I plan to revisit virtualization with some new contenders added to the list. Here is the current bare metal line up VMWare ESX Microsoft Hyper-V Citrix XEN RedHat KVM Windows VM VMWare Workstation & Server Oracle / Sun Virtual Box Parallels Workstation Linux VM VMWare Workstation & Server Oracle / Sun Virtual Box Parallels Workstation This will all run on the new server so it will be the same hardware each time around. I might do this before I put in the Raid 50 to make my life a lot more simple when installing and configuring these. If I choose that route I will likely test with a WD Raptor as my main drive to keep the speed up. This will take some time to complete since the new server isn’t built yet and it is going to take a LOT of reloads. Thanks and stick around it’s going to be interesting.
!!! — UPDATE — !!! ~~ UPDATE – I will not be contniuing this testing with this machine. I am finding that although I have all the proper drivers and can get everything to work, something still doesnt seem right. At least if anything we can learn that even with all the drivers Hyper-v runs HORRIBLE on an Nvidia chipset or possibly just runs horrible. I am trying to get my hands on a T300 to really make the test fair and then perform all of this testing again. My biggest goal is for a box that is fully supported by ESXi so I dont hear any whinning that the testing was unfair since I can load drivers for virtually anything in Windows but ESXi takes a bit of hacking. I will leave this page posted for general knowledge and to get a taste of whats to come. Sorry the testing is incomplete. Carry on ~~ Purpose – Benchmark Vmware and Hyper-v in several configurations then compair the numbers because numbers dont lie. The testbed-