Dear All:

Following several articles, web blogs, posts, forum entries and M$ documentation, I finally worked up the courage to attempt to deploy Office 2007 in my domain environment (Windows 2003/XP)

With that said, I attempted to generate a "single component" installer version for Outlook 2007 ONLY deployment... The idea was so that users can "get used to" Outlook 2007 and the Office 2007 look then I would "upgrade" them to the rest of the suite later on.

Prior to generating the MSP file, I grabbed the SP1 updater.exe from M$' MU site, and via the /extract option extracted the MSPs and placed them in the "\Updates" folder.

Then via the Off2K7 Enterprise (Volume License) CD content extracted on to my DFS share on the network I ran setup /admin and began fiddling with the ORK UI to generate the necessary MSP file.

For this example, I did the exact following:
********************************************************************************

SETUP
1) Install Location and Org. Name:
a) left path as is
b) Filled in our org. name

2) Addtl. network sources
a) entered full UNC path to Office 2007 CD content

3) Licensing and user interface
a) entered our VLK
b) checked EULA box
c) Set display level to None
d) Checked "Suppress modal" and "No cancel"

4) Remove Previous Installations
a) chose the 2nd radio button, and 1-by-1 via the "Details" button below set the "Remove" column for each entry to "Remove none" except Outlook 2007

FEATURES
2) Set Feature Installation States
a) In this tree, defined all as "Not Available" except Outlook, Shared Features and Tools
b) Set Shared Features and Tools to "1st time usage"

ADDITIONAL CONTENT
5) Configure shortcuts
a) Removed ALL except Outlook 2007

********************************************************************************

After this, I saved the MSP file, placed it in the network shares' root folder where setup.exe belonged then ran the following command-line on my system:

\\<DFSPATH>\<OFF2K7Share>\setup.exe /ADMINFILE Outlook2K7ONLY.MSP

after that I started watching via ProcessExplorer, and after about 7 minutes, my computer all of a sudden decided to reboot (surprise surprise! set the UI to 0 and whaddya get? ) After the reboot is what was "interesting"!!

Upon boot, the machine came to the logon window, I entered my creds, and moved on... it brought up my desktop and decided to freeze at that point! I waited for 20 minutes with no avail... so after that I forced a hard shutdown and booted into safe mode and forced a chkdsk on the entire disk. After the 5 stages of chkdsk completed I rebooted back into Normal and entered my creds...

At this stage, the ORK toolkit like screen popped-up and said "cannot use /ADMINFILE" then auto-dimissed itself and booted into my desktop. Upon inspection, it looks like all went well, as I have Outlook 2007 ONLY with the rest of the components as 2003. Outlook 2007 is SP1 version and the rest o the components are working happily alongside...

So... what is my question? Well:

a) Why did my computer freeze upon that forced reboot?
b) Is there a way to suppress the forced reboot?
c) What was that error msg all about? How can I get rid of that?
d) Looking at the XML file I generated via the MSP conversion tool ( http://technet.microsoft.com/en-us/library/cc179027.aspx ) I see entries for all the tools in there... Seeing as how I've been trying to make this a "single component install" is there a way to ensure these addtl. components DON'T get listed somehow?
e) regarding the MSPs for SP1, do we need ALL of them? Or for Outlook 2007, would just MAINWWsp1.msp suffice?

My suspicions:

a) I placed a bunch of MSP files that were extracted from the SP1 exe... I wonder if during the installation phase despite not needing it, it requested a file somehow then errored out perhaps?

b) Did I over-customize/utilize unnecessary fields in the ORK UI?

c) Do I need to create a seperate off2k7 share for the Outlook 2007 ONLY installer and have the SP1 update ONLY, along with Outlook2007ONLY msp file?


Any update/comment/insight is much appreciated as this is a now URGENT task that needs to be deployed/completed ASAP.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Also... do I need BOTH config.xml and .msp? Or is MSP just enough? If not, why not? If so, which is better?
Answered 08/11/2008 by: vtknightmare
Yellow Belt

Please log in to comment
0
ORIGINAL: vtknightmare
a) Why did my computer freeze upon that forced reboot?

There is a setting in the XML to supress reboots-
<!-- <Setting Id="Reboot" Value="Never" /> -->

ORIGINAL: vtknightmare
c) What was that error msg all about? How can I get rid of that?

I think that error comes up if you just type "setup.exe /adminfile", without the rest of the command line. I suspect the reboot wasnt invoked by the installer (maybe caused by), but windows needed a rest, probably why it hung. check the event logs.

ORIGINAL: vtknightmare
d) Looking at the XML file I generated via the MSP conversion tool I see entries for all the tools in there...

You can strip the XML file down to only things you need.
I have found that you need to use both an MSP and the config.xml file, although documentation says you can only use the msp. Specify both on the command line, even if the xml file is just the default.

ORIGINAL: vtknightmare
e) regarding the MSPs for SP1, do we need ALL of them?

I dont know, prob not. But, since your going to do the full Office install, not just Outlook, why wouldnt you want SP1 in there anyway.

ORIGINAL: vtknightmare
c) Do I need to create a seperate off2k7 share for the Outlook 2007 ONLY installer and have the SP1 update ONLY, along with Outlook2007ONLY msp file?

No. One set of media for all Office apps. I have a Publisher MSP in a seperate folder, just specify the location of the MSP on the command line. And, the SP1 MSP's in the updates folder.
Answered 08/11/2008 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
@red4eva:

Thank you for clarifying most of my questions! :)

With that said, so according to you I need BOTH the xml AND the msp file... how would I go about customizing the xml to install Outlook only then?

--vtk
Answered 08/12/2008 by: vtknightmare
Yellow Belt

Please log in to comment
0
@All:

Per reds4eva's recommendation, I went ahead and created BOTH a config.xml file and MSP file via the OCT. However, now I'm running into an all together different problem:

when I try to execute the setup as follows:

\\server\shared\msiDeploy\office\2K7CD\setup.exe /config \\server\shared\msiDeploy\office\2K7CD\Mods\Outlook2K7Only.xml /ADMINFILE \\server\shared\msiDeploy\office\2K7CD\Mods\Outlook2K7Onlyv012.MSP

NOTHING HAPPENS! You see a "blip" on the taskmgr where setup.exe opens and closes...

However, if I instead move the MSP to the Updates folder, and rename it as 00Outlook2K7Onlyv012.MSP then move the Outlook2K7Only.xml file to the Enterprise.WW folder and rename it as config.xml and then execute:

\\server\shared\msiDeploy\office\2K7CD\setup.exe

That works!?

What am I doing wrong? I thought I was told that I have to run BOTH MSP AND XML... I don't want to copy the CDfolder over and over to have different configs... hence why I tried my first cmdline... ?
Answered 08/12/2008 by: vtknightmare
Yellow Belt

Please log in to comment
0
Below are 2 command lines I use, the top one is for Full Office, the bottom one installs Publisher, both use the same source.

%~DP0\Install\setup.exe /adminfile %~DP0\Install\%Organisation%\OffStd2007.MSP /config %~DP0\Install\Standard.WW\config.xml

%~DP0\Install\setup.exe /adminfile %~DP0\Install\%client%\MSPublisher07_010.MSP /config %~DP0\Install\Publisher.WW\config.xml

Try-
\\server\shared\msiDeploy\office\2K7CD\setup.exe /adminfile \\server\shared\msiDeploy\office\2K7CD\Mods\Outlook2K7Onlyv012.MSP /config \\server\shared\msiDeploy\office\2K7CD\Outlook.WW\config.xml


And the contents of my Publisher xml file (you could leave it at default) -

<Configuration Product="Publisher">
<USERNAME Value="clientname" />

</Configuration>
Answered 08/13/2008 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
I am having a similar issue trying to deploy Office 2007. When I run the following from command line:

C:\>"Office2007\Office 2007 Standard\setup.exe" /ADMINFILE "OFFICE2007.msp

The installastion starts and then I get Setup Errors "The /adminfile command-line option can be used only during initial installation of the product"

I have already created the .msp just trying to get it to run. Any help would be appreciated.
Answered 02/04/2011 by: j.hydro
Senior Yellow Belt

Please log in to comment
0
I'm not sure if you are doing a new install or updating an existing install but from the error I would guess that you either need to specify the full path to the admin file or you already have office installed in which case you would apply the patch by doing msiexec.exe /p \\path to patch\office2007.msp /qb!

Because all of our MS Office products (office std, pro, project, visio, etc) are all combined we have to specify the config.xml file as well even though the config.xml file has not been modified. setup.exe /adminfile \\path to office\Updates\standard.msp /config \\path to office\Standard.WW\config.xml

ORIGINAL: j.hydro
I am having a similar issue trying to deploy Office 2007. When I run the following from command line:

C:\>"Office2007\Office 2007 Standard\setup.exe" /ADMINFILE "OFFICE2007.msp
Answered 02/04/2011 by: joedown
Second Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity