T
Tony
I have created the install point run setup /admin and created custom.msp it
is saved in the updates folder and contains the product key. When I run setup
on a workstation I have included the /adminfile switch and givern the full
path to the custom.msp. the first screen that appears asks for the product
key. When I check the setup log I find that setup has found the custom.msp
(see 2 lines from the log below)
Admin file located at: \\exsrv\apps\Office12\updates\custom.msp
Pidkey specified in config.xml file is not valid. Showing PidKey view.
But as you can see from the second line for some reason it is looking in
config.xml for the key. If I enter the same key in config.xml it is acepted.
is saved in the updates folder and contains the product key. When I run setup
on a workstation I have included the /adminfile switch and givern the full
path to the custom.msp. the first screen that appears asks for the product
key. When I check the setup log I find that setup has found the custom.msp
(see 2 lines from the log below)
Admin file located at: \\exsrv\apps\Office12\updates\custom.msp
Pidkey specified in config.xml file is not valid. Showing PidKey view.
But as you can see from the second line for some reason it is looking in
config.xml for the key. If I enter the same key in config.xml it is acepted.