Hi Dany,
On 17.11.2010 15:34, DANY CHOUINARD wrote:
> I'm (barely) deploying office 2010 in schools labs. I thought
> everything was quit fine (not really, but it was working when wpkg.js
> was called from the command prompt) but the Office's setup.exe forks
> into it's own process and loose it's network share once wpkg.js is done.
> Therefore no Office get ever deployed at bootup when using the wpkg
> service.
Interesting, my edition of Office 2010 Pro Plus does not fork a background
process.
Honestly I am not deploying it yet with WPKG yet but I launch setup.exe from
command prompt which does not exit until Office is installed.
I think the main difference is that you created an MSP file. I am not using an
MSP file but I do all the customization I need in my config XML file and so I
use different setup.exe command line switches.
I am basically calling
start /wait "O2k10" "setup.exe" /config "path\to\config.xml"
While my config.xml actually looks as follows:
<Configuration Product="ProPlusr">
<Display Level="none" CompletionNotice="no" SuppressModal="yes"
AcceptEula="yes" />
<AddLanguage Id="match" ShellTransform="yes"/>
<AddLanguage Id="en-us" />
<AddLanguage Id="de-de" />
<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office
Professional Plus Setup(*).txt" /> -->
<!-- <USERNAME Value="Customer" /> -->
<!-- <COMPANYNAME Value="MyCompany" /> -->
<!-- <COMPANYNAME Value="Cyberdyne" /> -->
<PIDKEY Value="XXXX-XXXX-XXXX-XXXX-XXXX" />
<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
<!-- <LIS CACHEACTION="CacheOnly" /> -->
<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" />
-->
<!-- <DistributionPoint Location="\\server\share\Office" /> -->
<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
<!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> -->
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<Setting Id="Reboot" Value="Never" />
<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i
\\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" />
-->
</Configuration>
The XML file also has some "command path" options (see last line). It might be
possible to activate Office by using this extension points.
The XML files included in Office 2010 distribution also contain some options to
include/exclude components. e.g.
<!-- Access -->
<!--
<OptionState Id="ACCESSFiles" State="absent" Children="force" />
-->
For uninstall I am basically just using the following command line:
start /wait "O2k10" "setup.exe" /uninstall PROPLUSR
I know this shitty Office 2010 installer is very special. It also requires
special treatment for OEM-preinstalling Office-ready machines. But at least
using the XML config method it does not fork (at least not for me).
br,
Rainer
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
