Virtualizing a Windows XP Pro (Server)

Yes, I am not joking...

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:

1. perform disk2vhd to somewhere outside of C drive on WinXP
2. transfer disk2vhd to host server
3. set-up hyper-v on host server
4. configure vm
5. decommission the old machine
6. run the new virtualized Windows XP

or so I thought..


my REAL process:

1. Installed Hyper-V function on the host server (all was smooth)
2. reboot host server on one wee-hour morning
3. set-up hyper-v environment
4. perform disk2vhd 2.01 conversion of the existing C: of WinXP machine to it's D:
5. transfer 20GB of VHD file (not VHDX) since host server is Windows Server Standard 2008r2 across network to the Host Server D:
6. configure working environment and boot.

Horror 1 - Mouse is not usable

1. what the heck, I just used keyboard. everything was typed!
2. alt-tab, shift-tab and tab were my friends
3. I had to run the VM in full-screen mode for transfer of short-cut keys to work...
4. I needed to be able to send "Windows + U" command to work... that's the most critical!

Horror 2 - Windows XP cannot activate

1. I couldn't activate windows! no LAN drivers activated too!
2. at the windows activation prompt, i had to say YES
3. then run "Windows + U" to run the Windows Narration Toolbar (Prompt)
4. then tab-tab to click on a link to browse internet.
5. Internet Explorer launches and I needed to then run c:\windows\explorer.exe on the address bar.
6. that will allow me to run windows explorer window, so that I can perform any application install/uninstall
7. I had lots of system junk stuff that came with my HP workstation, so i had to uninstall all of them.
8. went on to MSCONFIG and disabled a whole-load of un-helpful start-up items too.
9. shutdown VM
10. Mount VHD to the Host OS... as a new disk
11. Copy the following stuff:
1. 7-zip
2. AntiWAT tool for Windows XP Activation
12. after copying stuff, I then proceed to dismount and boot-up the Virtual Machine again.
13. repeat step 2 to 5, then run the activation of AntiWAT toolkit. Sorry Microsoft.
14. Reboot one more time after the Activation is successful in AntiWAT.
15. VIOLA! no more Windows XP Activation screen! 
16. Proceed to horror-3...

Horror 3 - Hyper-V integration cannot install

1. I thought installing hyper-v integration tool was supposed to be  breeze, well not-for-me.
2. 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.
3. then I realize the root issue, see, when I boot up the system i get this prompt:
   
4. I always chose the Disk2VHD Microsoft Windows XP Professional thinking that it's the right one...
5. 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.
6. 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.
7. Attempt to boot with auto-option 1 after integration service is installed proved futile:
   
8. Boot with the second option, and it works!
9. and my mouse works!!!

Horror 4 - what about drivers??

1. 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! 
2. 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.. :(

Troubleshooting Steps in Common Microsoft Office and Other Applications

Sometimes we encounter weird problems that appear from time to time while using our PCs or notebooks. As such, we've got to be armed and ready to carry out some diagnostic tasks to ensure that we eliminate 90% of the possible issues system wide. If these steps could not resolve the issue, I'd recommend re-format and re-install Windows as it'll be faster and more cost-effective to do that as re-install of Windows these days are pretty 'fast'.

Provided of course, you have all the drivers information, back-ed up data and all applications needed for the re-installation.

The troubleshooting for Common Microsoft Office or application issues especially when Windows gets cranky are:

1. Try to repeat the problem to find a pattern to the issue. 
2. If you're able to, that's good because we'll rely on the pattern to troubleshoot the issue
3. General guideline for troubleshooting for Ms Office issues
4. Go with Microsoft way of i-fix it at http://support.microsoft.com/fixit/ 

If i-fix it can't fix it, then:

1. find out when the problem occured, and 
2. then try to perform a system restore to (Before the problem happened).

If there's no system restore, go with these steps: (outlined here) 
Basically in summary, it's run the diagnostic tool that comes free with Ms Office, from 2007 on-wards. Location of fix tool is in Programs > Microsoft Office  > Microsoft Office Tools > Microsoft Office Diagnostics.

Run all the diagnostics to ensure that the Ms Office installation and system is well.

In the event where there is no system restore and no diagnostics - (Tough luck) 
Or, the system diagnosis stated that all is well....

1. run registry repair using Ccleaner, backup registry first using the ccleaner tool, save it to my-docs folder
2. go to add-remove programs, perform repair of the Microsoft Office
3. restart system and run all ms office updates and windows updates

I believe this should resolve 90% of all Microsoft Office issues. Do let me know if you have comments or improvements!

Converting a local old Machine to a Virtual Box compatible VM (VHD)

Client told me that they need to change PC, but has an old Accpac 4.0 that need to run only on XP. Plus without a valid maintenance contract, the vendor wants to charge them about 100bucks just to install the application. How? Need to change PC but don't want to spend too much money.

This is a step-by-step guide in how to virtualize a Windows XP or Windows 7 into a virtual machine so that users can run the Windows Virtual machine in Virtual Box. The steps are very important or you might possibly run into problems.

Tools needed:

1) USB Ext Disk 500GB

2) Disk2VHD (latest edition), i think v 1.4

3) Virtual Box 4.22

4) plenty of time

Phase 1 - virtualize the current machine

a) just run the disk2vhd

b) virtualize to a USB disk instead of local disk or D drive. it's safer and better

c) ensure that no running processes are in the system. close all running programs

d) ensure that all windows xp and 7 patches are installed and system is just restarted before the program is run.

e) proceed with the virtualizing to VHD format

 

Phase 2 - install virtualbox onto the new system

a) proceed with default installation and follow all steps

b) no special configuration is needed for virtual box

Phase 3 - Setup VHD and Virtualbox

this is complicated, pls follow carefully:

a) make network card to be bridged onto the physical network adapter

b) configure VM name carefully with the Upper cap and lower cap accordingly when creating a new VM.

c) set ram size to 512mb, and leave everything as default

d) create shortcut of the VM to the desktop for ease of access

e) when closing the VM, set to save the state

f) if there's a problem with auto-restarts all the time, do note to delete this file in c:\windows\system32\drivers\intelppm.sys, just delete that file in SAFE MODE of the VM, and restart. should solve the problem. happened to me several times when setting up the Windows XP VM on different machines, especially when I transfer the VM from 1 machine to another.

g) configure PC name to be (host pc name)-xp or (host pc name)-vm. Eg, mcsfin-pc01-xp

h) install the virtual box add-on tool VM add-on. you must configure the ISO image to be mounted. this is important for the sync of video and mouse

I think this is it! Everything should work as per norm. Will update again if there's things to add.