• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

p2v options for old win2k boxes

Methodical

is cool
2FA
Joined
Mar 21, 2000
Messages
7,540
I've got a couple win2k boxes running undemanding applications that need to be virtualized for safety in case something goes wrong with the hardware (which is very old generic hardware). virtual server 05 or vmware server? I notice both have semiautomated tools to facilitate the process, but those of you that have done this, any tips for a complete VM newbie?

host OS will be win2k3, or win2k8
 
I can only speak from VMWare experience, here. I have not yet tried Server 2k8 w/Hyper-V. If you use VMWare Server, you can download the Converter tool form the VMWare website, on a 60day trial basis, and use the tool until the time expires. After that, you will have to pay the licensing fee. The tool is very simple, it asks for:

host machine name, or IP address (of the machine to be P2V converted)
administrative login name (for the machine to be converted)
administative password
new VM machine name
location for P2V converted VM machine files (disk location)
any editing of machine virtual hardware, after the conversion process

once the P2V conversion starts, you get a progress bar, and hopefully, it completes successfully. Once that's done, you'll want to shut down the physical machine, and fire up the newly converted VM. After it started up, it'll go into Windows "I found a bunch of different hardware" freakout mode. You may have to reboot it a few times, and possibily even reset the NIC IP addresses (if not on DHCP) on the newly launched VM. Once it's done figuring out it's "new hardware," you'll want to make sure to install VMWare Tools on it, which is very simple to do, and can be found under Server's VM" dropdown menu, at the top of the Server window. After that installation, and a reboot, it's time to check that all of the programs, machine name, domain membership, and application services are operation as expected. From there, have people start hitting the machine.

Depends on the size of the disks, and amount of data on the physical machine, but a typical conversion on P2V is about 10GB/15minutes, so you can use that as a rough estimate on how long it will take the initial conversion process to complete. Most machines can be handled inside of an hour (from start to finish).
 
VMWare converter is dirt simple to use and in my experience works extremely well. Where I work we use Virtual Iron, which comes with 6 free conversions per socket with a product called Platespin. Platespin is a lot more complicated IMO to use, but it does an extremely good job as well. But to my knowledge there is no free version.
 
i've been using the combination of 'windows 2003 server -> vmware server 1.7 > vmware converter' for quite a while now, does what it says on the tin with minimal fuss. i would ideally like to have a play around with esxi but i would need new hardware for that.
 
Back
Top