I was faced with the task of getting Office 2007 out into the field last week. I found one problem that I can find a solution for.

We are using GPO to get it out to at least the group at this stage. I used the OCT to create the MSP file and place it into the updates directory. However I found on testing that it didnt read the MSP and wanted to read the Config.XML file. We are still running Exchange 2003 and thus cant use the auto config for the Exchange server at this stage.

Is there a way to get this out? Does Office 2007 Standard Edition read MSP files?

Any help would be greatly appreciated.

Thanks

Warren
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
You mean you used OCT to create an MST, surely?
Answered 07/30/2007 by: VBScab
Red Belt

Please log in to comment
0
Actually no in Office 2007 it only creates an MSP which you cant use via GPO. According to the doco it goes in the Updates directory but the installer doesnt appear to pick it up in the Standard Version.
Answered 07/30/2007 by: wazh
Senior Yellow Belt

Please log in to comment
0
Forgive my ignorance - I haven't yet had the pleasure of Office 2007 - if it's a patch, wouldn't you apply that to your admin image before deployment?
Answered 07/30/2007 by: VBScab
Red Belt

Please log in to comment
0
Good questions. I cant see any reason why not at all. I suppose I really need to find that out.
Answered 07/30/2007 by: wazh
Senior Yellow Belt

Please log in to comment
0
You could also transform the patch meaning:
Open the MSI in ORCA
Create a transform
Apply the patch
Save the transform

Just what out to include the streams when you save the transform.
Answered 07/30/2007 by: AngelD
Red Belt

Please log in to comment
0
To answer your question - There is no admin install point. The installation creates the MSOCache regardless and that is used during repairs.

Create a simple config.xml that contains the basic installation information, it does not need to contain all the settings you want for Office 2007. At the end of the office installation it should run all the MSP's in the "Updates" folder including your settings MSP - This is how you apply patches to your new installations. For existing installations the patches need to be run on that system - I have been unable to find a way to apply patches using setup.exe and say /repair or /modify.

Here would be a sample config.xml which needs to be placed in the %systemdrive%\MSOCache\All Users\{90120000-0012-0000-0000-0000000FF1CE}-???(this will be the same as the drive letter) or %systemdrive%\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-???(Same here) depending on whether you are talking about ProPlus(0011) or Std (0012).

A sample ProPlus config.xml - note for using xml -- starting a node with <!-- sets it to a comment and that code is not actually used, you will see this when you look in the current config.xml

<Configuration Product="ProPlus">

<Display Level="basic" NoCancel="yes" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

<Logging Type="ProPlus" Path="%temp%" Template="Microsoft Office ProPlus Setup(*).txt" />

<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />

<Setting Id="SETUP_REBOOT" Value="NEVER" />
<Setting Id="Reboot" Value="NEVER" />
<Setting Id="HIDEUPDATEUI" Value="True" />

</Configuration>

-- The new XML based MSI's that Microsoft is distributing is a real pain in the you know what. My deployment system refuses to evaluate the MSI and import it into my servers. I programmed my own frontend and used the LIS creation functionality that is available by the installer.

fyi - When a LIS is created the files will be delivered to your %systemdrive%\MSOCache the registry will also be updated to show the available status of the office components - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads.

You can find alot of information by looking through the links provided on the Office 2007 packaging guide on appdeploy, such as the settings for the config.xml.

Good Luck and hope this helps a little,
-Grant
Answered 07/30/2007 by: gmorgan618
Blue Belt

Please log in to comment
0
Presumably there's some reason why MS is fussing with this stuff yet again...
Answered 07/30/2007 by: VBScab
Red Belt

Please log in to comment
0
Is it possible to use setup.exe /adminfile \\blah\blah.msp without specifying /config ? According to the documentation you can use it on its own I would say, however, I am not getting it to read the msp either. I am going to try to setup a config.xml but it seems pointless to have to set some of the identical settings twice.
Answered 08/22/2007 by: schieb
Purple Belt

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