/build/static/layout/Breadcrumb_cap_w.png

Office 2007 Setup Parameters

Steps taken to package Office 2007 Professional Plus:

Steps:
[1]
Copied Office 2007 Source to a location and called it Office12 (included every folder from Access-en-US, Acceess.WW, Enterprise...to Word.WW)

Ran setup.exe /admin from command line.

Customized the OCT, selected Office 2007 Professional Plus as the product, entered product code, selected display to none, checked suppress modal, set install all on my hard drive and finally did File-Save As on the OCT wizard screen and saved the msp in the Updates folder. Renamed the msp as 1_Custom.msp

[2] Downloaded and Extracted office2007sp1-kb936982-fullfile-en-us.exe to the Updates folder. (This extracted lots of msp files ClientSharedMUIsp1-en-us.msp, MainMUIsp1-en-us.msp, MainWWSp1.msp, Proofsp1-en-us.msp, Office64wwsp1.msp)

Now, in our custom setup.bat file gave this command:
\\server\share\Office12\setup.exe /adminfile \\server\share\Office12\Updates\1custom.msp

Question:
On trying to install this setup,.bat on a test machine, I got the window prompt to select a product. I had already specified Office 2007 Professional Plus in the OCT, then why the prompt?

Do I need change the command line in my setup.bat to point to a config.xml file even though I have already created a customized msp?

Thanks

0 Comments   [ + ] Show comments

Answers (6)

Posted by: Foleymon 15 years ago
Orange Senior Belt
0
I think you need the config in there as well. My install executes with the following command line.
You can update that line to match your settings and see what you get.

setup.exe /adminfile "....\Updates\NAMEofYOUR.MSP" /config "....\Enterprise.WW\config.xml"
Posted by: turbokitty 15 years ago
6th Degree Black Belt
0
This package has been documented to death. Look at the Package KB and search the forums ("fora" for VBScab). The config file has some additional functionality in there that you'll probably need anyway. For example, I believe you need the config file to properly suppress any reboots. I can't remember exactly, but the info is there if you look.
Posted by: aek 15 years ago
Purple Belt
0
I got it to work using the config.xml command, but question:

1) I still a splash screen for like a brief second (The screen says Preparing for Office 2007 setup and then disappears)...and then the install starts in silent mode.

Is there a way to suppress this splash window? I already have Display Level=none and Suppressmodal=yes in the config.xml

Thank you
Posted by: Foleymon 15 years ago
Orange Senior Belt
0
Edit your config.xml and replace your line w/ the following, also make sure it is un-commented.
remove the <!-- in front of the line to un-comment
Change you line to the one below.
<Display Level="none" CompletionNotice="no" SuppressModal="yes" />

Also note the "QUOTES" around the ="none" and ="no" and ="yes"
Posted by: aek 15 years ago
Purple Belt
0
this splash window

Thanks - that worked. My bad..I did not un-comment the line. This prevented my reboot issue too.

Question: My current install has all the folders that I had copied from the CD. the size of this Office12 dir is 3GB+; Do I need to retain all the directories/folders to upgrade from Office 2003 to 2007?What all folders will I need to keep in my primary install directory?: ProPlus.WW, Updates, Catalog..do I need to keep all the others too? [Access.en-us, Access.WW, Excel-en-us, Excel.ww and so on?]

Thanks
Posted by: anonymous_9363 15 years ago
Red Belt
0
My general handling of Office is to futz with it as little as possible. 3Gb is nothing these days with storage so cheap.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ