Deploying Office 2003

[pcdrobbie]

I am in an organization where the different departments buy their own Volume
license Office products. I need to come up with a way to deploy office
remotely, using a non-MS deployment application. I know that I can use the
Administrative installation point, but then that AIpoint could only be used
with one department. I would have to create another one for each individual
office that has it's own volume license.

Is there a way for me to build one package that each department could use,
then insert their own Product key for thier volume license? Otherwise I will
be stuck building up to 15 or 20 separate, (Landesk), packages to install
Office 2003 to all of our users.
I have not found a way to perform a unattended installation and have the
user input their own product key.
I know there has to be a way to perform this without the duplicated work,
any help would be appreciated.

Thanks.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[Wayne Dougherty]

Use the Office RK utility Configure Installation Wizard (ciw.exe) to build an
..mst file. Then modify the .mst with the a department's license key and save
the file with a new filename. Create batch files for each departmnet to run
setup with the TRANSFORMS= command line property value set to the .mst file
with that department's license key. An alternative would be to create one
..mst configured to prompt the user for the license key. Check the Office RK
documentation.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[pcdrobbie]

Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application.

 

[Bob Buckland ?:-\)]

If you're installing from an Office Admin Point
then generally the Office Volume License key was
used to setup the Admin Point. Keep in mind that
if this is a corporate purchase the that license
accountability is still at the corporate level,
regardless of a specific deparment placing a P.O. for it.
Also note that to write the key to the registry or
acceptance of the End User License Agreement for
individual users would require admin rights and
trying to track individual license keys in a large
organization with your scenario can be a bit of nightmare,
especially if you're now using retail keys so that
activation of each workstation would be required.

You may want to look at using the OEM System Builder
imaging tools for your scenario http://microsoft.com/oem
if activation is going to be part of the process on
an individual basis.

If you're not going to create the Office Admin Point
then, for example a CD image from that Admin Point
(http://microsoft.com/office/ork/2003 then you may
want to look at the Local Install Source method, but
the compressed CD image approach, which would allow you to
use Wayne's suggestion of creating an MST that embed's
the product key would let you create a physical'package'
you could distribute to different departments.

======
Thanks for responding Wayne. I appreciate the input on saving multiple mst.
That would work, but what I really want to do is your second suggestion and
nothing I've tried will work. If I don't add the key to either the mst or
the command line, a silent install will fail with an "invalid product key"
error. I want to be able to build one package and let any user install, but
thne require them to input the license key before they can use the
application. >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx