Last friday I was able to decipher the XML to control the office2010
installation.  There was a numerous things that I needed to be done.
One done, I tried to run my installation script and ran into the same
probleme.  Setup lunch a separate process (OSE.EXE) and terminate.

My wpkg service runs as local system with desktop interaction enable.  I
don't know what I can do more.

I wrote the little script that basicly wait after the installation
process.  I did not had the time to test it properly.

---WAIT.BAT----
:UN
ping.exe -n 6 -w 1000 127.0.0.1 >NUL
tasklist /FI "IMAGENAME eq OSE.exe" 2>NUL | find /I /N "OSE.exe">NUL
if "%ERRORLEVEL%"=="0" goto UN
---------------

I hope to reach conclusion tomorrow, as I'll get back to that school and
have time to work on that.

Dany Chouinard



Le vendredi 19 novembre 2010 à 17:01 -0800, Kevin Keane a écrit :
> I suspect that what is going on has to do with UAC rather than with a 
> separate process. If wpkg.js runs as ordinary user (even an Administrator), 
> the installer has to switch to the "internal" Administrator account in order 
> to actually do the installation. Since this actually switches to another 
> account, you lose all file shares when this happens.
>
> Solution: make sure that when you run wpkg.js, you launch it with "run as 
> administrator" permission. You can also launch it as a startup script from a 
> group policy (don't launch it as a logon script - that runs as the regular 
> user).
>
> Here is how I install Office 2010: Note that you need to put the 
> configuration XML file into the %SOFTWARE%\configs directory. The 
> %SOFTWARE%\MSOffice2010 directory contains everything that's on the CDs.
>
> This is for Professional Plus; you may need to make adjustments for other 
> versions of Office.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <packages
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>     xsi:noNamespaceSchemaLocation="../xsd/packages.xsd" >
>
>    <package id="office2010proplus" name="Microsoft Office 2010 Professional 
> Plus" revision="20100" reboot="false" priority="10">
>      <check type="uninstall" condition="exists" path="Microsoft Office 
> Professional Plus 2010" />
>      <install cmd='"%SOFTWARE%\MSOffice2010\setup.exe" /config 
> "%SOFTWARE%\configs\MSOffice2010_ProPlusr.config.xml"' >
>        <exit code="3010" reboot="postponed"/>
>      </install>
>      <upgrade cmd='"%SOFTWARE%\MSOffice2010\setup.exe" /config 
> "%SOFTWARE%\configs\MSOffice2010_ProPlusr.config.xml"' >
>        <exit code="3010" reboot="postponed"/>
>      </upgrade>
>      <remove cmd='"%SOFTWARE%\MSOffice2010\setup.exe" /uninstall ProPlusr 
> /config "%SOFTWARE%\configs\MSOffice2010_ProPlusr.config.xml"' >
>
>        <exit code="3010" reboot="postponed"/>
>      </remove>
>    </package>
>
> </packages>
>
> -----Original Message-----
> From: wpkg-users-boun...@lists.wpkg.org 
> [mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of DANY CHOUINARD
> Sent: Wednesday, November 17, 2010 6:34 AM
> To: wpkg-users@lists.wpkg.org
> Subject: [wpkg-users] Deploying office 2010
>
> 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.
>
> It would be cool if anyone was able to make the script waits the completion 
> of the installation.
>
> Since I couldn't find any guide to deploy office 2010, here is how I'm doing 
> it :
>
> You need to create an MSP.  To do so, simply run "setup.exe /admin" from the 
> installation CD.  This is the nice and cool thing from office 2010.
> Put the MSP file in x86/Updates.
>
> Now in package.xml
>
> <package id="office2010"
>         name="Microsoft Office 2010"
>         revision="1"
>         reboot="false"
>         priority="40">
>         <check type="uninstall" condition="exists" path="Microsoft Office 
> Professional Plus 2010" />
>         <install cmd='%comspec% /C start "" /I /WAIT "%SOFTWARE% 
> \office2010\setup.exe" /adminfile "%SOFTWARE%\office2010\x86\Updates
> \horizon-office.msp" ' >
>                 <exit code="1641" reboot="delayed"/>
>         </install>
>         <upgrade cmd='%comspec% /C start /wait "%SOFTWARE%\office2010 
> \setup.exe" /adminfile "%SOFTWARE%\office2010\x86\Updates
> \horizon-office.msp"' >
>                 <exit code="1641" reboot="delayed"/>
>         </upgrade>
>         <remove cmd='%comspec% /C start /wait "%SOFTWARE%\office2010 
> \setup.exe" /uninstall ProPlus.WW /config  "%SOFTWARE%\office2010\x86 
> \ProPlus.WW\silentuninstall.xml"' /> </package>
>
> By the way, yo have to write down your own "silentuninstall.xml".  Mine looks 
> like this :
>
> <Configuration Product="ProPlus">
> <Display Level="none" CompletionNotice="no" SuppressModal="yes"
> AcceptEula="yes" />
> </Configuration>
>
> You'll be please to know that for own security, the software has to be 
> activate.  Normal user can't, just administrator.  There is a VBS script that 
> do that (i was about to cry).  It can be spawn from the installer by the MSP. 
>  Google that, it's true!  But that wont work for me, obviously 'cause an old 
> voodoo spell cast upon I.  I instead use this package :
>
> <package id="office2010-horizon-activation" name="Activation d'Office 2010"
>                 revision="1"
>                 reboot="false"
>                 priority="40">
>         <depends package-id="office2010-horizon" />
>         <check type="execute" path="%software%\office2010 \activation.bat" 
> condition="exitcodeequalto" value="0" />
>         <install cmd='"c:\windows\system32\cscript" "c:\program files 
> \Microsoft Office\Office14\OSPP.vbs" /act' />
>
> </package>
>
> Activation.bat contain the following code :
> c:\windows\system32\cscript "c:\program files\Microsoft Office\Office14 
> \OSPP.vbs" /dstatus | find "---LICENSED---"
> exit %errorlevel%
>
> There, I bared it all.  This works fine when called manually, but the 
> installer complain that he loose the network share when run from the wpkg 
> service.  I guess it is normal since the installer fork it's process, letting 
> the wpkg.js script terminate.
>
> I hope someone will find a neat hack to install office 2010.
>
>
> --
>   Dany CHOUINARD
>   Technicien en informatique               -o)
>   Commission scolaire de l'Or et des Bois   /\
>   chouinard.d...@csob.qc.ca                _\_v
>
>   tél. 819.825.4220 ext. 3041
>   cel. 819.856.6892
>   skype. dchouinard
>
>   www.danychouinard.net
> -------------------------------------------------------------------------
> 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
> -------------------------------------------------------------------------
> 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

--
  Dany CHOUINARD
  Technicien en informatique               -o)
  Commission scolaire de l'Or et des Bois   /\
  chouinard.d...@csob.qc.ca                _\_v

  tél. 819.825.4220 ext. 3041
  cel. 819.856.6892
  skype. dchouinard

  www.danychouinard.net
-------------------------------------------------------------------------
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

Reply via email to