Upgrading bug: BizTalk 2010 to BizTalk 2013 R2

Hi,
Upgrading has been made easy with newer versions of BizTalk. I recently upgraded the BizTalk software from 2010 version to 2013 R2.
Here are few screenshots....Important is the last screenshot.. :)

Here it talks about Pre-Actions required.
Stop WorldWide Web Publishing Service.
Start Enterprise SIngle SignOn Service.

Since I had selected to install Developer Tools also...it gives me an Error with missing prerequisites.
I installed Visual Studio 2013 and then continued on.

"Buckle your seatbelts....there are no Airbags to save you in this crash ride".
Microsoft will not rollback the databases if the Upgrade fails.
I did ensure that I had a backup of all the databases.

Forgot to stop RuleEngine Update Service.

And Finally the surprise...........

Seems Microsoft forgot to rename the Folder from "BizTalk Server 2010" in Program Files to "BizTalk Server 2013 R2" but product got upgraded successfully.

Hope they will fix this soon ;).

BAM Add-In Excel Issue : Object library invalid or contains references to object definitions that could not be found.

Recently when I opened Excel every time I got a weird Error for BAM Add-In.
Incidently I have not messed up with BAM recently for sure.  After googling a bit I could not find any post related to BAM Add-In issue but many with VBA macros failing after a Cumulative update.
My laptop is set to auto update the system with latest updates as I love to try new features out in Microsoft market and this Cumulative update had messed up the macro settings in Excel.
http://support.microsoft.com/kb/957924/en-us

The point here is if you get Errors related to BAM Add-In Excel macro while opening Excel just follow these steps
To resolve the problem, delete cached versions of the control type libraries. 
To do this, search the hard disk for “.exd,” and then delete all occurrences. The .exd files are re-created automatically by using the new controls the next time that you use VBA.

After deleting all .exd files(there were only 2 in AppData folder) things were back to normal and BAM Excel Add-In worked fine.