Unattended Office 2003 Instalation

[vcv_bonsai]

Hi guys, this is my first post from argentina, so i hope that you can understand me.

The thing is quite simple.

MS Office2003 Ent. with volume licensing.

10 Windows XP Pro desktops, already deploy.

Im trying to deploy the office instalation as follows.

1. Create the MST file with the Office Resource Kit.

2. Configure all the needed settings for the instalacion.

3. on the desktops, I open a cmd and i write.

"setup.exe TRANSFORMS="z:\CAU\Office2k3\CAU.mst /qb-"

when i hit enter, a pop ups, comes from windows sayin that. "for installing or configure the sistem components, you should use control panel".

Im stucked in this screen cause, the installation wont go any further.

I hope, that you understand me.

And comments???

THANKS!!!

[Bendes]

Hello

Maybe try the following command :

setup.exe TRANSFORMS=z:\CAU\Office2k3\CAU.mst /qb-

(without quotes !!!)

Edited June 10, 2005 by Bendes

[Jelorian]

We did it a little bit different but it seems to work like a champ.

Not sure if it will apply to your environment but it seems to work for ours. I'm pretty sure you can find away to integrate it within a batch process.

We used the Custom Installation Wizard which is found with the Office resource kit. (orktools.exe)

Check out this site for more information.

http://office.microsoft.com/en-us/assistan...1362781033.aspx

You define where the .MSI file lives and then go through the prompts, customizing as you go. In the end we wrote a simple batch file for our users to run. The program then generates the .MST file based on your config options as well as what you call it.

The user's PC needs access to where the .MSI file lives, either on the network or on another drive (based on where you pointed to the .MSI file in the CIW).

The batch file is a single command with these parameters.

setup.exe TRANSFORMS=P:\Office2003Std\office.MST /qb-

You would run this from the command line from the root of where the installation files live. In our case we pointed to a network drive p:\ and the install files lived in p:\Office2003Std\office.MST

We found that we can install MS Office 2003 on Dell Precision 370's running XP Pro on a Gbit network in 1 minute or less.

We're still working on getting CIW to install the updates as well, but just getting this far was a big hurdle to overcome (Office 2003 rollout to 90+ users)

Hope this helps.

Jel

[Jelorian]

Hi guys, this is my first post from argentina, so i hope that you can understand me.

The thing is quite simple.

MS Office2003 Ent. with volume licensing.

10 Windows XP Pro desktops, already deploy.

Im trying to deploy the office instalation as follows.

1. Create the MST file with the Office Resource Kit.

2. Configure all the needed settings for the instalacion.

3. on the desktops, I open a cmd and i write.

"setup.exe TRANSFORMS="z:\CAU\Office2k3\CAU.mst /qb-"

when i hit enter, a pop ups, comes from windows sayin that. "for installing or configure the sistem components, you should use control panel".

Im stucked in this screen cause, the installation wont go any further.

I hope, that you understand me.

And comments???

THANKS!!!

<{POST_SNAPBACK}>

Sorry I just re-read your post and it seems you are doing pretty much the same as us. Hope you get it resolved soon.

[vcv_bonsai]

hey guys im been working my brain to its limits and i found it!!!

pretty stupid my error...i must say that my troubleshooting was quite poor this time.

The thing is that the batch file, was pointing to a setup.exe that did not exist in the intallation folder, so with a little bit of testing and error i got it right..

the line is as follows...

start /wait Z:\CAU\Office2k3\setuppro.exe TRANSFORMS=PRO11.MST /qb-

Notice, that I create another MST file...(just in case! )

and i realize that the executable was setuppro.exe or pro11.msi.

Already deploy and i can go home and sleep with mi girl in peace!!

thanks for your replys, they were really usefull.

PD: i have another issue with the servicepack slipstreaming...but to keep tidy this forum, I will create another thread.