SBS 2003 to SBS 2011 migration

The network enviornment that I had carried out the migration on was a fairly simple one Windows AD domain(DOH!).  In terms of the hardware infrastructure, the core of it consists of just a couple of ageing 10/100/1000 MBit switches and a Dell Poweredge 2950.  The server was running a VMWare ESXi 5 host operating system and the guest machine was a SBS 2003.  The client had purchased a new Dell R710 server and I had to  migrate the system to an SBS 2011.  They had one LOB application which is simply a self contained folder and all I had to do was copy and pasted onto a new shared folder on the destination server.  Other than that there really was just the rest of the data (company and users) and printers that required to be manually migrated.  The built in SBS migration mode of SBS 2010 automated the intitial migration of AD, DNS, DHCP and Email Exchange services but with some manual process involved.  I skipped out migrating sharepoint as that wasn't used by the client.....fortunately.   Other manual changes required are to update the port forwarding or network address translation rules in your  router, scan to email settings on the printers etc...  The wonderful thing about the whole experience was how sequential the process was.  There is a migration wizard that guides you through each step of the way in addition to the many trustworthy blogs/articles available on the web that you can access.
I am not saying that it is easy as that really depends on the health of the source server (sbs 2003), the number and complexity of LOB applications(especially legacy and database), whether sharepoint is utilised,  vpn configuration etc....
The first stage is the most important.  If you can get past stage 1 smoothly then the rest of your journey will be childs play. 
http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx

I then followed this document:
http://www.microsoft.com/download/en/details.aspx?id=3231

I encountered a weird issue whereby exchange installation failed during the live migration and so I had to revert back to a snapshot(THANK VMWARE FOR THIS JAILBREAKER) and start again.  I had successfully completed a migration on a cloned system previously and resolved the little bugs/issues along the way.  I had no idea why it failed but read somewhere that IPv6 was to blame and that there was a registry entry required to be entered.  I thought hard and realised I had the regedit program opened a long the way as I was anticipating an issue to occur but never manifested during the live migration(I swear it did happen during the test migration on the clone).

Acceleration test for the MK6 GTI

The night was clear, there was little to no winds/crosswinds, humidity was low, altitude...? , but I gave it my best and had a pretty good result on my first attempt with traction control off using launch control.  The final result was 6.2 secs:

The following week I tried it again.  Conditions were similar but this time with traction control on and I did not really mash the accelerator hard enough during launch control.  The final result was 6.7 secs:

http://www.youtube.com/watch?v=k96z0WEYxq8