Hello Dizzle,
The steps that you have mentioned will only work if you have a standalone sku of office 2010 standard or professional plus.
The steps which I have mentioned is beneficial for organization which has a Volume licensing with Microsoft, because when they download the office 2010 package from the VL site, the single package contains the following content
Standalone packages
===================
word
excelpowerpoint
access
one-note
visio
project
sharepoint workspace
Along with standalone packages they also contain the following packages.
========================================================================
Office 2010 standard edition
office 2010 Professional plus
When SCCM executes the task sequence the setup stalls, as it has no information on which package / Product to install. Thats why you need to copy the proper config.xml file in the source folder. In my case i wanted to install professional plus from the Volumen licensing package, so i had copied the "config.xml" from the "ProPlus" folder to the source folder.
So now when SCCM executes the task sequence, it will first check which product to install.
Config.xml which was copied to the source folder has the information (in my case professional plus)
Then it will pass the control to your custom .msp file in the Updates folder.
Hope this clears everything.