I have created an MST file for Office 2003 Standard using the Customization Installation Wizard.

One of the screens during the wizard asks for a product key for local installation purposes. I entered what I thought was a valid 25 alpha-numeric code (we have checked this several times) without the spaces!

The package deploys correctly but after a few seconds we get the Activation Wizard screen asking the client to register the software.

Am I doing something wrong?

I can only think that the code numbers that I am entering are "wrong". Is there anything else that I should check besides the validty of these numbers in the MST?


John Falloon
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


when packaging office 2003, i would start by using the office resource kit to create your transform, this should solve any problems
you can download it from the microsoft website here if it isnt included in a folder on the cd called "ork"
Answered 08/29/2005 by: ictu packager
Orange Belt

Please log in to comment
Hi ictu,

It looks like he has already got that, the Custom Installation Wizard as the tool in the Office Resource Kit that is used to customise Office.


I'd create a verbose log file and try and see if it accepts your serial number you are passing to it. (just search the log file for a secton of your licence code to see if it appears)

Is it a volume licence key you have? What kind of key are you using to install office?

Hoefully someone else will chime in being of more use :)

Answered 08/29/2005 by: plangton
Second Degree Blue Belt

Please log in to comment
Hi Zeke:

Make sure your office is not equipped with limited licenses in that case it will ask you for activation. In case its on enterprise licensing then it wont. Check it out at your end and let us know.
Answered 08/30/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment