Deploying 2007 With Script - Prompted To Select Application

[PBA-IT]

I'm deploying Office 2007 Professional Plus with a script (using setup.exe
/adminfile). I've got the system automated except for one thing.

When I call the script (which is to say, launch setup.exe /adminfile), the
user is prompted for which product to install. I don't want the user to have
to do anything, and I certainly don't want them deciding what to install.

Can I suppress this prompt and have setup proceed directly to installing?
It seems like maybe using the product code might be a possibility... though I
don't know what it is, or where to specify it.

Thanks!

 

[Sloan Crayton [MSFT]]

There should not be a prompt to select a product. Have you combined any
other products or languages into the installation source? In your
customization patch (.MSP), what were the installation UI choices?

Sloan Crayton
Microsoft

--------------------
| Thread-Topic: Deploying 2007 With Script - Prompted To Select Application
| thread-index: Achfm68oww6hCT3jTGWjDVq51Besvg==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?UEJBLUlU?= <[email protected]>
| Subject: Deploying 2007 With Script - Prompted To Select Application
| Date: Fri, 25 Jan 2008 13:46:04 -0800
| Lines: 12
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.office.setup
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:9914
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.office.setup
|
| I'm deploying Office 2007 Professional Plus with a script (using
setup.exe
| /adminfile). I've got the system automated except for one thing.
|
| When I call the script (which is to say, launch setup.exe /adminfile),
the
| user is prompted for which product to install. I don't want the user to
have
| to do anything, and I certainly don't want them deciding what to install.
|
| Can I suppress this prompt and have setup proceed directly to installing?

| It seems like maybe using the product code might be a possibility...
though I
| don't know what it is, or where to specify it.
|
| Thanks!
|

 

[PBA-IT]

Hi Sloan,

Thanks for the reply. In answer to your question, yes and no... I'm
writing this post in a detailed fashion in the event that anyone else has
this issue.

Per the instructions for deploying the Office 2007 suite, I created the
installation source which copies setup files for the entire product line. So
in that event, yes, there are other products with the Office Professional
Plus at the installation source, each in a subdirectory, with setup.exe at
the root of the installation source. I did not combine any other languages
into the installation source.

In any event, I was able to solve the problem. Based on my research of
various deployment methods, I found Active Directory to be unacceptable
(thanks, by the way, for taking that out... it worked brilliantly with
2003... I would have had too much time on my hands had I used it again...),
so I viewed a startup script or the config.xml deployment methods.

I didn't know one could combine the startup script with a custom config.xml
script. I created a config.xml file which only designated the product ID,
and I placed that in the same folder as setup.exe. Now when I call
"setup.exe /adminfile file.msp", setup apparently reads the config.xml file
and proceeds directly to the installation with no prompt. I'm inclined to
believe that I could replace it with whatever product ID I wanted to, and it
would install it correspondingly.

Here's the very simple Config.xml file:

<Configuration Product="ProPlus">

<!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> -->

</Configuration>

I found the Product ID for Professional Plus in the default config.xml file
in the ProPlus.WW subfoler.

Bottom line: using the config.xml file provides setup.exe with the product
to install, and using the /adminfile switch with a custom .msp file gives all
of the user settings.

Thanks again for your reply.