Virtualizing the legacy kit
The p2v process is relatively easy, the principle is basically ‘ghosting the system’ then sending it over the network to a virtual session you’ve created with sufficient space and relevant configuration for the target machine.
We virtualized many machines, particulary the windows nt boxes, with a focus on the legacy proliant 2500/6500/1600s which were ‘easy winners’ as in typically development, typically low specification and when tested worked in vmware (in our configuration) with transparency to the end user.
The process was used as I say to transfer the physical to virtual session, but we also took the opportunity to standardise, to reconfigure those servers that were out of date, always lacked enough space on the c drive/data drive, and ensure that all the relevant core patches (Microsoft security patches) were installed.
We basically did something like the following: clear the temporary files/unnecessary profiles/log files etc, check service packs, internet explorer versions (all 5.5 sp2 on NT4) etc.
The key things to watch out for were the compaq netflex adapters not wanting to work at 100/full, the proliant 5000’s didn’t seem to be that fond of booting from the p2v disk and the usual disk copying type issues, the copy is only as good as the original - we had a few servers with thousands of 1k files which took a long time to copy.
http://www.vmware.com/community/message.jspa?messageID=202944 - discusses the proliant 5000 http://www.vmware.com/community/message.jspa?messageID=268148 - discusses the network card problem


