my client has a Windows XP, running core-2-duo, more than 8-years old system that is running a critical operation on their hotel infrastructure.
the PC simply perform interfacing between their phone, POS and internet accounting systems into the property management system.
well, the idea is that since it's not broken, why fix it... But isn't it concerning to know that there is no RAID, only a simple configuration backup, and the OS is obsolete, to run a critical system?
thus, i decided to take this opportunity to re-arrange their infrastructure a little bit, convert one of their 'free' server to work as a Hyper-V machine!
process is supposedly simple:
- perform disk2vhd to somewhere outside of C drive on WinXP
- transfer disk2vhd to host server
- set-up hyper-v on host server
- configure vm
- decommission the old machine
- run the new virtualized Windows XP
my REAL process:
- Installed Hyper-V function on the host server (all was smooth)
- reboot host server on one wee-hour morning
- set-up hyper-v environment
- perform disk2vhd 2.01 conversion of the existing C: of WinXP machine to it's D:
- transfer 20GB of VHD file (not VHDX) since host server is Windows Server Standard 2008r2 across network to the Host Server D:
- configure working environment and boot.
Horror 1 - Mouse is not usable
- what the heck, I just used keyboard. everything was typed!
- alt-tab, shift-tab and tab were my friends
- I had to run the VM in full-screen mode for transfer of short-cut keys to work...
- I needed to be able to send "Windows + U" command to work... that's the most critical!
Horror 2 - Windows XP cannot activate
- I couldn't activate windows! no LAN drivers activated too!
- at the windows activation prompt, i had to say YES
- then run "Windows + U" to run the Windows Narration Toolbar (Prompt)
- then tab-tab to click on a link to browse internet.
- Internet Explorer launches and I needed to then run c:\windows\explorer.exe on the address bar.
- that will allow me to run windows explorer window, so that I can perform any application install/uninstall
- I had lots of system junk stuff that came with my HP workstation, so i had to uninstall all of them.
- went on to MSCONFIG and disabled a whole-load of un-helpful start-up items too.
- shutdown VM
- Mount VHD to the Host OS... as a new disk
- Copy the following stuff:
- 7-zip
- AntiWAT tool for Windows XP Activation
- after copying stuff, I then proceed to dismount and boot-up the Virtual Machine again.
- repeat step 2 to 5, then run the activation of AntiWAT toolkit. Sorry Microsoft.
- Reboot one more time after the Activation is successful in AntiWAT.
- VIOLA! no more Windows XP Activation screen!
- Proceed to horror-3...
Horror 3 - Hyper-V integration cannot install
- I thought installing hyper-v integration tool was supposed to be breeze, well not-for-me.
- no matter how many times i tried installing them-app, the system reboots after that stating that integration service need to be installed to be running etc-etc.
- then I realize the root issue, see, when I boot up the system i get this prompt:
- I always chose the Disk2VHD Microsoft Windows XP Professional thinking that it's the right one...
- I was obviously wrong. After selecting the second option, I could proceed with the installation, and after 2-reboot, the integration services/stuff/ were installed succesfully.
- But I can no longer boot into the first option... so I really need to go into boot.ini file to remove that line.. or my horror won't stop when the server is unable to start after it's reboot.
- Attempt to boot with auto-option 1 after integration service is installed proved futile:
- Boot with the second option, and it works!
- and my mouse works!!!
Horror 4 - what about drivers??
- Guess what! after horror 3, the installation of the Hyper-V integration tools automatically installed the system driver, the mouse, the LAN and everything is working in-order!
- Next, proceed with boot.ini amendments and we're done!
such is how i spent my saturday 12-noon to 4-pm in my office.. :(
