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.