So I honestly don't care as long as we can make the conversion and that it works properly. 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.Īnd they have agreed to support the product in a VM. 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.

Indeed, when the VM is booted on the hypervisor it will immediately start uninstalling old drivers and ask for new drivers. 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.

So our only hope is to build a BootCD with network support that could run vCenter Converter 5.x. So we checked with them and they don't see any problem in converting the system to virtual. We reeeeally don't want to mess with our accounting software. 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. 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). VMware used to have a BootCD for their vCenter Converter tool but unfortunately it was discontinued since version 4.3 (current is v5.x). It's been some time since I last used winbuilder and all the other tools referenced here in the forum.īut I am facing a difficult task and I remembered reboot.pro could have the solution to my problem.

Vmware converter 4.1 boot cd download