Software Deployment

silly silly silly.

If its already a MSI, then create a MST.

As a rule of thumb - NEVER capture a MSI.

If your customer "thinks" they want Office repackaged, it is really up to you to explain why this is such a bad idea. It is already an MSI (and a very complex one at that). You will cause limitless problems repackaging this application. Take a look at the Custom Installation Wizard (CIW) provided with the Office Resource Kit (free from MS) and you will see it is very easy to do it correctly.

*Link to kit. ORK.exe*

(though the MSI is already there and i could have made one MST for customization, but its user's requirement are to do so).
Sometimes the best thing to do for a customer is to adamantly refuse to do what they ask. This is one of those times. Office is an unusual MSI in that it should only, and I mean only, be transformed by an MST made with the Custom Installation Wizard in the Office Resource Kit. If not you are 100% guaranteed to run into a problem during packaging or post deployment because Office has a lot of essential Custom Actions that will not be part of the captured install. Sooner or later, something won't work.

If I were in your position, I'd explain to the customer that capturing Office is a very bad direction full of problems. Office must be an exception. If they insisted, and it came right down to it, I would point blank refuse to capture Office because I will not perform work that is guaranteed to cause my customers major problems in the future. I will not soil my reputation of producing solid work just to make a customer temporarily happy. (and if that's said in a calm, professional manner very few customers persist.)